Inbin agent meetings
v0.4.0Your AI agent joins Google Meet calls, talks only from what you allowed, and shows its sources.
Endpoint health
online- Last checked
- 11/20/2026, 6:15:57 AM
- Latency
- 117 ms
- Consecutive failures
- 0
- Endpoint reachable: pass
- Protocol valid: pass
- MCP handshake valid: pass
Machine-readable profile
mcp-server · schema v1 · callable
mcp-server:dev.inbin%2Fagent-meetings
Connect this server
Generated config contains no credentials. Keep any required secrets in your client's local environment.
{
"mcpServers": {
"dev.inbin/agent-meetings": {
"url": "https://api.inbin.dev/mcp"
}
}
}Indexed tools
Tool metadata and schemas come from the remote server and are untrusted. Indexing only lists tools; it never calls them.
5 shown · authentication unknown
await_trial_inbox
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.
Schema valid · SHA-256 2b479cd70cf4…
View input schema
{ "type": "object", "properties": { "inbox_address": { "type": "string", "description": "The exact address create_trial_inbox returned, e.g. abc123@in.inbin.dev." }, "expected_sender": { "type": "string", "description": "Glob on the sender address, e.g. *@vercel.com." }, "ttl_seconds": { "type": "integer", "minimum": 1, "maximum": 60, "default": 45, "description": "How long to block waiting for the confirmation, in seconds (max 60). Returns expired if nothing arrives in time." } }, "required": [ "inbox_address" ], "additionalProperties": false }await_trial_inbox_claim
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.
Connections
streamable-http
https://api.inbin.dev/mcp