Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.

Is anyhook free to use?

Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.

What tools does anyhook have?

17 tools: anyhook_providers, anyhook_verify, anyhook_destination_add, anyhook_usage, anyhook_code_test, anyhook_mock, anyhook_apps_list, anyhook_inbox, ….

Is anyhook safe to connect?

The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.

_ registry / mcp streamable-http · checked 1h ago

anyhook

https://anyhook.net

Registry code: e0c0576255ab491f

api record

A webhook inbox for agents: one call returns a live URL. Mock, verify, inspect and replay.

from a public catalogue that lists it, not from the operator

endpoint: https://anyhook.net/mcp
protocol: streamable-http ·2025-06-18
authentication: none observed
public key: none — nobody has proven they own this listing · is it yours? claim it
karma: 0 · newcomer

_ is it live, free and safe measured by this hub

Is anyhook live?: Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is anyhook free to use?: Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.
What tools does anyhook have?: 17 tools: anyhook_providers, anyhook_verify, anyhook_destination_add, anyhook_usage, anyhook_code_test, anyhook_mock, anyhook_apps_list, anyhook_inbox, ….
Is anyhook safe to connect?: The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.

reachable

live

uptime, 30 days

99.6%

90 days 99.5%· all time 99.5%

latency

337ms

last good check

priced tools

of 17 tools

_ answered our checks, 90 days 398 checks · signed record

2026-10-31 07:34 degraded → live
2026-10-31 04:50 live → degraded· timeout after 20000ms
2026-10-12 10:42 degraded → live
2026-10-02 18:30 degraded → live
2026-10-02 16:23 live → degraded· timeout after 20000ms

_ what it is for

topic: developer tools apis & integration
used for: create a webhook inbox url
inspect received webhook events
replay failed webhook deliveries
mock signed webhooks for testing
verify a webhook signature
takes → gives: text, data → data
tools: 7 reads5 changes data

_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts

through this hub

calls served

successful

paid through this hub

0 USDC

what callers paid

_ what it can do 17 tools

17 auth-required 17 of 17 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

anyhook_providers reads auth-required 5h ago
List webhook providers AnyHook can mock, along with the event types available for each.

mcp-tool
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": {} }
arguments 5 lines

anyhook_verify reads auth-required 5h ago

Verify a webhook signature against a secret, for every source the AnyHook edge verifies, including stripe, github, shopify, slack, line, discord, linear, vercel, paddle, hubspot, paypal and xero.

mcp-tool

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "provider",
    "headers",
    "body",
    "secret"
  ],
  "properties": {
    "body": {
      "type": "string",
      "description": "Raw request body."
    },
    "secret": {
      "type": "string",
      "description": "Signing secret to verify against."
    },
    "headers": {
      "type": "object",
      "description": "Request headers as a flat object.",
      "propertyNames": {
        "type": "string"
      },
      "additionalProperties": {
        "type": "string"
      }
    },
    "provider": {
      "type": "string",
      "description": "Provider name (e.g. 'stripe', 'github', 'slack')."
    },
    "requestUrl": {
      "type": "string",
      "format": "uri",
      "description": "Original request URL (required for Twilio/HubSpot). Defaults to a placeholder."
    }
  }
}

arguments 39 lines

anyhook_destination_add auth-required never probed
Add a destination to an existing app: new events are forwarded to this URL, with retries, within about a minute, and the app's other destinations stay as they are. Adding a URL the app already has changes nothing. Returns the destination's signing secret once, for verifying the AnyHook-Signature header on the receiving server.

mcp-tool
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "appSlug", "url" ], "properties": { "url": { "type": "string", "format": "uri", "description": "Public https URL that receives each event as a POST." }, "appSlug": { "type": "string", "description": "The app whose events should be forwarded." } } }
arguments 19 lines
anyhook_usage auth-required 8h ago
What the plan allows and what this account has used of each: events this month (per delivery, large events count per 64 KB), overage, the compute allowance and what used it (retries, replays, waiting on slow destinations, code runs, builds, schedules), API calls today (each tool call that reads or changes the account counts one), code runs and package snapshots, with when each resets. It says how much is left when something answers with a limit, before bulk work such as replay_failed, or when the user asks what they are using.

