Whisper
REMOTE · WHISPER.ONLINE · 3 COMPONENTS
One routable IPv6 per AI agent, verifiable from the DNS root. Keyless tools need no signup.
Last scanned (15 hours ago)
Scores higher than 86% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Cloud Infrastructure
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security83
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability66
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 5064 tokens (~120/item across 42 items; 42 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 43 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 18 Nov 26 0
- Server version: 0.272.0 → 0.273.0 functional
- Server version: 0.271.0 → 0.272.0 functional
- 17 Nov 26 0
- Server version: 0.270.0 → 0.271.0 functional
- Server version: 0.269.2 → 0.270.0 functional
- Server version: 0.269.0 → 0.269.2 functional
- New tool “whisper_agents_edge” functional
- 16 Nov 26 0
- Server version: 0.268.2 → 0.269.0 functional
- 15 Nov 26 0
- Server version: 0.268.1 → 0.268.2 functional
- Server version: 0.267.4 → 0.268.1 functional
- 14 Nov 26 0
- Server version: 0.267.2 → 0.267.4 functional
- 13 Nov 26 0
- Server version: 0.267.0 → 0.267.2 functional
- Server version: 0.266.1 → 0.267.0 functional
- 12 Nov 26 0
- Server version: 0.266.0 → 0.266.1 functional
- Server version: 0.265.1 → 0.266.0 functional
- 11 Nov 26 0
- Stability: 0.97 → pass security
- Server version: 0.265.0 → 0.265.1 functional
- Server version: 0.264.2 → 0.265.0 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Probed https://whisper.online/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=whisper.online | CN=YE1,O=Let's Encrypt,C=US | 18 Nov 2026 | 16 Feb 2027 | ECDSA 256 | ECDSA-SHA384 | 5105c544c98d1139b303acb4386bee3c945 |
| SANs: whisper.online | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of whisper.online. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| online. | DS published | 30961 | 13 | Verified |
| whisper.online. | DS published | 50855 | 13 | Verified |
| whisper.online. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
| x-content-type-options | nosniff |
| referrer-policy | no-referrer |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://whisper.online/mcp | Verified | 200 | |
| http (plaintext) | http://whisper.online/mcp | HTTPS enforced | 301 | https://whisper.online/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
whisper_agents_agent agents: agent ~200
The agent operation on the Whisper control plane, served as CALL whisper.agents({op:'agent', args:{...}}). Requires your Whisper API key. The identifier in the example is a placeholder for one of YOUR agents: list them with the "agents.list" skill and {"kind":"agents"}. Add include:'tombstones' to read an agent that is gone: its newest lifecycle row says whether it was revoked, released, erased or reaped, when, by whom and why. Example call: {"skill":"agents.agent","input":{"agent":"agent-a1f4c0b2d3e4f5a67"}} Needs a linked Whisper account (OAuth) or your API key in the X-API-Key header.
| Name | Type | Req | Description |
|---|---|---|---|
| input | object | yes | Arguments for this operation, as an object. The example passes {"agent":"agent-a1f4c0b2d3e4f5a67"}. |
| Name | Type | Req | Description |
|---|---|---|---|
| columns | array | yes | The column names, in order. Each row holds one value per column at the same position. |
| rows | array | yes | The answers, one array per row, its values in the order of the column names above. An empty array means the call was understood and there was nothing to list, which is an answer and not a failure. |
| sensitive | array | yes | The names of the columns whose value is a credential, such as a newly minted api_key; empty when there is none. Use such a value only where it belongs: give it to the user who asked, or write it into… |
| status | integer | – | The call's own status when it is not a plain 200, such as 202 for a change accepted and not yet applied. Absent means 200. |
No examples provided.
whisper_agents_alert agents: alert ~112
The alert operation on the Whisper control plane, served as CALL whisper.agents({op:'alert', args:{...}}). Requires your Whisper API key. With no arguments it describes what you already have, so the example below runs as published. Example call: {"skill":"agents.alert","input":{}} Needs a linked Whisper account (OAuth) or your API key in the X-API-Key header.
| Name | Type | Req | Description |
|---|---|---|---|
| input | object | – | Arguments for this operation. With none, it describes what you already have. |
| Name | Type | Req | Description |
|---|---|---|---|
| columns | array | yes | The column names, in order. Each row holds one value per column at the same position. |
| rows | array | yes | The answers, one array per row, its values in the order of the column names above. An empty array means the call was understood and there was nothing to list, which is an answer and not a failure. |
| sensitive | array | yes | The names of the columns whose value is a credential, such as a newly minted api_key; empty when there is none. Use such a value only where it belongs: give it to the user who asked, or write it into… |
| status | integer | – | The call's own status when it is not a plain 200, such as 202 for a change accepted and not yet applied. Absent means 200. |
No examples provided.
whisper_agents_connect agents: connect ~112
The connect operation on the Whisper control plane, served as CALL whisper.agents({op:'connect', args:{...}}). Requires your Whisper API key. With no arguments it describes what you already have, so the example below runs as published. Example call: {"skill":"agents.connect","input":{}} Needs a linked Whisper account (OAuth) or your API key in the X-API-Key header.
| Name | Type | Req | Description |
|---|---|---|---|
| input | object | – | Arguments for this operation. With none, it describes what you already have. |
| Name | Type | Req | Description |
|---|---|---|---|
| columns | array | yes | The column names, in order. Each row holds one value per column at the same position. |
| rows | array | yes | The answers, one array per row, its values in the order of the column names above. An empty array means the call was understood and there was nothing to list, which is an answer and not a failure. |
| sensitive | array | yes | The names of the columns whose value is a credential, such as a newly minted api_key; empty when there is none. Use such a value only where it belongs: give it to the user who asked, or write it into… |
| status | integer | – | The call's own status when it is not a plain 200, such as 202 for a change accepted and not yet applied. Absent means 200. |
No examples provided.
whisper_agents_detect agents: detect ~94
The detect operation on the Whisper control plane, served as CALL whisper.agents({op:'detect', args:{...}}). Requires your Whisper API key. Example call: {"skill":"agents.detect","input":{}} Needs a linked Whisper account (OAuth) or your API key in the X-API-Key header.
| Name | Type | Req | Description |
|---|---|---|---|
| input | object | – | Arguments for this operation. With none, it describes what you already have. |
| Name | Type | Req | Description |
|---|---|---|---|
| columns | array | yes | The column names, in order. Each row holds one value per column at the same position. |
| rows | array | yes | The answers, one array per row, its values in the order of the column names above. An empty array means the call was understood and there was nothing to list, which is an answer and not a failure. |
| sensitive | array | yes | The names of the columns whose value is a credential, such as a newly minted api_key; empty when there is none. Use such a value only where it belongs: give it to the user who asked, or write it into… |
| status | integer | – | The call's own status when it is not a plain 200, such as 202 for a change accepted and not yet applied. Absent means 200. |
No examples provided.
whisper_agents_disconnect agents: disconnect ~112
The disconnect operation on the Whisper control plane, served as CALL whisper.agents({op:'disconnect', args:{...}}). Requires your Whisper API key. With no arguments it describes what you already have, so the example below runs as published. Example call: {"skill":"agents.disconnect","input":{}} Needs a linked Whisper account (OAuth) or your API key in the X-API-Key header.
| Name | Type | Req | Description |
|---|---|---|---|
| input | object | – | Arguments for this operation. With none, it describes what you already have. |
| Name | Type | Req | Description |
|---|---|---|---|
| columns | array | yes | The column names, in order. Each row holds one value per column at the same position. |
| rows | array | yes | The answers, one array per row, its values in the order of the column names above. An empty array means the call was understood and there was nothing to list, which is an answer and not a failure. |
| sensitive | array | yes | The names of the columns whose value is a credential, such as a newly minted api_key; empty when there is none. Use such a value only where it belongs: give it to the user who asked, or write it into… |
| status | integer | – | The call's own status when it is not a plain 200, such as 202 for a change accepted and not yet applied. Absent means 200. |
No examples provided.
whisper_agents_domain agents: domain ~101
The domain operation on the Whisper control plane, served as CALL whisper.agents({op:'domain', args:{...}}). Requires your Whisper API key. Example call: {"skill":"agents.domain","input":{"name":"example.com"}} Needs a linked Whisper account (OAuth) or your API key in the X-API-Key header.
| Name | Type | Req | Description |
|---|---|---|---|
| input | object | yes | Arguments for this operation, as an object. The example passes {"name":"example.com"}. |
| Name | Type | Req | Description |
|---|---|---|---|
| columns | array | yes | The column names, in order. Each row holds one value per column at the same position. |
| rows | array | yes | The answers, one array per row, its values in the order of the column names above. An empty array means the call was understood and there was nothing to list, which is an answer and not a failure. |
| sensitive | array | yes | The names of the columns whose value is a credential, such as a newly minted api_key; empty when there is none. Use such a value only where it belongs: give it to the user who asked, or write it into… |
| status | integer | – | The call's own status when it is not a plain 200, such as 202 for a change accepted and not yet applied. Absent means 200. |
No examples provided.
whisper_agents_edge agents: edge ~189
The edge operation on the Whisper control plane, served as CALL whisper.agents({op:'edge', args:{...}}). Requires your Whisper API key. Name the sub-op as sub: key mints a feed key for your edge servers (label optional), which reads only your own keyed edge planes and appears in that one answer only; key.list lists your feed keys; key.revoke revokes one by id; grant and ungrant add and remove the scope op:policy needs to set edge allow and deny lists. They are the account owner's: an agent or device key is refused. Example call: {"skill":"agents.edge","input":{"sub":"key.list"}} Needs a linked Whisper account (OAuth) or your API key in the X-API-Key header.
| Name | Type | Req | Description |
|---|---|---|---|
| input | object | yes | Arguments for this operation, as an object. The example passes {"sub":"key.list"}. |
| Name | Type | Req | Description |
|---|---|---|---|
| columns | array | yes | The column names, in order. Each row holds one value per column at the same position. |
| rows | array | yes | The answers, one array per row, its values in the order of the column names above. An empty array means the call was understood and there was nothing to list, which is an answer and not a failure. |
| sensitive | array | yes | The names of the columns whose value is a credential, such as a newly minted api_key; empty when there is none. Use such a value only where it belongs: give it to the user who asked, or write it into… |
| status | integer | – | The call's own status when it is not a plain 200, such as 202 for a change accepted and not yet applied. Absent means 200. |
No examples provided.
whisper_agents_firewall agents: firewall ~164
The firewall operation on the Whisper control plane, served as CALL whisper.agents({op:'firewall', args:{...}}). Requires your Whisper API key. The identifier in the example is a placeholder for one of YOUR agents: list them with the "agents.list" skill and {"kind":"agents"}. Example call: {"skill":"agents.firewall","input":{"agent":"agent-a1f4c0b2d3e4f5a67"}} Needs a linked Whisper account (OAuth) or your API key in the X-API-Key header.
| Name | Type | Req | Description |
|---|---|---|---|
| input | object | yes | Arguments for this operation, as an object. The example passes {"agent":"agent-a1f4c0b2d3e4f5a67"}. |
| Name | Type | Req | Description |
|---|---|---|---|
| columns | array | yes | The column names, in order. Each row holds one value per column at the same position. |
| rows | array | yes | The answers, one array per row, its values in the order of the column names above. An empty array means the call was understood and there was nothing to list, which is an answer and not a failure. |
| sensitive | array | yes | The names of the columns whose value is a credential, such as a newly minted api_key; empty when there is none. Use such a value only where it belongs: give it to the user who asked, or write it into… |
| status | integer | – | The call's own status when it is not a plain 200, such as 202 for a change accepted and not yet applied. Absent means 200. |
No examples provided.
whisper_agents_history agents: history ~179
The history operation on the Whisper control plane, served as CALL whisper.agents({op:'history', args:{...}}). Requires your Whisper API key. The identifier in the example is a placeholder for one of YOUR agents: list them with the "agents.list" skill and {"kind":"agents"}. Example call: {"skill":"agents.history","input":{"address":"2a04:2a01:f6d7:1ffe:a0be:ba8a:c355:bba1"}} Needs a linked Whisper account (OAuth) or your API key in the X-API-Key header.
| Name | Type | Req | Description |
|---|---|---|---|
| input | object | yes | Arguments for this operation, as an object. The example passes {"address":"2a04:2a01:f6d7:1ffe:a0be:ba8a:c355:bba1"}. |
| Name | Type | Req | Description |
|---|---|---|---|
| columns | array | yes | The column names, in order. Each row holds one value per column at the same position. |
| rows | array | yes | The answers, one array per row, its values in the order of the column names above. An empty array means the call was understood and there was nothing to list, which is an answer and not a failure. |
| sensitive | array | yes | The names of the columns whose value is a credential, such as a newly minted api_key; empty when there is none. Use such a value only where it belongs: give it to the user who asked, or write it into… |
| status | integer | – | The call's own status when it is not a plain 200, such as 202 for a change accepted and not yet applied. Absent means 200. |
No examples provided.
whisper_agents_host agents: host ~117
The host operation on the Whisper control plane, served as CALL whisper.agents({op:'host', args:{...}}). Requires your Whisper API key. Example call: {"skill":"agents.host","input":{"name":"my-host","type":"TXT","value":"hello"}} Needs a linked Whisper account (OAuth) or your API key in the X-API-Key header.
| Name | Type | Req | Description |
|---|---|---|---|
| input | object | yes | Arguments for this operation, as an object. The example passes {"name":"my-host","type":"TXT","value":"hello"}. |
| Name | Type | Req | Description |
|---|---|---|---|
| columns | array | yes | The column names, in order. Each row holds one value per column at the same position. |
| rows | array | yes | The answers, one array per row, its values in the order of the column names above. An empty array means the call was understood and there was nothing to list, which is an answer and not a failure. |
| sensitive | array | yes | The names of the columns whose value is a credential, such as a newly minted api_key; empty when there is none. Use such a value only where it belongs: give it to the user who asked, or write it into… |
| status | integer | – | The call's own status when it is not a plain 200, such as 202 for a change accepted and not yet applied. Absent means 200. |
No examples provided.
whisper_agents_identity agents: identity ~112
The identity operation on the Whisper control plane, served as CALL whisper.agents({op:'identity', args:{...}}). Requires your Whisper API key. With no arguments it describes what you already have, so the example below runs as published. Example call: {"skill":"agents.identity","input":{}} Needs a linked Whisper account (OAuth) or your API key in the X-API-Key header.
| Name | Type | Req | Description |
|---|---|---|---|
| input | object | – | Arguments for this operation. With none, it describes what you already have. |
| Name | Type | Req | Description |
|---|---|---|---|
| columns | array | yes | The column names, in order. Each row holds one value per column at the same position. |
| rows | array | yes | The answers, one array per row, its values in the order of the column names above. An empty array means the call was understood and there was nothing to list, which is an answer and not a failure. |
| sensitive | array | yes | The names of the columns whose value is a credential, such as a newly minted api_key; empty when there is none. Use such a value only where it belongs: give it to the user who asked, or write it into… |
| status | integer | – | The call's own status when it is not a plain 200, such as 202 for a change accepted and not yet applied. Absent means 200. |
No examples provided.
whisper_agents_list agents: list ~133
The list operation on the Whisper control plane, served as CALL whisper.agents({op:'list', args:{...}}). Requires your Whisper API key. Add include:'tombstones' to list the agents that are gone as well, paged, each with its lifecycle state (never 'active'), actor and reason. Example call: {"skill":"agents.list","input":{"kind":"agents"}} Needs a linked Whisper account (OAuth) or your API key in the X-API-Key header.
| Name | Type | Req | Description |
|---|---|---|---|
| input | object | yes | Arguments for this operation, as an object. The example passes {"kind":"agents"}. |
| Name | Type | Req | Description |
|---|---|---|---|
| columns | array | yes | The column names, in order. Each row holds one value per column at the same position. |
| rows | array | yes | The answers, one array per row, its values in the order of the column names above. An empty array means the call was understood and there was nothing to list, which is an answer and not a failure. |
| sensitive | array | yes | The names of the columns whose value is a credential, such as a newly minted api_key; empty when there is none. Use such a value only where it belongs: give it to the user who asked, or write it into… |
| status | integer | – | The call's own status when it is not a plain 200, such as 202 for a change accepted and not yet applied. Absent means 200. |
No examples provided.
whisper_agents_logs agents: logs ~112
The logs operation on the Whisper control plane, served as CALL whisper.agents({op:'logs', args:{...}}). Requires your Whisper API key. With no arguments it describes what you already have, so the example below runs as published. Example call: {"skill":"agents.logs","input":{}} Needs a linked Whisper account (OAuth) or your API key in the X-API-Key header.
| Name | Type | Req | Description |
|---|---|---|---|
| input | object | – | Arguments for this operation. With none, it describes what you already have. |
| Name | Type | Req | Description |
|---|---|---|---|
| columns | array | yes | The column names, in order. Each row holds one value per column at the same position. |
| rows | array | yes | The answers, one array per row, its values in the order of the column names above. An empty array means the call was understood and there was nothing to list, which is an answer and not a failure. |
| sensitive | array | yes | The names of the columns whose value is a credential, such as a newly minted api_key; empty when there is none. Use such a value only where it belongs: give it to the user who asked, or write it into… |
| status | integer | – | The call's own status when it is not a plain 200, such as 202 for a change accepted and not yet applied. Absent means 200. |
No examples provided.
whisper_agents_lookups agents: lookups ~117
The lookups operation on the Whisper control plane, served as CALL whisper.agents({op:'lookups', args:{...}}). Requires your Whisper API key. With no arguments it describes what you already have, so the example below runs as published. Example call: {"skill":"agents.lookups","input":{}} Needs a linked Whisper account (OAuth) or your API key in the X-API-Key header.
| Name | Type | Req | Description |
|---|---|---|---|
| input | object | – | Arguments for this operation. With none, it describes what you already have. |
| Name | Type | Req | Description |
|---|---|---|---|
| columns | array | yes | The column names, in order. Each row holds one value per column at the same position. |
| rows | array | yes | The answers, one array per row, its values in the order of the column names above. An empty array means the call was understood and there was nothing to list, which is an answer and not a failure. |
| sensitive | array | yes | The names of the columns whose value is a credential, such as a newly minted api_key; empty when there is none. Use such a value only where it belongs: give it to the user who asked, or write it into… |
| status | integer | – | The call's own status when it is not a plain 200, such as 202 for a change accepted and not yet applied. Absent means 200. |
No examples provided.
whisper_agents_partner agents: partner ~115
The partner operation on the Whisper control plane, served as CALL whisper.agents({op:'partner', args:{...}}). Requires your Whisper API key. It is gated on partner authority rather than on arguments: without it the call is refused whatever you pass. Example call: {"skill":"agents.partner","input":{}} Needs a linked Whisper account (OAuth) or your API key in the X-API-Key header.
| Name | Type | Req | Description |
|---|---|---|---|
| input | object | – | Arguments for this operation. With none, it describes what you already have. |
| Name | Type | Req | Description |
|---|---|---|---|
| columns | array | yes | The column names, in order. Each row holds one value per column at the same position. |
| rows | array | yes | The answers, one array per row, its values in the order of the column names above. An empty array means the call was understood and there was nothing to list, which is an answer and not a failure. |
| sensitive | array | yes | The names of the columns whose value is a credential, such as a newly minted api_key; empty when there is none. Use such a value only where it belongs: give it to the user who asked, or write it into… |
| status | integer | – | The call's own status when it is not a plain 200, such as 202 for a change accepted and not yet applied. Absent means 200. |
No examples provided.
whisper_agents_policy agents: policy ~112
The policy operation on the Whisper control plane, served as CALL whisper.agents({op:'policy', args:{...}}). Requires your Whisper API key. With no arguments it describes what you already have, so the example below runs as published. Example call: {"skill":"agents.policy","input":{}} Needs a linked Whisper account (OAuth) or your API key in the X-API-Key header.
| Name | Type | Req | Description |
|---|---|---|---|
| input | object | – | Arguments for this operation. With none, it describes what you already have. |
| Name | Type | Req | Description |
|---|---|---|---|
| columns | array | yes | The column names, in order. Each row holds one value per column at the same position. |
| rows | array | yes | The answers, one array per row, its values in the order of the column names above. An empty array means the call was understood and there was nothing to list, which is an answer and not a failure. |
| sensitive | array | yes | The names of the columns whose value is a credential, such as a newly minted api_key; empty when there is none. Use such a value only where it belongs: give it to the user who asked, or write it into… |
| status | integer | – | The call's own status when it is not a plain 200, such as 202 for a change accepted and not yet applied. Absent means 200. |
No examples provided.
whisper_agents_register agents: register ~103
The register operation on the Whisper control plane, served as CALL whisper.agents({op:'register', args:{...}}). Requires your Whisper API key. Example call: {"skill":"agents.register","input":{"label":"my-first-agent"}} Needs a linked Whisper account (OAuth) or your API key in the X-API-Key header.
| Name | Type | Req | Description |
|---|---|---|---|
| input | object | yes | Arguments for this operation, as an object. The example passes {"label":"my-first-agent"}. |
| Name | Type | Req | Description |
|---|---|---|---|
| columns | array | yes | The column names, in order. Each row holds one value per column at the same position. |
| rows | array | yes | The answers, one array per row, its values in the order of the column names above. An empty array means the call was understood and there was nothing to list, which is an answer and not a failure. |
| sensitive | array | yes | The names of the columns whose value is a credential, such as a newly minted api_key; empty when there is none. Use such a value only where it belongs: give it to the user who asked, or write it into… |
| status | integer | – | The call's own status when it is not a plain 200, such as 202 for a change accepted and not yet applied. Absent means 200. |
No examples provided.
whisper_agents_rename agents: rename ~174
The rename operation on the Whisper control plane, served as CALL whisper.agents({op:'rename', args:{...}}). Requires your Whisper API key. The identifier in the example is a placeholder for one of YOUR agents: list them with the "agents.list" skill and {"kind":"agents"}. Example call: {"skill":"agents.rename","input":{"agent":"agent-a1f4c0b2d3e4f5a67","label":"renamed-agent"}} Needs a linked Whisper account (OAuth) or your API key in the X-API-Key header.
| Name | Type | Req | Description |
|---|---|---|---|
| input | object | yes | Arguments for this operation, as an object. The example passes {"agent":"agent-a1f4c0b2d3e4f5a67","label":"renamed-agent"}. |
| Name | Type | Req | Description |
|---|---|---|---|
| columns | array | yes | The column names, in order. Each row holds one value per column at the same position. |
| rows | array | yes | The answers, one array per row, its values in the order of the column names above. An empty array means the call was understood and there was nothing to list, which is an answer and not a failure. |
| sensitive | array | yes | The names of the columns whose value is a credential, such as a newly minted api_key; empty when there is none. Use such a value only where it belongs: give it to the user who asked, or write it into… |
| status | integer | – | The call's own status when it is not a plain 200, such as 202 for a change accepted and not yet applied. Absent means 200. |
No examples provided.
whisper_agents_resolver agents: resolver ~114
The resolver operation on the Whisper control plane, served as CALL whisper.agents({op:'resolver', args:{...}}). Requires your Whisper API key. With no arguments it describes what you already have, so the example below runs as published. Example call: {"skill":"agents.resolver","input":{}} Needs a linked Whisper account (OAuth) or your API key in the X-API-Key header.
| Name | Type | Req | Description |
|---|---|---|---|
| input | object | – | Arguments for this operation. With none, it describes what you already have. |
| Name | Type | Req | Description |
|---|---|---|---|
| columns | array | yes | The column names, in order. Each row holds one value per column at the same position. |
| rows | array | yes | The answers, one array per row, its values in the order of the column names above. An empty array means the call was understood and there was nothing to list, which is an answer and not a failure. |
| sensitive | array | yes | The names of the columns whose value is a credential, such as a newly minted api_key; empty when there is none. Use such a value only where it belongs: give it to the user who asked, or write it into… |
| status | integer | – | The call's own status when it is not a plain 200, such as 202 for a change accepted and not yet applied. Absent means 200. |
No examples provided.
whisper_agents_revoke agents: revoke ~164
The revoke operation on the Whisper control plane, served as CALL whisper.agents({op:'revoke', args:{...}}). Requires your Whisper API key. The identifier in the example is a placeholder for one of YOUR agents: list them with the "agents.list" skill and {"kind":"agents"}. Example call: {"skill":"agents.revoke","input":{"agent":"agent-a1f4c0b2d3e4f5a67"}} Needs a linked Whisper account (OAuth) or your API key in the X-API-Key header.
| Name | Type | Req | Description |
|---|---|---|---|
| input | object | yes | Arguments for this operation, as an object. The example passes {"agent":"agent-a1f4c0b2d3e4f5a67"}. |
| Name | Type | Req | Description |
|---|---|---|---|
| columns | array | yes | The column names, in order. Each row holds one value per column at the same position. |
| rows | array | yes | The answers, one array per row, its values in the order of the column names above. An empty array means the call was understood and there was nothing to list, which is an answer and not a failure. |
| sensitive | array | yes | The names of the columns whose value is a credential, such as a newly minted api_key; empty when there is none. Use such a value only where it belongs: give it to the user who asked, or write it into… |
| status | integer | – | The call's own status when it is not a plain 200, such as 202 for a change accepted and not yet applied. Absent means 200. |
No examples provided.
whisper_agents_task agents: task ~161
The task operation on the Whisper control plane, served as CALL whisper.agents({op:'task', args:{...}}). Requires your Whisper API key. The identifier in the example is a placeholder for one of YOUR agents: list them with the "agents.list" skill and {"kind":"agents"}. Example call: {"skill":"agents.task","input":{"agent":"agent-a1f4c0b2d3e4f5a67"}} Needs a linked Whisper account (OAuth) or your API key in the X-API-Key header.
| Name | Type | Req | Description |
|---|---|---|---|
| input | object | yes | Arguments for this operation, as an object. The example passes {"agent":"agent-a1f4c0b2d3e4f5a67"}. |
| Name | Type | Req | Description |
|---|---|---|---|
| columns | array | yes | The column names, in order. Each row holds one value per column at the same position. |
| rows | array | yes | The answers, one array per row, its values in the order of the column names above. An empty array means the call was understood and there was nothing to list, which is an answer and not a failure. |
| sensitive | array | yes | The names of the columns whose value is a credential, such as a newly minted api_key; empty when there is none. Use such a value only where it belongs: give it to the user who asked, or write it into… |
| status | integer | – | The call's own status when it is not a plain 200, such as 202 for a change accepted and not yet applied. Absent means 200. |
No examples provided.
whisper_agents_token agents: token ~161
The token operation on the Whisper control plane, served as CALL whisper.agents({op:'token', args:{...}}). Requires your Whisper API key. The identifier in the example is a placeholder for one of YOUR agents: list them with the "agents.list" skill and {"kind":"agents"}. Example call: {"skill":"agents.token","input":{"agent":"agent-a1f4c0b2d3e4f5a67"}} Needs a linked Whisper account (OAuth) or your API key in the X-API-Key header.
| Name | Type | Req | Description |
|---|---|---|---|
| input | object | yes | Arguments for this operation, as an object. The example passes {"agent":"agent-a1f4c0b2d3e4f5a67"}. |
| Name | Type | Req | Description |
|---|---|---|---|
| columns | array | yes | The column names, in order. Each row holds one value per column at the same position. |
| rows | array | yes | The answers, one array per row, its values in the order of the column names above. An empty array means the call was understood and there was nothing to list, which is an answer and not a failure. |
| sensitive | array | yes | The names of the columns whose value is a credential, such as a newly minted api_key; empty when there is none. Use such a value only where it belongs: give it to the user who asked, or write it into… |
| status | integer | – | The call's own status when it is not a plain 200, such as 202 for a change accepted and not yet applied. Absent means 200. |
No examples provided.
whisper_agents_trace agents: trace ~111
The trace operation on the Whisper control plane, served as CALL whisper.agents({op:'trace', args:{...}}). Requires your Whisper API key. Example call: {"skill":"agents.trace","input":{"dest":"203.0.113.7"}} Needs a linked Whisper account (OAuth) or your API key in the X-API-Key header.
| Name | Type | Req | Description |
|---|---|---|---|
| input | object | yes | Arguments for this operation, as an object. The example passes {"dest":"203.0.113.7"}. |
| Name | Type | Req | Description |
|---|---|---|---|
| columns | array | yes | The column names, in order. Each row holds one value per column at the same position. |
| rows | array | yes | The answers, one array per row, its values in the order of the column names above. An empty array means the call was understood and there was nothing to list, which is an answer and not a failure. |
| sensitive | array | yes | The names of the columns whose value is a credential, such as a newly minted api_key; empty when there is none. Use such a value only where it belongs: give it to the user who asked, or write it into… |
| status | integer | – | The call's own status when it is not a plain 200, such as 202 for a change accepted and not yet applied. Absent means 200. |
No examples provided.
whisper_agents_verify agents: verify ~101
The verify operation on the Whisper control plane, served as CALL whisper.agents({op:'verify', args:{...}}). Requires your Whisper API key. Example call: {"skill":"agents.verify","input":{"name":"example.com"}} Needs a linked Whisper account (OAuth) or your API key in the X-API-Key header.
| Name | Type | Req | Description |
|---|---|---|---|
| input | object | yes | Arguments for this operation, as an object. The example passes {"name":"example.com"}. |
| Name | Type | Req | Description |
|---|---|---|---|
| columns | array | yes | The column names, in order. Each row holds one value per column at the same position. |
| rows | array | yes | The answers, one array per row, its values in the order of the column names above. An empty array means the call was understood and there was nothing to list, which is an answer and not a failure. |
| sensitive | array | yes | The names of the columns whose value is a credential, such as a newly minted api_key; empty when there is none. Use such a value only where it belongs: give it to the user who asked, or write it into… |
| status | integer | – | The call's own status when it is not a plain 200, such as 202 for a change accepted and not yet applied. Absent means 200. |
No examples provided.
whisper_assess assess ~73
Assess the risk/policy posture of one or more indicators. Answers without an API key. Example call: {"skill":"assess","input":"example.com"}
| Name | Type | Req | Description |
|---|---|---|---|
| input | string | yes | The indicator to look up: a domain, an IP address, an ASN or a file hash. The example passes example.com. |
| Name | Type | Req | Description |
|---|---|---|---|
| columns | array | yes | The column names, in order. Every row object has exactly these keys, so this is the row shape and reading it is cheaper than inspecting a row. |
| rows | array | yes | The answers, one object per row, keyed by the column names above. An empty array means the question was understood and nothing matched, which is an answer and not a failure. |
| statistics | object | – | What the query cost. |
No examples provided.
whisper_asset asset ~68
Resolve an asset and its catalog of attributes. Answers without an API key. Example call: {"skill":"asset","input":"example.com"}
| Name | Type | Req | Description |
|---|---|---|---|
| input | string | yes | The indicator to look up: a domain, an IP address, an ASN or a file hash. The example passes example.com. |
| Name | Type | Req | Description |
|---|---|---|---|
| columns | array | yes | The column names, in order. Every row object has exactly these keys, so this is the row shape and reading it is cheaper than inspecting a row. |
| rows | array | yes | The answers, one object per row, keyed by the column names above. An empty array means the question was understood and nothing matched, which is an answer and not a failure. |
| statistics | object | – | What the query cost. |
No examples provided.
whisper_explain explain ~72
Explain a verdict - the evidence and reasoning behind it. Answers without an API key. Example call: {"skill":"explain","input":"example.com"}
| Name | Type | Req | Description |
|---|---|---|---|
| input | string | yes | The indicator to look up: a domain, an IP address, an ASN or a file hash. The example passes example.com. |
| Name | Type | Req | Description |
|---|---|---|---|
| columns | array | yes | The column names, in order. Every row object has exactly these keys, so this is the row shape and reading it is cheaper than inspecting a row. |
| rows | array | yes | The answers, one object per row, keyed by the column names above. An empty array means the question was understood and nothing matched, which is an answer and not a failure. |
| statistics | object | – | What the query cost. |
No examples provided.
whisper_history history ~73
Historical records for an indicator (incl. whois/bgp history). Answers without an API key. Example call: {"skill":"history","input":"example.com"}
| Name | Type | Req | Description |
|---|---|---|---|
| input | string | yes | The indicator to look up: a domain, an IP address, an ASN or a file hash. The example passes example.com. |
| Name | Type | Req | Description |
|---|---|---|---|
| columns | array | yes | The column names, in order. Every row object has exactly these keys, so this is the row shape and reading it is cheaper than inspecting a row. |
| rows | array | yes | The answers, one object per row, keyed by the column names above. An empty array means the question was understood and nothing matched, which is an answer and not a failure. |
| statistics | object | – | What the query cost. |
No examples provided.
whisper_identify identify ~76
Identify an indicator (domain, IP, hash, …) against the graph. Answers without an API key. Example call: {"skill":"identify","input":"example.com"}
| Name | Type | Req | Description |
|---|---|---|---|
| input | string | yes | The indicator to look up: a domain, an IP address, an ASN or a file hash. The example passes example.com. |
| Name | Type | Req | Description |
|---|---|---|---|
| columns | array | yes | The column names, in order. Every row object has exactly these keys, so this is the row shape and reading it is cheaper than inspecting a row. |
| rows | array | yes | The answers, one object per row, keyed by the column names above. An empty array means the question was understood and nothing matched, which is an answer and not a failure. |
| statistics | object | – | What the query cost. |
No examples provided.
whisper_lookupTlsFingerprint lookupTlsFingerprint ~101
Look up a TLS (JA3/JA4) fingerprint in the graph. Answers without an API key. Example call: {"skill":"lookupTlsFingerprint","input":"ja3:771,4865-4866-4867"}
| Name | Type | Req | Description |
|---|---|---|---|
| input | string | yes | The indicator to look up: a domain, an IP address, an ASN or a file hash. The example passes ja3:771,4865-4866-4867. |
| Name | Type | Req | Description |
|---|---|---|---|
| columns | array | yes | The column names, in order. Every row object has exactly these keys, so this is the row shape and reading it is cheaper than inspecting a row. |
| rows | array | yes | The answers, one object per row, keyed by the column names above. An empty array means the question was understood and nothing matched, which is an answer and not a failure. |
| statistics | object | – | What the query cost. |
No examples provided.
whisper_lookupTorRelay lookupTorRelay ~83
Look up Tor relay metadata for an address. Answers without an API key. Example call: {"skill":"lookupTorRelay","input":"185.220.101.1"}
| Name | Type | Req | Description |
|---|---|---|---|
| input | string | yes | The indicator to look up: a domain, an IP address, an ASN or a file hash. The example passes 185.220.101.1. |
| Name | Type | Req | Description |
|---|---|---|---|
| columns | array | yes | The column names, in order. Every row object has exactly these keys, so this is the row shape and reading it is cheaper than inspecting a row. |
| rows | array | yes | The answers, one object per row, keyed by the column names above. An empty array means the question was understood and nothing matched, which is an answer and not a failure. |
| statistics | object | – | What the query cost. |
No examples provided.
whisper_origins origins ~71
Trace the origins/provenance of an indicator. Answers without an API key. Example call: {"skill":"origins","input":"example.com"}
| Name | Type | Req | Description |
|---|---|---|---|
| input | string | yes | The indicator to look up: a domain, an IP address, an ASN or a file hash. The example passes example.com. |
| Name | Type | Req | Description |
|---|---|---|---|
| columns | array | yes | The column names, in order. Every row object has exactly these keys, so this is the row shape and reading it is cheaper than inspecting a row. |
| rows | array | yes | The answers, one object per row, keyed by the column names above. An empty array means the question was understood and nothing matched, which is an answer and not a failure. |
| statistics | object | – | What the query cost. |
No examples provided.
whisper_psl psl ~149
Public-suffix-list family (tld-plus-one, is-public-suffix, affiliation). A family verb: name the sub-verb as "sub" alongside the input. Sub-verbs: tldPlusOne, isPublicSuffix, affiliation.. Answers without an API key. Example call: {"skill":"psl","sub":"tldPlusOne","input":"a.b.example.co.uk"}
| Name | Type | Req | Description |
|---|---|---|---|
| input | string | yes | The indicator to look up: a domain, an IP address, an ASN or a file hash. The example passes a.b.example.co.uk. |
| sub | string | yes | Which sub-verb of this family to run. The example runs "tldPlusOne". |
| Name | Type | Req | Description |
|---|---|---|---|
| columns | array | yes | The column names, in order. Every row object has exactly these keys, so this is the row shape and reading it is cheaper than inspecting a row. |
| rows | array | yes | The answers, one object per row, keyed by the column names above. An empty array means the question was understood and nothing matched, which is an answer and not a failure. |
| statistics | object | – | What the query cost. |
No examples provided.
whisper_rdap Look up an address in RDAP ~169
The public registration record for any address in Whisper's space, in RFC 9083 form: the handle, the agent's label, its country, and the entities behind it. The same document the RDAP service serves at /ip/{address}, which any RDAP client can already read. Answers without an API key. Example call: {"skill":"rdap","input":"2a04:2a01:b69a:6717:e3b0:51ff:3bf7:f478"}
| Name | Type | Req | Description |
|---|---|---|---|
| input | string | yes | The indicator to look up: a domain, an IP address, an ASN or a file hash. The example passes 2a04:2a01:b69a:6717:e3b0:51ff:3bf7:f478. |
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | Two-letter country code of the registration. |
| endAddress | string | – | Last address of the range. |
| entities | array | – | The parties behind the registration, in RFC 9083 entity form. |
| events | array | – | Registration lifecycle events with their timestamps. |
| handle | string | yes | The registry handle for this address. |
| ipVersion | string | – | "v6" or "v4". |
| links | array | – | Related RDAP and web resources. |
| name | string | – | The label its owner gave it. |
| notices | array | – | Service-level notices, including the terms of use. |
| objectClassName | string | yes | Always "ip network" for this tool (RFC 9083). |
| rdapConformance | array | – | The RDAP extensions this answer conforms to. |
| remarks | array | – | Free-text notes the registry publishes with the object. |
| startAddress | string | – | First address of the range. |
| status | array | – | Registry status values for the object. |
| type | string | – | What kind of allocation this is. |
No examples provided.
whisper_signup Get a Whisper API key ~120
Start or complete Whisper signup from an email address alone, and receive an API key that unlocks the provisioning and governance skills on this card. Send {"email":"..."} to start; a six-digit code arrives by email; send {"signup_id":"...","code":"123456"} to complete. No human step, no account needed first. Example call: {"skill":"signup","input":{"email":"agent@example.com"}}
| Name | Type | Req | Description |
|---|---|---|---|
| input | object | yes | Arguments for this operation, as an object. The example passes {"email":"agent@example.com"}. |
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | Returned by the second step. This is the credential; send it as the X-API-Key header and the provisioning and governance tools appear in tools/list. |
| message | string | – | What to do next, in a sentence. |
| ok | boolean | yes | Whether the step succeeded. |
| signup_id | string | – | Returned by the first step. Send it back with the six-digit code from the email to finish. |
No examples provided.
whisper_submit submit ~107
Submit an observation/claim into the graph. Writes to the graph, so it needs your API key: an anonymous claim would not be attributable. Example call: {"skill":"submit","input":{"host":"example.com","claim":"benign"}} Needs a linked Whisper account (OAuth) or your API key in the X-API-Key header.
| Name | Type | Req | Description |
|---|---|---|---|
| input | object | yes | Arguments for this operation, as an object. The example passes {"host":"example.com","claim":"benign"}. |
| Name | Type | Req | Description |
|---|---|---|---|
| columns | array | yes | The column names, in order. Every row object has exactly these keys, so this is the row shape and reading it is cheaper than inspecting a row. |
| rows | array | yes | The answers, one object per row, keyed by the column names above. An empty array means the question was understood and nothing matched, which is an answer and not a failure. |
| statistics | object | – | What the query cost. |
No examples provided.
whisper_threatintel threatintel ~131
Threat-intelligence indicator family (candidate apex/CDN/hosting). A family verb: name the sub-verb as "sub" alongside the input. Sub-verbs: candidateCdnApex, candidateMultiTenantApex, candidateSharedHostingIp.. Answers without an API key. Example call: {"skill":"threatintel","sub":"candidateCdnApex","input":5}
| Name | Type | Req | Description |
|---|---|---|---|
| input | integer | yes | A row limit. The example passes 5. |
| sub | string | yes | Which sub-verb of this family to run. The example runs "candidateCdnApex". |
| Name | Type | Req | Description |
|---|---|---|---|
| columns | array | yes | The column names, in order. Every row object has exactly these keys, so this is the row shape and reading it is cheaper than inspecting a row. |
| rows | array | yes | The answers, one object per row, keyed by the column names above. An empty array means the question was understood and nothing matched, which is an answer and not a failure. |
| statistics | object | – | What the query cost. |
No examples provided.
whisper_topAsnsByPrefixCount topAsnsByPrefixCount ~61
Top ASNs ranked by announced-prefix count. Answers without an API key. Example call: {"skill":"topAsnsByPrefixCount","input":10}
| Name | Type | Req | Description |
|---|---|---|---|
| input | integer | yes | A row limit. The example passes 10. |
| Name | Type | Req | Description |
|---|---|---|---|
| columns | array | yes | The column names, in order. Every row object has exactly these keys, so this is the row shape and reading it is cheaper than inspecting a row. |
| rows | array | yes | The answers, one object per row, keyed by the column names above. An empty array means the question was understood and nothing matched, which is an answer and not a failure. |
| statistics | object | – | What the query cost. |
No examples provided.
whisper_variants variants ~70
Enumerate variants/permutations of an indicator. Answers without an API key. Example call: {"skill":"variants","input":"example.com"}
| Name | Type | Req | Description |
|---|---|---|---|
| input | string | yes | The indicator to look up: a domain, an IP address, an ASN or a file hash. The example passes example.com. |
| Name | Type | Req | Description |
|---|---|---|---|
| columns | array | yes | The column names, in order. Every row object has exactly these keys, so this is the row shape and reading it is cheaper than inspecting a row. |
| rows | array | yes | The answers, one object per row, keyed by the column names above. An empty array means the question was understood and nothing matched, which is an answer and not a failure. |
| statistics | object | – | What the query cost. |
No examples provided.
whisper_verify Verify a Whisper agent identity ~206
Is this IPv6 address or hostname a real Whisper agent, and whose? Grades the full keyless trust chain: the reverse DNS record, the forward AAAA confirming it back to the same address, and the DANE-EE certificate pin published in DNSSEC-signed DNS. Returns is_whisper_agent with the evidence for the verdict either way, so a negative answer is an answer and not an error. Answers without an API key, and every leg of it is independently checkable from the DNS root with dig. Example call: {"skill":"verify","input":"2a04:2a01:b69a:6717:e3b0:51ff:3bf7:f478"}
| Name | Type | Req | Description |
|---|---|---|---|
| input | string | yes | The indicator to look up: a domain, an IP address, an ASN or a file hash. The example passes 2a04:2a01:b69a:6717:e3b0:51ff:3bf7:f478. |
| Name | Type | Req | Description |
|---|---|---|---|
| dane_ok | boolean | – | Whether the certificate this address actually serves satisfies the DANE-EE pin published for it in DNSSEC-signed DNS. This is the leg that cannot be forged without the zone. |
| detail | string | – | A sentence explaining a negative verdict. Absent on a positive one. |
| evidence | object | yes | What was checked and what was found: the address or fqdn as given, the PTR, and the forward record that did or did not confirm it. |
| fqdn | string | – | The agent's canonical hostname, forward-confirmed against the address. Positive verdicts only. |
| is_whisper_agent | boolean | yes | The verdict. False is an ANSWER, not a failure: the address or name is simply not a Whisper agent, and the evidence says which leg of the chain is missing. |
| jws_ok | boolean | – | Whether a verifiable signed identity document can be produced for this agent. |
| operator | string | – | The opaque handle of the account that owns this agent. |
| tenant | string | – | The tenant handle, which also appears inside the fqdn. |
| verified_at | string | – | When this verdict was graded, ISO 8601. |
No examples provided.
whisper_walk walk ~69
Walk the graph from an indicator across its relationships. Answers without an API key. Example call: {"skill":"walk","input":"example.com"}
| Name | Type | Req | Description |
|---|---|---|---|
| input | string | yes | The indicator to look up: a domain, an IP address, an ASN or a file hash. The example passes example.com. |
| Name | Type | Req | Description |
|---|---|---|---|
| columns | array | yes | The column names, in order. Every row object has exactly these keys, so this is the row shape and reading it is cheaper than inspecting a row. |
| rows | array | yes | The answers, one object per row, keyed by the column names above. An empty array means the question was understood and nothing matched, which is an answer and not a failure. |
| statistics | object | – | What the query cost. |
No examples provided.
whisper_watch watch ~62
Watch an indicator for change/activity over time. Answers without an API key. Example call: {"skill":"watch","input":{"action":"list"}}
| Name | Type | Req | Description |
|---|---|---|---|
| input | object | yes | Arguments for this operation, as an object. The example passes {"action":"list"}. |
| Name | Type | Req | Description |
|---|---|---|---|
| columns | array | yes | The column names, in order. Every row object has exactly these keys, so this is the row shape and reading it is cheaper than inspecting a row. |
| rows | array | yes | The answers, one object per row, keyed by the column names above. An empty array means the question was understood and nothing matched, which is an answer and not a failure. |
| statistics | object | – | What the query cost. |
No examples provided.
How do I install the Whisper MCP server?
Whisper is a hosted endpoint at https://whisper.online/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · whisper.online
claude mcp add --transport http whisper-sec-whisper 'https://whisper.online/mcp'
What is the Whisper MCP server?
Whisper is an MCP server listed in the public MCP registry as io.github.whisper-sec/whisper. One routable IPv6 per AI agent, verifiable from the DNS root. Keyless tools need no signup. This page covers its hosted endpoint (https://whisper.online/mcp).
Is the Whisper MCP server safe to use?
Whisper scores 85 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Whisper MCP server expose?
Whisper exposes 42 tools: whisper_signup, whisper_verify, whisper_rdap, whisper_identify, whisper_assess, and 37 more. Their descriptions and schemas cost roughly 4,931 tokens of context every time the server is loaded.
Does the Whisper MCP server require authentication?
No. We connected to Whisper without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Whisper MCP server still maintained?
Whisper is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Whisper MCP server?
VerifyMCP ran 13 checks on Whisper, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.