mcpbeat Sign in

webhook-inbox MCP Server

by kymac-inbox Your server? Claim it
answering

webhook-inbox is answering right now. Last checked 11 min ago. It exposes 15 tools.

Ephemeral HTTPS inbox for bots: mint URL, capture POSTs, list JSON. TEST. https://inbox.kymac.co

Uptime history 22 hours of history
22 hours agonow
100.0%
Uptime 24h
83 of 83 checks
15
Tools
read from the server
455 ms
Response time
average over 24h
open, no key
Access
streamable-http

Nothing serious here today

Today is the operative word: we check webhook-inbox every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 11 min ago.

run in your terminal
claude mcp add webhook-inbox --transport http https://inbox.kymac.co/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "webhook-inbox": {
      "url": "https://inbox.kymac.co/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.webhook-inbox]
url = "https://inbox.kymac.co/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "webhook-inbox": {
      "url": "https://inbox.kymac.co/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "webhook-inbox": {
      "url": "https://inbox.kymac.co/mcp"
    }
  }
}

Available tools 15

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

credit
credit_balance
Derived prepaid balance for this caller_id (GET /credits/balance).
credit_events
Append-only Ledger events for this caller_id (GET /credits/events): credit.grant (first_key), credit.purchase, credit.debit reason=inbox_mint, optional credit.balance_snapshot.
list_credit_packs
Prepaid TEST packs (GET /credits/packs). checkout_credits is intent only; credits grant after confirm_credits.
revoke
revoke_inbox
Stop further captures (DELETE /inbox/{id}). Does not refund the mint debit. Owner only.
revoke_key
Invalidate the presented secret (POST /keys/revoke). Same id is revoked; old secret then fails 401 invalid_api_key. Prefer Authorization: Bearer; X-API-Key is an alias only. No ops file-edit.
capture
capture_inbox
Public capture (POST /c/{id}). No API key. No debit. Not an install entry. Stores raw body + headers for list_inbox_events. Rejects revoked (410 inbox_revoked) or expired (410 inbox_expired) inboxes. Body limit 1MB.
checkout
checkout_credits
Stripe TEST PaymentIntent for a pack (POST /credits/checkout). Intent only — returns credits_pending; credits are not granted or spendable until confirm_credits succeeds. Requires a caller key.
confirm
confirm_credits
Confirm a TEST PaymentIntent with Stripe test card pm_card_visa (POST /credits/confirm). This is when credits become granted/spendable (appends credit.purchase with credits_added). TEST only.
health
health
Public readiness (GET /health): billing (test|live|gated) and runner_ready. No key.
inbox
list_inbox_events
Owner list (GET /inbox/{id}/events). Returns captured POSTs as JSON (headers + body). Does not debit. Other callers see 404.
issue
issue_key
Mint a caller key (POST /keys). Bot install starts at GET https://inbox.kymac.co/llms.txt (sole advertised entry). Secret whi_… is returned once. Prefer Authorization: Bearer; X-API-Key is an alias. First issue grants 1 free credit (credit.grant reason=first_key). Quote cost with quote_credits before mint_inbox.
mint
mint_inbox
Mint a capture URL (POST /inbox). Install via GET https://inbox.kymac.co/llms.txt only. Prefer Authorization: Bearer; X-API-Key is an alias. First key includes 1 free credit. Quote first with quote_credits (no debit). Debits 1 credit on success (credit.debit reason=inbox_mint, request_id=inbox id). 201 body includes id, capture_url, expires_at, credits_remaining. HTTP fails use code/message/retryable/next (error aliases message). 401 next=refresh key. 402: code=insufficient_credits, retryable=false, next=buy credits.
quote
quote_credits
Dry-run cost for an op without debit (GET /credits/quote?op=inbox). Returns cost, balance, and would_succeed.
rotate
rotate_key
Replace the presented secret (POST /keys/rotate). Same id/caller_id and credits. New whi_… is returned once. Old secret then fails 401 invalid_api_key. Prefer Authorization: Bearer; X-API-Key is an alias only. No ops file-edit.
verify
verify_key
Confirm WEBHOOK_INBOX_API_KEY or Authorization: Bearer (GET /keys/verify). X-API-Key is an alias only. Does not echo the secret.

Endpoints

URLTransportStateLatencyChecked
https://inbox.kymac.co/mcp streamable-http answering 444 ms 11 min ago

Alternatives to webhook-inbox

same job, measured the same way
C
pdf-text
by kymac-pdf

PDF URL → extracted text for bots. Free try then prepaid TEST. https://pdf.kymac.co

12 tools answering
C
image-ocr
by kymac-ocr

Image URL → plain text OCR for bots. Free try then prepaid TEST. https://ocr.kymac.co

12 tools answering
C
feed-digest
by kymac-feeds

RSS/Atom URL → structured items for bots. Free try then prepaid TEST. https://feeds.kymac.co

12 tools answering
WebhookTest.net
by webhooktest

Anonymous webhook capture, inspection, waiting, and response configuration for AI agents.

8 tools answering
Otterkit
by useotterkit

Tunnels and webhooks for AI agents: capture, await, verify, replay, and send signed test events.

117 installs/wk local only
MailFixture
by mailfixture

Test-inbox API for email and SMS: create inboxes, long-poll messages, extract OTPs and links.

answering
Pagent
by aihumin

Hosted MCP for Pagent: review Bayesian A/B tests, capture hypotheses, manage websites via OAuth.

answering
C
shelf-smoke — url smoke / headless QA
by kymac-shelf

url smoke / headless QA: desktop+phone → pass/fail JSON. MCP shelf.kymac.co

12 tools answering

webhook-inbox — questions

Answers built from our own checks of this server.

What can webhook-inbox do?
It exposes 15 tools, read directly from the server on our last check. Among them: capture_inbox, checkout_credits, confirm_credits, credit_balance, credit_events, health and 9 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
What is webhook-inbox mostly used for?
Its tools cluster around credit and revoke. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.
Is webhook-inbox working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 83 of 83 checks got a reply (100.0%), average response time 455 ms. The bar chart above shows every period we have measured.
How do I connect webhook-inbox?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does webhook-inbox need an API key?
No. webhook-inbox completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 15 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is webhook-inbox?
It answers our handshake in 455 ms on average, which is faster than 32% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.