Home / MCP registry index / io.github.whisper-sec/whisper
Whisper
io.github.whisper-sec/whisper in the official MCP registry.
Endpoint https://whisper.online/mcp. Source: github.com/whisper-sec/whisper-cli.
The registry describes it as: One routable IPv6 per AI agent, verifiable from the DNS root. Keyless tools need no signup.
We read its 17 tools on 2026-10-22. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
whisper_signup whisper_verify whisper_rdap whisper_identify whisper_assess whisper_walk whisper_watch whisper_explain whisper_variants whisper_origins whisper_history whisper_lookupTlsFingerprint whisper_lookupTorRelay whisper_asset whisper_threatintel whisper_psl whisper_topAsnsByPrefixCount
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-github-whisper-sec-whisper)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.