server.json
1 field changed
- version
-
0.265.10.267.3
io.github.whisper-sec/whisper
29 changes recorded. MCP Harbor re-reads this listing from the official registry every six hours and asks the live server what it exposes, and keeps what changed between one look and the next.
https://whisper.online/llms.txt
− and the graph. Send X-API-Key and the other 22 appear.− You may hold up to 1000 agents per account.− dig +short TLSA _443._tcp.ae3b051ff3bf7f478.tdc38e7c55bad3306a92b830f9bb1e4f9.agents.whisper.online # 3 DANE key pinned in signed DNS− curl -s https://rdap.whisper.online/ip/2a04:2a01:b69a:6717:e3b0:51ff:3bf7:f478 # 4 RDAP registry record, refers up to RIPE− whois -h whois.whisper.online 2a04:2a01:b69a:6717:e3b0:51ff:3bf7:f478 # 5 WHOIS (RFC 3912), same record− curl -s https://rdap.whisper.online/verify-identity/2a04:2a01:b69a:6717:e3b0:51ff:3bf7:f478 | jq '{is_whisper_agent,dane_ok,jws_ok}' # 6 keyless full chain− dig +short CNAME scout.tdc38e7c55bad3306a92b830f9bb1e4f9.agents.whisper.online # 7 friendly name resolves to the same agent− One CLI command re-derives all seven proofs above itself -- DNSSEC, DANE, the− transparency ledger, and a signed identity document -- anchored at the IANA− DNSSEC root, with Whisper's own API explicitly NOT in the trust path:− for every MCP host. KEYLESS tools: verify, rdap. KEY-GATED tools: register,− list, policy, logs, revoke, egress-config.− - Concepts -- what the identity is, and the architecture underneath it.+ Site owners: https://whisper.online/docs/verify-agents says what a Whisper agent is,+ the three ways to verify one, and where to report one.+ and the graph. Send X-API-Key and the other 24 appear.+ Each account holds up to 1000 agents.+ dig +short CNAME scout.tdc38e7c55bad3306a92b830f9bb1e4f9.agents.whisper.online # 3 friendly name resolves to the same agent+ dig +short TLSA _443._tcp.ae3b051ff3bf7f478.tdc38e7c55bad3306a92b830f9bb1e4f9.agents.whisper.online # 4 DANE key pinned in signed DNS+ curl -s https://rdap.whisper.online/ip/2a04:2a01:b69a:6717:e3b0:51ff:3bf7:f478 # 5 RDAP registry record, refers up to RIPE+ whois -h whois.whisper.online 2a04:2a01:b69a:6717:e3b0:51ff:3bf7:f478 # 6 WHOIS (RFC 3912), same record+ curl -s https://rdap.whisper.online/verify-identity/2a04:2a01:b69a:6717:e3b0:51ff:3bf7:f478 | jq '{is_whisper_agent,dane_ok,jws_ok}' # 7 keyless full chain+ The numbers are the ones https://whisper.online/docs/identity gives the proofs.+ One CLI command runs four checks itself -- DNSSEC over proofs 1, 2 and 4, a+ live DANE handshake, the transparency ledger, and the signed identity document --+ anchored at the IANA DNSSEC root, with Whisper's own API explicitly NOT in the+ trust path:+ for every MCP host, run locally over stdio. KEYLESS tools: verify, rdap,+ assess, identify, explain. KEY-GATED tools: register, list, policy, logs,+ revoke, egress-config, and the graph tools. Not to be confused with the hosted+ https://whisper.online/mcp (17 tools keyless, 41 with a key) or the graph+ server https://mcp.whisper.security (OAuth or a key, always).+ - Concepts -- what the identity is, and the architecture underneath it. Start with+ /docs/step-by-step (one agent from sign-up to revoke, and the assumptions it rests on)+ For site owners receiving agent traffic, start at /docs/verify-agents
https://whisper.online/llms.txt
− When Whisper fetches on your behalf, the request is signed. Web Bot Auth (the IETF− webbotauth work): Ed25519 HTTP Message Signatures with tag web-bot-auth, and the key at− can verify it without asking us. Cloudflare, AWS WAF, Vercel, DataDome, Akamai and HUMAN− already check this, and fewer than a hundred directories exist.− 2a04:2a01::/32 (within RIPE allocation 2a04:2a00::/31); one /128 per agent. No− third party sits anywhere in the trust path.− agent identities under YOUR-DOMAIN.COM, proven by DNSSEC delegation + DS.− agents mount under it, DNSSEC-signed, so a name like agents.YOUR-DOMAIN.COM is+ When Whisper fetches on your behalf through the fetch-forward gateway+ (forward.whisper.online), the request is signed with Web Bot Auth (the IETF webbotauth+ drafts): an Ed25519 HTTP Message Signature with tag web-bot-auth, and the key at+ can verify it without asking us. Egress over SOCKS5, HTTP CONNECT and WireGuard tunnels+ TCP and packets, so it carries no HTTP signature; it is attributable instead by its source+ /128, inside the ranges at https://whisper.online/.well-known/agent-ranges.json and by+ forward-confirmed reverse DNS. Cloudflare, AWS WAF, Vercel, DataDome, Akamai and HUMAN+ verify Web Bot Auth signatures, but none of them is enrolled to recognise Whisper yet;+ we are seeking enrolment.+ 2a04:2a01::/32 (within RIPE allocation 2a04:2a00::/31); one /128 per agent. No third-party CA, DNS host or signing service sits in the trust path; above our own zones there are only the parent registries and the IANA root.+ agent identities under {your-domain}, proven by DNSSEC delegation + DS.+ agents mount under it, DNSSEC-signed, so a name like agents.{your-domain} is+ ## The edge feed (keyless)+ Typed data planes about IP addresses, free with no key and no account, with what+ is live and what is withheld rendered from the signed manifest:+ https://whisper.online/edge/ (Markdown twin: https://whisper.online/edge.md ).+ The documents behind it, served as Markdown:+ https://whisper.online/edge/README.md what it is, and how to start+ https://whisper.online/edge/REFERENCE.md the full operator manual+ https://whisper.online/edge/POLICY.md the policy language+ https://whisper.online/edge/DATA.md every data plane+ https://whisper.online/edge/ARCHITECTURE.md how the feed is built, signed and served
https://raw.githubusercontent.com/whisper-sec/whisper-cli/HEAD/AGENTS.md
− Requires Go 1.25+. Run all four before proposing a change; CI runs the same set and a+ Requires Go 1.26.9+. Run all four before proposing a change; CI runs the same set and a
We can't find the internet
Attempting to reconnect
Something went wrong!
Attempting to reconnect