mcp-registry/com.webhook-studio/webhooks · v0.1.1
As of 2026-10-18 22:57 UTC, the Webhook Studio Webhooks MCP server is up with a Glimind reliability score of 87/100 (grade B). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 7 outages in 90 days, with a median recovery of 3 minutes.
Keyless webhook endpoints: capture, wait, replay, forward, and generate types from real traffic.
Claude Code
claude mcp add --transport http webhook-studio-webhooks-mcp-server https://webhook-studio.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"webhook-studio-webhooks-mcp-server": {
"type": "http",
"url": "https://webhook-studio.com/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
17 of 17 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
2 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.
Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →
Handshake + tools/list takes ~1,831 ms.
Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.webhook-studio%2Fwebhooks/fixes
{
"name": "create_bucket",
"description": "Provision a new webhook endpoint (a \"bucket\") that captures incoming HTTP requests. Returns its id, public ingest url to point a provider at, inbox_url (the live human view to hand back), and signing secret. Pass external_ref — your own stable name like \"acme-api:stripe\" — so you can re-find this exact bucket later with list_buckets after losing context.",
"inputSchema": {
"type": "object",
"required": [],
"properties": {
"name": {
"type": "string",
"description": "Human label for the bucket."
},
"environment": {
"enum": [
"production",
"staging",
"sandbox",
"development"
],
"type": "string",
"description": "Deployment environment."
},
"external_ref": {
"type": "string",
"description": "Your own stable identifier (unique per account) for idempotent re-provisioning and re-finding."
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
}
}{
"name": "delete_bucket",
"description": "Permanently delete a webhook endpoint and its captured events.",
"inputSchema": {
"type": "object",
"required": [
"bucket_id"
],
"properties": {
"bucket_id": {
"type": "string",
"description": "The endpoint id."
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": true,
"idempotentHint": true
}
}{
"name": "find_correlation_keys",
"description": "List the correlation-key candidates for a learned schema — the fields that look like identifiers (e.g. data.object.id), ranked by how consistently they appear. These are the fields to group events by when reconstructing a lifecycle (a Stripe payment_intent across created -> succeeded, a GitHub PR across its events). Derived from real traffic, so it reflects what THIS account actually receives.",
"inputSchema": {
"type": "object",
"required": [
"schema_id"
],
"properties": {
"version": {
"type": "string",
"description": "Version number, or \"current\" (the default)."
},
"schema_id": {
"type": "string",
"description": "The schema id."
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/com.webhook-studio/webhooks"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/com.webhook-studio/webhooks"}) over MCP.
list_events ~360 tokensreplay_event ~343 tokensgenerate_types ~291 tokensconfigure_verification ~277 tokensforward_bucket ~272 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fcom.webhook-studio%2Fwebhooks?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fcom.webhook-studio%2Fwebhooks?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.webhook-studio%2Fwebhooks.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.webhook-studio%2Fwebhooks.svg :target: https://glimind.com/server/mcp-registry%2Fcom.webhook-studio%2Fwebhooks?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:94ccfa01f6fc1002…, first seen 2026-10-17, included at leaf 2059 of 23,692. Version history · verify what your client received.
Compare: most reliable security servers · most reliable devops servers · most reliable other servers · most reliable data servers · most reliable web servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-18 22:57 UTC, the Webhook Studio Webhooks MCP server is up with a Glimind reliability score of 87/100 (grade B). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 7 outages in 90 days, with a median recovery of 3 minutes.
Webhook Studio Webhooks MCP server advertises 17 tools, including configure_verification, create_bucket, delete_bucket, diff_schema, find_correlation_keys.
Point your MCP client at this streamable-http endpoint: https://webhook-studio.com/mcp
Glimind scanned all 17 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.