webhook-inbox
REMOTE · INBOX.KYMAC.CO
Ephemeral HTTPS inbox for bots: mint URL, capture POSTs, list JSON. TEST. https://inbox.kymac.co
Available components
Last scanned (36 days ago)
Scores higher than 0% of remote servers
Unreachable for 7 days in a row. Last reached 23 Sep 2026.
Category Workflow Automation
Dead
Every channel of this server has been unreachable for long enough to be marked dead. Its trust score is pinned to 0 and does not recover automatically: even once the server responds again it stays dead until it is manually reinstated.
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security11
- TLS not yet verified: we couldn't open a connection to check the certificate. View diagnostics → Unverified
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC not yet verified: we couldn't validate it against a resolver. View diagnostics → Unverified
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 30 Sept 26 −13
The score moved with no change recorded against any check. We would rather say so than guess.
- 29 Sept 26 −13
The score moved with no change recorded against any check. We would rather say so than guess.
- 28 Sept 26 −13
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Sept 26 −13
The score moved with no change recorded against any check. We would rather say so than guess.
- 26 Sept 26 −13
The score moved with no change recorded against any check. We would rather say so than guess.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- DNSSEC: fail → unverified ▼ security
- Authorization: fail → unverified ▼ security
- HSTS header: fail → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- Stability: 0.17 → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 23 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 30 Sept 2026 · Probed https://inbox.kymac.co/mcp
TLS unreached
Background: What to check on a remote MCP endpoint →
DNSSEC inconclusive
Validation of inbox.kymac.co. — Inconclusive
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| inbox.kymac.co. | Error no A/AAAA/CNAME RRset answered for the name |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://inbox.kymac.co/mcp | Unreachable | ||
| http (plaintext) | http://inbox.kymac.co/mcp | HTTPS enforced |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
capture_inbox Capture a raw POST — webhook inbox, request bin ~125
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.
| Name | Type | Req | Description |
|---|---|---|---|
| body | – | – | Raw capture payload. Objects are JSON-encoded. Strings are sent as-is. |
| content_type | string | – | Content-Type for the capture. Defaults to application/json for objects. |
| id | string | yes | Inbox id from mint_inbox (inb_…). |
No output schema declared.
No examples provided.
checkout_credits Checkout credit pack — webhook inbox, request bin ~70
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.
| Name | Type | Req | Description |
|---|---|---|---|
| pack_id | string | yes | Pack id from list_credit_packs (e.g. pack_10). |
No output schema declared.
No examples provided.
confirm_credits Confirm TEST credit purchase — webhook inbox, request bin ~72
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.
| Name | Type | Req | Description |
|---|---|---|---|
| stripe_payment_intent_id | string | yes | PaymentIntent id (pi_…) from checkout_credits. |
No output schema declared.
No examples provided.
credit_balance Credit balance — webhook inbox, request bin ~22
Derived prepaid balance for this caller_id (GET /credits/balance).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
credit_events Credit ledger events — webhook inbox, request bin ~46
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
health Health — webhook inbox, request bin ~30
Public readiness (GET /health): billing (test|live|gated) and runner_ready. No key.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
issue_key Issue caller key — webhook inbox, request bin ~89
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_credit_packs List credit packs — webhook inbox, request bin ~35
Prepaid TEST packs (GET /credits/packs). checkout_credits is intent only; credits grant after confirm_credits.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_inbox_events List captured POSTs — webhook inbox, request bin ~61
Owner list (GET /inbox/{id}/events). Returns captured POSTs as JSON (headers + body). Does not debit. Other callers see 404.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Inbox id from mint_inbox (inb_…). |
No output schema declared.
No examples provided.
mint_inbox Mint ephemeral inbox — webhook inbox, request bin ~147
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
quote_credits Quote credit cost — webhook inbox, request bin ~52
Dry-run cost for an op without debit (GET /credits/quote?op=inbox). Returns cost, balance, and would_succeed.
| Name | Type | Req | Description |
|---|---|---|---|
| op | string | – | Operation to quote. Defaults to inbox. |
No output schema declared.
No examples provided.
revoke_inbox Revoke inbox early — webhook inbox, request bin ~48
Stop further captures (DELETE /inbox/{id}). Does not refund the mint debit. Owner only.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Inbox id from mint_inbox (inb_…). |
No output schema declared.
No examples provided.
revoke_key Revoke caller key — webhook inbox, request bin ~55
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
rotate_key Rotate caller key — webhook inbox, request bin ~66
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
verify_key Verify caller key — webhook inbox, request bin ~42
Confirm WEBHOOK_INBOX_API_KEY or Authorization: Bearer (GET /keys/verify). X-API-Key is an alias only. Does not echo the secret.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the webhook-inbox MCP server?
webhook-inbox is a hosted endpoint at https://inbox.kymac.co/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · inbox.kymac.co
claude mcp add --transport http co-kymac-inbox-webhook-inbox 'https://inbox.kymac.co/mcp'
What is the webhook-inbox MCP server?
webhook-inbox is an MCP server listed in the public MCP registry as co.kymac.inbox/webhook-inbox. Ephemeral HTTPS inbox for bots: mint URL, capture POSTs, list JSON. TEST. https://inbox.kymac.co. This page covers its hosted endpoint (https://inbox.kymac.co/mcp).
Is the webhook-inbox MCP server safe to use?
webhook-inbox scores 0 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the webhook-inbox MCP server expose?
webhook-inbox exposes 15 tools: issue_key, verify_key, rotate_key, revoke_key, list_credit_packs, and 10 more. Their descriptions and schemas cost roughly 960 tokens of context every time the server is loaded.
Does the webhook-inbox MCP server require authentication?
Its publisher declares no required credentials for webhook-inbox. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the webhook-inbox MCP server still maintained?
webhook-inbox has been unreachable for long enough that we treat it as dead, and its score is pinned to zero. We last reached this channel on 23 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.