hooks.bot bronze

www.hooks.bot

“hooks.bot gives you disposable webhook endpoints and a signature debugger. THE LOOP 1. create_endpoint — returns a URL like https://www.hooks.bot/h/{id} 2. Give that URL to the user and tell them to point their provider at it. 3. wait_for_request — blocks until something lands. Call this instead of asking the user to paste anything; it returns the captured bytes directly. 4. diagnose_signature with endpoint_id + request_id and the user's signing secret. WHAT diagnose_signature ACTUALLY DOES It does not merely check a signature. It rebuilds it across every plausible construction — body normalization, secret derivation, hash algorithm, digest encoding and signed-string layout — finds the one that reproduces the signature the provider sent, and reports which step differs from that provider's documented scheme. So a result is a proven cause, not a guess. Prefer it over reasoning about the user's code. READING THE RESULT - status "valid" means the signature verifies. Check the timestamp finding anywa

https://www.hooks.bot/mcp its card

Checked 5d ago prompts, resources, tools

we checked this the operator says this

Community rating 0 0 up · 0 down — sign in to vote

Verified by agenttru.st

Everything here is a check agenttru.st performed itself. Assurance, protocol, hosting and freshness are in the card above and are not repeated.

Certificate: Issued by Google Trust Services domain-validated
Valid until 16 Jan 2027 as of our check on 9 Nov 2026. A wildcard certificate: its other hosts are invisible here, because CT logs the wildcard, not them.

Control of the hostname was checked; nothing about who operates it.

Key ECDSA P-256, signed ECDSA-SHA256, issued via WE1 under GTS Root R4 — classical, as every publicly trusted certificate is today.

Names on this certificate (3)

hooks.bot, www.hooks.bot, *.www.hooks.bot.
Connection: TLS 1.3 · X25519MLKEM768 — post-quantum hybrid key exchange, agreed with our checker on 9 Nov 2026. What this means
DANE / TLSA: Not verified (TLSA query returned RCodeNameError)
Discovery: Well-known document
AI use policy: Search: yesAI input: yesAI training: yes

What this site's robots.txt says about how AI may use its content. Recorded as the operator wrote it, not enforced — these are preferences about use, not access, and agenttru.st only reads the agent's own discovery documents.
AI-facing documents: Publishes /llms.txt — “hooks.bot” a curated map of the site's content for language models

Fetched from this host during verification. Neither document is how this agent was discovered.
First seen: 1 Nov 2026

View verification details

Assurance: bronze Bronze — agent card fetched over HTTPS with a valid certificate
Protocols: MCP verified by handshake or card fetch, not merely advertised
Hosted in: ? Unknown · Cloudflare, Inc. (AS13335)
The address did not geolocate — usually anycast hosting, where one address answers from many places at once.
Last checked: 5d ago

What this agent says it can do

Declared in the agent's own card. agenttru.st has not tested whether it completes any of these tasks — the operator of www.hooks.bot controls every word below.

This card declares no skills. That is not a fault — the field is optional, and an agent can be perfectly functional without describing itself.

What kind of listing

No skills declared: Its card declares no skills, or, for an MCP server, listed no tools.

Checked by agenttru.st against this listing's hostname and card — facts about a name or an address, not about what the agent does. How kinds are decided.

Technical agent card

Copied from the agent's card. The operator controls these values; agenttru.st has not verified them.

Protocol: mcp
Version: 0.1.0

View all card details

Capabilities: prompts resources tools
Agent card: https://www.hooks.bot/mcp

Operate this agent and would rather not be listed? Request removal.