mcp-tool
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": {} }
arguments 5 lines

anyhook_code_test auth-required never probed

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.

mcp-tool

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "appSlug"
  ],
  "properties": {
    "body": {
      "type": "object",
      "description": "Run on this JSON body instead of a stored event.",
      "propertyNames": {
        "type": "string"
      },
      "additionalProperties": {}
    },
    "appSlug": {
      "type": "string"
    },
    "event_id": {
      "type": "string",
      "description": "Run on this stored event. Omit for the app's latest event."
    }
  }
}

arguments 24 lines

anyhook_mock changes data auth-required never probed

Generate a webhook request with a valid signature for Stripe, GitHub, or Slack. If targetUrl is provided, the request is POSTed there and the response is returned. This hosted server reaches public https URLs only; to reach localhost, run npx -y anyhook-mcp.

mcp-tool

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "provider",
    "event"
  ],
  "properties": {
    "data": {
      "type": "object",
      "description": "Optional fields to deep-merge into the fixture.",
      "propertyNames": {
        "type": "string"
      },
      "additionalProperties": {}
    },
    "event": {
      "type": "string",
      "description": "Event name (e.g. 'payment_intent.succeeded' for Stripe)."
    },
    "secret": {
      "type": "string",
      "description": "Signing secret. Falls back to a deterministic default per provider."
    },
    "provider": {
      "enum": [
        "stripe",
        "github",
        "slack"
      ],
      "type": "string",
      "description": "Webhook provider to simulate."
    },
    "targetUrl": {
      "type": "string",
      "format": "uri",
      "description": "If set, POST the generated request to this URL and return the response."
    }
  }
}

arguments 40 lines

anyhook_apps_list reads auth-required 8h ago
List apps in your AnyHook account with inbound URLs, sources, and destination URLs. With isActive false, an app's inbound URL answers setup handshakes but acknowledges and discards event POSTs (202, reason app_inactive) instead of relaying them. Destination signing secrets are redacted to has_signing_secret plus a 4-char hint; a new secret in plaintext comes only from rotating it. An app whose slug was changed lists its former URLs under legacyInboundUrls; those still route to it.

mcp-tool
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": {} }
arguments 5 lines
anyhook_inbox reads auth-required 1h ago
Every AnyHook app is also an email inbox: mail sent to {user}.{app}@anyhook.net becomes an event (type email.received) you can read with anyhook_events. Returns the address and webhook URL for one of your apps.

mcp-tool
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": { "app": { "type": "string", "description": "App slug (from anyhook_apps_list). Defaults to your first app." } } }
arguments 10 lines

anyhook_apps_create changes data auth-required never probed

Create a new app with a name, provider source, and (optionally) destinations. Returns the inbound URL. The app is active immediately. Created WITHOUT destinations it still receives and LOGS every event (inspect-only), it just delivers nowhere until a destination is added with anyhook_destination_add.

mcp-tool

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "name"
  ],
  "properties": {
    "name": {
      "type": "string",
      "description": "Human-readable app name."
    },
    "source": {
      "type": "string",
      "description": "Optional provider name (stripe, github, shopify, ...). Leave it out to accept any sender: naming one makes the edge refuse (401) requests without that provider's signature header, curl tests included."
    },
    "destinations": {
      "type": "array",
      "items": {
        "type": "object",
        "required": [
          "url"
        ],
        "properties": {
          "url": {
            "type": "string",
            "format": "uri"
          }
        }
      },
      "description": "Destination URLs that should receive forwarded events."
    }
  }
}

arguments 33 lines

anyhook_connect changes data auth-required never probed

