Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/TodiwalaVentures/phantom-voices-apiWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/todiwalaventures/phantom-voices-api/phantom-voices)<a href="https://agentmods.dev/mcp/todiwalaventures/phantom-voices-api/phantom-voices"><img src="https://agentmods.dev/badge/mcp/todiwalaventures/phantom-voices-api/phantom-voices/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/todiwalaventures/phantom-voices-api/phantom-voices"><img src="https://agentmods.dev/badge/mcp/todiwalaventures/phantom-voices-api/phantom-voices.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
phantom-voices scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"phantom-voices": {
"command": "npx",
"args": [
"phantom-voices-mcp"
],
"env": {
"PHANTOM_VOICES_API_URL": "https://auto-business-agent.replit.app"
}
}
}What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 11 lines scan A b9de8afe7bdd
phantom-voices is an MCP server published in the GitHub repository TodiwalaVentures/phantom-voices-api (0 stars, last pushed 7mo ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other mcp servers, from other repositories
aegis
Auto-instrument AI agent frameworks with runtime security. One line to govern LangChain, CrewAI, OpenAI, Anthropic — injection blocking, PII masking, action policy, audit trail. Zero code changes. Runs locally from the agent-aegis Python package. Needs 1 environment variable to run.
acmi-mcp
Persistent agent memory via ACMI — Profile/Signals/Timeline. 16 tools on Upstash Redis. Runs locally from the @madezmedia/acmi-mcp npm package. Needs 2 environment variables to run.
agentguard47
Read-only MCP server for coding-agent traces, alerts, costs, usage, and budget health. Runs locally from the @agentguard47/mcp-server npm package. Needs 2 environment variables to run.
veriswarm-mcp
VeriSwarm MCP Server — Trust infrastructure for AI agents via Model Context Protocol. Runs locally from the veriswarm-mcp Python package.
speak-aloud
MCP server "speak-aloud" as configured in tsuru0805/speak-aloud-mcp. Launched with speak-aloud-mcp. Needs 4 environment variables to run.
mcp-server
Pay-per-call AI + web + on-chain tools over x402 (USDC on Base): LLM, SEO, extract, token safety. Runs locally from the @true402.dev/mcp-server npm package. Needs 3 environment variables to run.