webhook-inbox
REMOTE · INBOX.KYMAC.CO · SCANNED SEP 20
Ephemeral HTTPS inbox for bots: mint URL, capture POSTs, list JSON. TEST. https://inbox.kymac.co
Available components
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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (revoke_key). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability78
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 960 tokens (~64/item across 15 items; 15 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management7
- Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 15 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities40
- Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
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'
{
"mcpServers": {
"co-kymac-inbox-webhook-inbox": {
"url": "https://inbox.kymac.co/mcp"
}
}
} {
"servers": {
"co-kymac-inbox-webhook-inbox": {
"type": "http",
"url": "https://inbox.kymac.co/mcp"
}
}
} [mcp_servers.co-kymac-inbox-webhook-inbox] url = "https://inbox.kymac.co/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"co-kymac-inbox-webhook-inbox": {
"type": "remote",
"url": "https://inbox.kymac.co/mcp",
"enabled": true
}
}
} openclaw mcp add co-kymac-inbox-webhook-inbox --url 'https://inbox.kymac.co/mcp' --transport streamable-http
mcp_servers:
co-kymac-inbox-webhook-inbox:
url: "https://inbox.kymac.co/mcp" {
"McpServers": {
"co-kymac-inbox-webhook-inbox": {
"Transport": "http",
"Url": "https://inbox.kymac.co/mcp"
}
}
} assistant mcp add co-kymac-inbox-webhook-inbox -t streamable-http -u 'https://inbox.kymac.co/mcp'
{
"mcpServers": {
"co-kymac-inbox-webhook-inbox": {
"type": "http",
"url": "https://inbox.kymac.co/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 19 Sept 26 +1
- Stability: unverified → 0.03 ▲ functional
- 18 Sept 26 62
First indexed and scored.
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 20 Sept 2026 · Probed https://inbox.kymac.co/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=inbox.kymac.co | CN=Amazon ECDSA 256 M01,O=Amazon,C=US | 17 Sept 2026 | 2 Apr 2027 | ECDSA 256 | ECDSA-SHA256 | 4e26063a86ea97c1278e107338671fc |
| SANs: inbox.kymac.co | ||||||
| CN=Amazon ECDSA 256 M01,O=Amazon,C=US (CA) | CN=Amazon Root CA 3,O=Amazon,C=US | 23 Aug 2022 | 23 Aug 2030 | ECDSA 256 | ECDSA-SHA256 | 773126684d577c0fcf8d3a342bea86f94fc8f |
| CN=Amazon Root CA 3,O=Amazon,C=US (CA) | CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US | 25 May 2015 | 31 Dec 2037 | ECDSA 256 | SHA256-RSA | 67f944a30cfcc4f74b5f5306e54d3b7be0ac3 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of inbox.kymac.co. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| co. | present | 7786 | 8 | Verified |
| kymac.co. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
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 | Verified | 200 | |
| http (plaintext) | http://inbox.kymac.co/mcp | HTTPS enforced | 301 | https://inbox.kymac.co:443/mcp |
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.
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 63 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?
No. We connected to webhook-inbox without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the webhook-inbox MCP server still maintained?
webhook-inbox is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.