Inbin
Query Inbin's parsed email events (newsletters, invoices, alerts) as typed JSON tools.
Connector by yaotsakpo · GitHub account verified by the MCP Registry
Install
Works with Claude Code, VS Code, Codex, Cursor, Windsurf, Claude Desktop. Read the repository before you give any tool access to your data.
npx agentmarket install connector/yaotsakpo-inbin
Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.
Remote endpoint
https://api.inbin.dev/mcpRemote (HTTP)
Get the weekly diff
The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.
About
Reviews
Write a reviewNo reviews yet. Installed it? Reviews come from verified installers only. How reviews work
Permissions
What this server can do and what it asks for, from its tool list and install config. Checked Oct 25, 2026.
- Tools
- 3 read · 2 write · 0 delete
- Secrets
- 2 (API keys, tokens or passwords)
- Install scripts
- Not scanned yet
- Runs as
- Node.js package
Tools by what they do 5
From the running server's own tool list (tools/list) on Oct 25, 2026.
Read 3 · Look things up without changing anything.
await_trial_inboxawait_trial_inbox_claimclaim_connection_status
Write 2 · Create, change, send or run things.
claim_trial_inboxcreate_trial_inbox
Secrets and settings it asks for
Secrets: values you paste in that let it act as you.
AuthorizationINBIN_API_KEY
Network hosts it talks to 1
api.inbin.dev· found in remote endpoint, install command
Tools (5)
As the server listed them on Oct 25, 2026. Descriptions are the server’s own words; hidden characters are shown as [U+…].
await_trial_inboxWait for a trial inbox's confirmationread-onlyBlock (up to ttl_seconds, max 60) for the one confirmation email on a trial inbox created by create_trial_inbox. Pass the exact inbox_address that call returned. The inbox does NOT self-delete or become unusable after a match: it keeps receiving mail and can still be claimed afterward (call claim_trial_inbox any time before it expires) if the human wants to keep using the same address. Call this AFTER you have actually used the address somewhere (signed up, requested a code) -- calling it before that will just expire, since there is nothing to wait for yet. 60 seconds is a hard per-call ceilin…
await_trial_inbox_claimWait for the claim page to be finishedread-onlyBlock (up to ttl_seconds, max 60) for a human to finish the EMAIL+CODE step on the claim_url page from claim_trial_inbox. This NEVER returns a credential, at any status. It returns one of three honest states, not a single 'connected': "claim_pending" (nobody has entered the code yet -- keep waiting or call again), "claimed" (the human proved ownership and a credential was ISSUED, but nothing has used it yet -- a client still needs to be installed with the config from the claim page's 'Advanced' section before anything works), or "client_installed" (some client has actually authenticated with t…
claim_connection_statusCheck a connection's real statusread-onlyRead-only, non-blocking check of exactly which state a claim_trial_inbox connection is in RIGHT NOW: "claim_pending", "claimed" (credential issued, unused), or "client_installed" (a client has actually authenticated with it at least once -- real, observed). Never returns a credential. Use this instead of await_trial_inbox_claim when you want to check progress WITHOUT blocking, especially much later than the original chat session -- installing a client into its own config is a human action with no fixed timeline, so polling this occasionally (not in a tight loop) is the right way to check back.…
claim_trial_inboxConnect an agent to this inbox, permanentlyStart connecting an agent to this inbox address, permanently -- the SAME address. Works whether this is a brand-new trial inbox OR one that's already been claimed by a different agent before: more than one agent can independently connect to the same inbox, each getting its own separate, revocable connection. Returns a claim_url immediately -- share it in chat right away. The human clicks it, enters their email, enters the one-time code Inbin sends there, and a credential is ISSUED. That is NOT the same as the connection working yet -- the human still has to install that credential into an MCP …
create_trial_inboxCreate a no-signup trial inboxCreate a temporary inbox with NO Inbin account required at all -- usable before the human has signed up for anything. Returns the inbox address IMMEDIATELY; it does not wait for anything. Use the address to sign up wherever you need a confirmation sent, THEN call await_trial_inbox with that same address to block for the confirmation -- calling this alone does not get you a confirmation. This inbox is NOT tied to any account yet and expires automatically within about two weeks regardless of use. If the human wants to keep using this SAME address permanently, call claim_trial_inbox: no dashboard…
Signals
- Stars
- 1
- Forks
- 0
- Open issues
- 0
- Weekly downloads
- 12
- Last commit
- Aug 23, 2026 (2 months ago)
- Last release
- Jul 25, 2026 (3 months ago)
- Last package publish
- Jul 25, 2026 (3 months ago)
From GitHub (fetched Oct 24, 2026) and the package registry.
Details
- Registry name
io.github.yaotsakpo/inbin- Version
- 0.2.0
- Auth
- Bearer token, API key
- Packages
- npm @inbin/mcp
- License
- MIT
- Repository
- github.com/yaotsakpo/inbin-mcp
- First seen
- Oct 24, 2026
- Last checked
- Oct 24, 2026
More from yaotsakpo
Cite this page
Inbin MCP server. Agent Mart. https://agentmart.dev/connectors/yaotsakpo-inbin (last updated 2026-10-24)