mcp-registry/net.anyhook/anyhook · v0.4.0
Also listed as glama/gba3124/anyhook-mcp, mcp-registry/io.github.gba3124/mcp · primary listing: mcp-registry/io.github.gba3124/mcp
As of 2026-10-26 18:45 UTC, the Anyhook MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
A webhook inbox for agents: one call returns a live URL. Mock, verify, inspect and replay.
Point your MCP client at this streamable-http endpoint: https://anyhook.net/mcp
4 parameter(s) across 3 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
1 tool(s) have parameters with no type (no type/enum/anyOf/$ref).
Give every parameter a "type" (or "enum"/"anyOf"). Untyped parameters make models guess — strings for numbers, objects for arrays. How to fix →
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 →
In the last 30 days: 0 tool(s) removed and 20 schema change(s).
Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 3 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fnet.anyhook%2Fanyhook/fixes
{
"name": "anyhook_code_test",
"description": "Run the saved handler now and return its logs, return value and duration: on a stored event (the latest when event_id is omitted) or on a body you give. Counts as a run. Nothing is delivered, but whatever the code itself sends does happen.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"appSlug"
],
"properties": {
"body": {
"description": "Run on this body instead of a stored event.",
"type": "string"
},
"appSlug": {
"type": "string"
},
"event_id": {
"type": "string",
"description": "Run on this stored event. Omit for the app's latest event."
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": false,
"openWorldHint": true,
"destructiveHint": true
},
"title": "Run an app's code on a stored event"
}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/net.anyhook/anyhook"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/net.anyhook/anyhook"}) over MCP.
anyhook_code_deploy ~788 tokensanyhook_connect ~384 tokensanyhook_apps_create ~266 tokensanyhook_mock ~259 tokensanyhook_verify ~255 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%2Fnet.anyhook%2Fanyhook?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fnet.anyhook%2Fanyhook?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fnet.anyhook%2Fanyhook.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fnet.anyhook%2Fanyhook.svg :target: https://glimind.com/server/mcp-registry%2Fnet.anyhook%2Fanyhook?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:d8f8c5c8cc39dc9e…, first seen 2026-10-22, included at leaf 47565 of 74,811. Version history · verify what your client received.
Compare: most reliable other servers · most reliable code servers · most reliable web servers · most reliable email servers · most reliable devops 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-26 18:45 UTC, the Anyhook MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Anyhook MCP server advertises 16 tools, including anyhook_apps_create, anyhook_apps_list, anyhook_code_deploy, anyhook_code_get, anyhook_code_test.
Point your MCP client at this streamable-http endpoint: https://anyhook.net/mcp
Glimind scanned all 16 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.