Whisper vs Hindsight
A side-by-side look at the Whisper and Hindsight MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Whisper for speech-to-text work as a local process; choose Hindsight for knowledge & memory as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Whisper when
- You need dedicated capabilities in the Speech-to-Text domain.
- You prefer a local stdio subprocess transport.
- You want tools like
whisper_verify, whisper_rdap, whisper_identify.
Choose Hindsight when
- You need dedicated capabilities in the Knowledge & Memory domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
HINDSIGHT_API_LLM_API_KEY, HINDSIGHT_API_LLM_PROVIDER, HINDSIGHT_DB_PASSWORD.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Speech-to-Text | Knowledge & Memory |
| Quality signal | 61/100 · Good | 57/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | API key required |
| Pricing | Not declared | Free |
| Required env vars | None listed | HINDSIGHT_API_LLM_API_KEYHINDSIGHT_API_LLM_PROVIDERHINDSIGHT_DB_PASSWORD |
| Verified owner | Community listing | Community listing |
| GitHub stars | 3 | 52,712 |
| Directory activity | 1 views 0 installs 0 upvotes | 14 views 0 installs 0 upvotes |
| Tools | 5 | Not listed |
| Full listing | View Whisper | View Hindsight |
Tools & capabilities
Whisper tools 5
whisper_verifyVerify whether an address or FQDN is a real Whisper agent and, if so, whose - running the full keyless trust chain (reverse-DNS + DANE-EE TLSA pin + DNSSEC + JWS identity doc). Returns the verdict as JSON. Use it to check any peer's claimed identity before trusting it. No API key needed.whisper_rdapFetch the RDAP record for a Whisper IPv6 /128 (the IP-anchored registration object: who operates the agent identity, since when, under which tenant). Returns RDAP JSON. Use it to look up ownership/registration facts about an address. No API key needed.whisper_identifyName the vendor and operator role behind a host or IP in one call. Resolves a host/IP to its canonical vendor, category and operator roles (DNS_OPERATOR / CDN / ORIGIN_AS / MAIL_RECEIVER) with a confidence band. No API key needed. Docs: https://www.whisper.security/docs/whisper-graph/procedures/identifywhisper_assessGet a labelled threat posture for a host or IP - malicious, benign, or unknown. Returns a posture label + severity band + sub-labels + coverage + evidence for an indicator; benign-allowlisted vs malicious-evidenced, never a bare score. No API key needed. Docs: https://www.whisper.security/docs/whisper-graph/procedureswhisper_explainScore an indicator against the threat feeds and explain exactly why. Threat-intel scorer: score + level + human explanation + the feeds it is listed in (feedId, weight, firstSeen/lastSeen). Two live forms: bare CALL explain($v) (full columns) and CALL whisper.explain($v) (restricted YIELD). No API key needed. Docs: https://www.whisper.security/docs/whisper-graph/procedures/explain
Hindsight tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Whisper
{
"mcpServers": {
"whisper": {
"command": "npx",
"args": [
"-y",
"@whisper-security/whisper-mcp"
]
}
}
}
Hindsight
{
"mcpServers": {
"vectorize-io-hindsight": {
"command": "npx",
"args": [
"-y",
"@vectorize-io/hindsight-coding-agents"
],
"env": {
"HINDSIGHT_API_LLM_API_KEY": "YOUR_HINDSIGHT_API_LLM_API_KEY_HERE",
"HINDSIGHT_API_LLM_PROVIDER": "YOUR_HINDSIGHT_API_LLM_PROVIDER_HERE",
"HINDSIGHT_DB_PASSWORD": "YOUR_HINDSIGHT_DB_PASSWORD_HERE"
}
}
}
}
Frequently asked questions
Whisper is categorized under Speech-to-Text and uses a local stdio subprocess. Hindsight belongs to Knowledge & Memory and uses a local stdio subprocess. Pick Whisper for speech-to-text work and Hindsight for knowledge & memory.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Whisper has no declared pricing — check the project's own site. Hindsight is listed as free. Auth: api key required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add whisper and vectorize-io-hindsight as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Whisper has a quality signal of 61/100 (Good) with 1 views, 0 installs and 3 GitHub stars. Hindsight has 57/100 (Good) with 14 views, 0 installs and 52,712 GitHub stars.