Whisper for Pi

Give a Pi coding agent a real, routable, verifiable Whisper network identity - keyless verify/RDAP, and the full control plane + /128 egress with a key.

Install

pi install npm:whisper-pi

Restart Pi. On start, the extension launches the whisper CLI's MCP server (whisper mcp) and registers its tools with Pi natively - nothing else to configure, no separate MCP bridge to add.

Prerequisite: the whisper CLI on your PATH - curl -fsSL https://get.whisper.online | sh (see https://get.whisper.online). If the CLI is not installed, the extension is a silent no-op (it never breaks Pi's startup).

Two-tier (auth optional)

The tool surface tracks your key state automatically, because it is exactly what whisper mcp advertises:

• No key: whisper_verify / whisper_rdap - verify whether any address or hostname is a real Whisper agent, and whose, and read its public RDAP. Works for everyone.
• With WHISPER_API_KEY (or whisper login): the full control plane (whisper_register, whisper_list, whisper_policy, whisper_logs, whisper_revoke, whisper_egress_config), /128 egress, and the security-graph tools (below).

Query the security graph

With a key, the tool surface also includes the whisper.security graph - 7.4B nodes (hostnames, IPs, ASNs, certs, threat intel), the same graph the Whisper resolver consults on every lookup. whisper_graph_query runs raw parameterised Cypher, and every catalog recipe is its own tool: whisper_identify, whisper_assess, whisper_variants, whisper_typosquat, whisper_attackSurface, ... 29 in all (graph tools ship in whisper CLI v0.130.0+). Just ask Pi:

Run whisper_assess on 8.8.8.8 and tell me its threat posture.

Docs: https://www.whisper.security/docs (the raw Cypher API: https://www.whisper.security/docs/cypher-api).

Prove the egress

whisper run curl -s https://api64.ipify.org    # prints the agent's /128
dig -x <that /128>                              # reverse-DNS -> the agent's Whisper hostname

Learn more: https://whisper.online