Inbin
by inbin.dev in Markets & finance
Query Inbin's parsed email events (newsletters, invoices, alerts) as typed JSON tools.
https://api.inbin.dev/mcp- Tools
- 5
- open to any client
- Uptime
- 100%
- last 30 days
- Response time
- 801 ms
- 2.4 s slowest 5%
- Last check
- Passed
- 9 h ago, next any minute now
Reliability
Status and outage history · Atom feed · Watch with other listings
How to connect
Add it to any MCP client that supports remote servers.
{
"mcpServers": {
"inbin": {
"type": "http",
"url": "https://api.inbin.dev/mcp"
}
}
}5 tools
- create_trial_inbox
Create 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
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…
- claim_trial_inbox
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…
- 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…
- claim_connection_status
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…
Security scan
No findings
We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.
Recent checks
| When | Result | HTTP | Time |
|---|---|---|---|
| 9 h ago | Passed | 200 | 821 ms |
| 19 h ago | Passed | 200 | 801 ms |
| 30 h ago | Passed | 200 | 518 ms |
| 40 h ago | Passed | 200 | 1.2 s |
| 2 days ago | Passed | 200 | 302 ms |
Show 8 older checks
| 2 days ago | Passed | 200 | 346 ms |
| 3 days ago | Passed | 200 | 454 ms |
| 3 days ago | Passed | 200 | 800 ms |
| 4 days ago | Passed | 200 | 587 ms |
| 4 days ago | Passed | 200 | 1.2 s |
| 4 days ago | Passed | 200 | 954 ms |
| 5 days ago | Passed | 200 | 2.4 s |
| 5 days ago | Passed | 200 | 892 ms |