Inbin: email and meetings for AI agents MCP server
io.github.yaotsakpo/inbinyaotsakpostreamable-httpv0.4.0Scanned
Email and meetings for AI agents you can trust: checked mail, held sends, Meet calls you approve.
5 tools: 3 change things and 2 only read.
- Reads private data · 2
- Reads text others write · 2
- Can send data out · 0
- 3 findings
Tools listed without sign-in. Remote posture
With Anlyon
3 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Inbin: email and meetings for AI agents MCP server can do
The Inbin: email and meetings for AI agents MCP server is published by the GitHub account yaotsakpo. It has 5 tools. It can create or change data (3 tools: create_trial_inbox, claim_trial_inbox and await_trial_inbox_claim), but cannot delete data. 2 tools only read.
2 tools read private data (await_trial_inbox and claim_connection_status); 2 tools bring in text other people can write (await_trial_inbox and claim_connection_status).
The fixed checks matched 3 findings (credentials-mention). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.
Last scanned Nov 11, 2026, version 0.4.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
5 tools
Changes things 3Claude Code: ask
await_trial_inbox_claimBlock (up to ttl_seconds, max 60) for a human to finish the EMAIL+CODE step on the claim_url page from claim_trial_inbox.1 finding
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Info
The description mentions "credential".
What this check looks forMatched text
description: "...claim_trial_inbox. This NEVER returns a credential, at any status. It returns one of three..."
Description, as the server wrote it Block (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 the connection at least once -- a real, observed signal, not an assumption). Each response includes a next_action field telling you exactly what to say or do -- follow it literally rather than guessing. "claimed" is NOT success: do not tell the human it's working until you see "client_installed", and even then, verify it yourself (call list_inboxes or similar through the new connection and read the actual result) before claiming it works for you specifically -- call claim_connection_status later if you need to check again after this chat session, since installing a client can take arbitrarily long and this tool only blocks up to 60s.
Annotations the server declares
- title: Wait for the claim page to be finished
- readOnlyHint: true
claim_trial_inboxStart connecting an agent to this inbox address, permanently -- the SAME address.1 finding
Why it is in this group
- The description's first verb is "start": a word for a change.
Findings
- Info
The description mentions "credential".
What this check looks forMatched text
description: "...one-time code Inbin sends there, and a credential is ISSUED. That is NOT the same as the..."
Description, as the server wrote it Start 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 client's config before anything can actually use it, and you will never see the credential itself, by design. Call await_trial_inbox_claim afterward to see the human finish the email+code step, then claim_connection_status (repeatedly, possibly much later -- installing a client is not instant) to see whether a client has actually started using it. The inbox must still exist (not yet expired) for this to work; it does not need to still be a TRIAL inbox specifically.
Annotations the server declares
- title: Connect an agent to this inbox, permanently
- readOnlyHint: false
- idempotentHint: false
create_trial_inboxGet a disposable email address (a temporary inbox) for a signup or verification code, with NO Inbin account required at all -- usable before the human has signed up for anything.No findings
Why it is in this group
- The name "create_trial_inbox" says "create": a word for a change.
Description, as the server wrote it Get a disposable email address (a temporary inbox) for a signup or verification code, 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 visit, no key to copy, and more than one agent can independently connect to the same address over time this way.
Annotations the server declares
- title: Create a no-signup trial inbox
- readOnlyHint: false
- idempotentHint: false
Only reads 2Show 2 read-only tools
await_trial_inboxWait for the verification code or confirmation link email on a trial inbox: block (up to ttl_seconds, max 60) for the one confirmation email on a trial inbox created by create_tria…Reads private dataReads text others writeNo findings
Why it is in this group
- The description's first verb is "wait": a word for reading.
What it can reach
- private-dataThe name "await_trial_inbox" says "inbox": it reads mail.
- private-dataThe description's first sentence says "wait" and "email": it reads mail.
- private-dataThe input names an inbox (input.inbox_address), and the tool reads: it reads mail.
- untrusted-inputThe name "await_trial_inbox" says "inbox": it reads inbound email, which other people can write.
- untrusted-inputThe description's first sentence says "wait" and "email": it reads inbound email, which other people can write.
Description, as the server wrote it Wait for the verification code or confirmation link email on a trial inbox: block (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 ceiling, not the inbox's total lifetime: a sender that takes longer than that is not a failure, just call this again with the same inbox_address to keep waiting (the inbox stays valid for its full ~2-week expiry, and you can call this again later too, e.g. to catch a second, later email on the same address). Only treat expired as final once you've retried a few times.
Annotations the server declares
- title: Wait for a trial inbox's confirmation
- readOnlyHint: true
claim_connection_statusRead-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" (…Reads private dataReads text others write1 finding
Why it is in this group
- The name "claim_connection_status" says "status": a word for reading.
What it can reach
- private-dataThe description's first sentence says "read" and "inbox": it reads mail.
- untrusted-inputThe description's first sentence says "read" and "inbox": it reads inbound email, which other people can write.
Findings
- Info
The description mentions "credential".
What this check looks forMatched text
description: "...RIGHT NOW: "claim_pending", "claimed" (credential issued, unused), or "client_installed"..."
Description, as the server wrote it Read-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. Each response includes a next_action field telling you exactly what to say or do.
Annotations the server declares
- title: Check a connection's real status
- readOnlyHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.
- Reads private data2
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write2
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:13 UTC, unchanged since Nov 13, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 3
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://api.inbin.dev/.well-known/oauth-protected-resource/mcp
- Authorization servers
- https://inbin.dev
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- yes
- Client ID metadata documents
- no
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 3 tools that change things (3 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://api.inbin.dev/mcp: tools/list returned 5 tools to an anonymous client, including create_trial_inbox (write), claim_trial_inbox (write), await_trial_inbox_claim (write)
Posture changes
- Nov 13, 2026
- Tools that change things, listed without credentials: 4 to 3
Findings
Matches of fixed checks, with the text they matched.
The description mentions "credential".
What this check looks forMatched text
description: "...one-time code Inbin sends there, and a credential is ISSUED. That is NOT the same as the..."
The description mentions "credential".
What this check looks forMatched text
description: "...claim_trial_inbox. This NEVER returns a credential, at any status. It returns one of three..."
The description mentions "credential".
What this check looks forMatched text
description: "...RIGHT NOW: "claim_pending", "claimed" (credential issued, unused), or "client_installed"..."
History
Changes to its tool definitions and to its remote endpoint, newest first.
PostureRemote posture changed. Tools that change things, listed without credentials: 4 -> 3.View diff
- Tools that change things, listed without credentials: 4 to 3
Tools1 changed.~1 changedView diff
- Changed:claim_trial_inboxChanges thingsinputSchema
Tools2 changed.~2 changedView diff
- Changed:await_trial_inboxOnly readsdescription
- Changed:create_trial_inboxChanges thingsdescription
Install
Pinned to version 0.4.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http inbin https://api.inbin.dev/mcpclaude mcp add --transport http inbin https://api.inbin.dev/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__inbin__await_trial_inbox",
"mcp__inbin__claim_connection_status"
],
"ask": [
"mcp__inbin__create_trial_inbox",
"mcp__inbin__claim_trial_inbox",
"mcp__inbin__await_trial_inbox_claim"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as inbin. Review it before you use it.
Capability tags behind 2 rules
- mcp__inbin__await_trial_inbox private-data, untrusted-input
- mcp__inbin__claim_connection_status private-data, untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.yaotsakpo/inbin/verify?hash=7afb5b0b3074f6bed97ccdf2893b62fab2beea4b9ddb374ac4dbcf1d4edcf569" | jq -e '.changed == false'Pinned hash 7afb5b0b3074, from Nov 11, 2026, 23:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.yaotsakpo/inbin/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.yaotsakpo/inbin)Source: MCP Registry · repository. Synced Nov 11, 2026, 23:18 UTC.
Inbin: email and meetings for AI agents MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Inbin: email and meetings for AI agents MCP server safe?
- No scan can promise that. What its definitions show: 5 tools, 3 of which can change, send or delete something, and 3 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Inbin: email and meetings for AI agents MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Inbin: email and meetings for AI agents MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Inbin: email and meetings for AI agents MCP server have?
- 5 tools: 3 write, 2 read. create_trial_inbox, claim_trial_inbox, await_trial_inbox_claim, await_trial_inbox and claim_connection_status.
Does the Inbin: email and meetings for AI agents MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Inbin: email and meetings for AI agents MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Inbin: email and meetings for AI agents MCP server changed its tools?
- Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 11, 2026. Every change is on this page and in its Atom feed.