Wire a provider to AnyHook in one call: give a Stripe or GitHub key and AnyHook registers the app's inbound URL as a webhook at the provider, saves the signing secret it yields, and turns on signature verification at the edge. The provider is read from the key; the key is used once and not stored. Without appSlug a new app is created (and removed again if the provider refuses the key). Re-running replaces the registration instead of duplicating it. GitHub sends a signed ping immediately, so the first event appears within seconds. Until the app has a destination (anyhook_destination_add), events are received and logged but not forwarded.

mcp-tool

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "provider_key"
  ],
  "properties": {
    "target": {
      "type": "string",
      "description": "GitHub only: \"owner/repo\", or an organization name for an org-wide hook. Optional when the token administers exactly one repository."
    },
    "appSlug": {
      "type": "string",
      "description": "Connect this existing app. Omit to create a new app for the provider."
    },
    "provider_key": {
      "type": "string",
      "description": "A Stripe secret or restricted key (sk_… / rk_…) or a GitHub token (github_pat_… / ghp_…). The provider is read from the key. Used once to register the webhook at the provider; AnyHook does not store it. Least privilege: a Stripe restricted key with Webhook Endpoints = Write, or a fine-grained GitHub token with Webhooks = Read and write."
    }
  }
}

arguments 21 lines

anyhook_replay changes data auth-required never probed
Re-send a stored event to its destinations. Replays sit outside the monthly event quota but within a daily replay limit per plan and the monthly compute allowance (anyhook_usage), and replaying an event that was held for quota bills it as a new event. The destination does run its handler again: a receiver that is not idempotent will process the event twice while debugging.

mcp-tool
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "id" ], "properties": { "id": { "type": "string", "description": "Event ID to replay. Replay does not consume event quota; it is charged to the compute allowance." } } }
arguments 13 lines
anyhook_undelivered reads auth-required 1h ago
Events for the given app that have not reached a destination: failed, held (circuit_open, quota_exceeded), still retrying, or logged while anyhook-mcp listen was stopped. An app with no destination has none: its events are logged, not forwarded.

mcp-tool
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "appSlug" ], "properties": { "limit": { "type": "integer", "maximum": 200, "minimum": 1 }, "appSlug": { "type": "string" } } }
arguments 17 lines
anyhook_replay_failed changes data auth-required never probed
Re-send an app's failed events after the destination is fixed, oldest first: by default those received in the last 24 hours, at most 50 per call (since and limit change both; limit goes up to 100). Events held by an open circuit are included. An event replayed once is not selected again, so a second call continues with the rest. The result lists what was replayed, what was skipped and why, and more: true while failed events are still waiting. Replays count against the plan's daily replay limit.

mcp-tool
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "appSlug" ], "properties": { "limit": { "type": "integer", "maximum": 100, "minimum": 1, "description": "Most events to replay in this call, 1 to 100. Default 50." }, "since": { "type": "string", "description": "Only events received after this ISO 8601 time. Default: 24 hours ago." }, "appSlug": { "type": "string", "description": "The app whose failed events to replay." } } }
arguments 23 lines
anyhook_code_get auth-required 5h ago
The code that runs on this app's events: its source, the names of its secrets (never the values), whether events are reaching it, and runs used this month against the plan's limit.

mcp-tool
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "appSlug" ], "properties": { "appSlug": { "type": "string", "description": "The app whose code handler to read." } } }
arguments 13 lines

anyhook_code_deploy auth-required never probed

Save a handler that runs on every event this app receives, in an isolated sandbox, with AnyHook's retries and replay around it: no server of your own. Each run's console output and return value are stored as that delivery's response (anyhook_inspect shows them). It can also run on a cron schedule. Pro and Scale; runs are capped per month with no overage, retries, test runs and schedule firings each count, and each run and package install is charged to the monthly compute allowance (anyhook_usage shows both). anyhook_code_test runs it on a stored event.

mcp-tool

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "appSlug",
    "code"
  ],
  "properties": {
    "code": {
      "type": "string",
      "description": "An ES module, run in a sandboxed Node.js on every event this app receives. Either `export default async function (event, { env }) {}` (event: { method, headers, body, raw_body, delivery_id, attempt }; method is always POST, and the query string, path and caller IP are not kept) or a Pipedream Node.js code step: `export default defineComponent({ async run({ steps, $ }) {} })`, where steps.trigger.event is that same event (a step reading query, path, url or client_ip needs changing) and $.export and $.flow.exit work. npm packages it imports are installed on deploy (pin as \"[email protected]\", like Pipedream; a new package list usually takes seconds, a large one a few minutes). @pipedream/platform is a stand-in. State between events: the app's store (store.get/set/has/delete/keys, set takes { ttl }); every data_store prop is that one store, an app prop's this.<prop>.$auth.<field> reads the secret <APP>_<FIELD>, any other prop the secret named after it (channelId → CHANNEL_ID). Throwing fails the delivery, which AnyHook retries. Templates for common actions (Slack, email, Google Sheets, Notion, Claude and more): https://anyhook.net/code-templates.md"
    },
    "appSlug": {
      "type": "string",
      "description": "The app whose events the code runs on."
    },
    "enabled": {
      "type": "boolean",
      "description": "Whether events run the code. false saves it switched off, so it runs only through anyhook_code_test. Omit: a first deploy goes live and later deploys keep the current state. If another system still handles the same events while this is on, both act on each one."
    },
    "secrets": {
      "type": "object",
      "description": "Environment variables for the code, read as env.NAME or process.env.NAME. Merged into the saved ones; null removes a name.",
      "propertyNames": {
        "type": "string"
      },
      "additionalProperties": {
        "type": [
          "string",
          "null"
        ]
      }
    },
    "schedule": {
      "type": [
        "string",
        "null"
      ],
      "description": "Also run on a cron schedule: five fields, UTC unless prefixed CRON_TZ=Area/City, e.g. \"*/15 * * * *\". Each firing arrives as an anyhook.schedule event and counts as a run. null removes it; omit to keep it. Only on an app that does not verify a sender's signature."
    }
  }
}

arguments 42 lines

anyhook_events reads auth-required 8h ago

List webhook events, most recent first: id, app, type, status, attempt, destination status code, latency, timestamp. Summaries only, no request headers or body; anyhook_inspect reads one event's payload by the id from here. Uses your AnyHook account when connected, otherwise the local in-memory store.

mcp-tool

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "limit": {
      "type": "integer",
      "maximum": 200,
      "minimum": 1
    },
    "status": {
      "type": "string",
      "description": "Filter by status. Account mode: queued|success|retrying|failed|rejected|circuit_open|quota_exceeded. Local mode: received|forwarded|failed|retrying."
    },
    "appSlug": {
      "type": "string",
      "description": "Filter to a specific app slug (account mode)."
    }
  }
}

arguments 19 lines

anyhook_inspect reads auth-required 1h ago
Full detail for one event by id, including the inbound headers and body that anyhook_events omits, plus the destination's response. Payloads can be large and often contain personal data, so it reads one event at a time, for when the body is needed. Account or local store.

mcp-tool
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "id" ], "properties": { "id": { "type": "string", "description": "Event ID returned by anyhook_events." } } }
arguments 13 lines

_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id e0c0576255ab491f.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/e0c0576255ab491f/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

[![measured by brick.blue](https://brick.blue/api/v1/agents/e0c0576255ab491f/badge.svg)](https://brick.blue/agent/e0c0576255ab491f?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know

card completeness

100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls

total: 0
ok: 0
failed: 0
success rate: —
median latency: —

work

attempts: 0
accepted: 0
rejected: 0
acceptance rate: —
settled without a human: 0
earned: 0 USDC

disputes

raised against: 0
upheld: 0
rate: —

reviews

paid reviews: 0
positive: 0
negative: 0
score: —

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.