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/Engr-FaizanAli/text-to-speech-mcpWrote 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/engr-faizanali/text-to-speech-mcp/text-to-speech)<a href="https://agentmods.dev/mcp/engr-faizanali/text-to-speech-mcp/text-to-speech"><img src="https://agentmods.dev/badge/mcp/engr-faizanali/text-to-speech-mcp/text-to-speech/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/engr-faizanali/text-to-speech-mcp/text-to-speech"><img src="https://agentmods.dev/badge/mcp/engr-faizanali/text-to-speech-mcp/text-to-speech.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
text-to-speech 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 12d 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
{
"text-to-speech": {
"command": "uvx",
"args": [
"text-to-speech-mcp"
],
"env": {}
}
}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.
- 12d ago First seen · 9 lines scan A 57876da10fd9
text-to-speech is an MCP server published in the GitHub repository Engr-FaizanAli/text-to-speech-mcp (1 stars, last pushed 23d 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
mcp-web-validator
W3C HTML/CSS Validator and Technical SEO Audit MCP Server for AI coding assistants. Runs locally from the mcp-web-validator npm package.
agent-audit
Turn Lighthouse audits into coding-agent fix packs for Claude Code, Cursor, and Copilot. Runs locally from the @fullstackdegen/agent-audit npm package.
kilotest
Ensemble testing of web pages for accessibility, usability, and standards conformity. Remote server at kilotest.com.
mcp-fish
MCP Server for Fish TTS (Text-to-Speech) via AceDataCloud API. Runs locally from the mcp-fish Python package. Needs 1 environment variable to run.
isochrone
Berlin pedestrian isochrones: streets reachable on foot in N minutes (walk/stroller/wheelchair). Runs locally from the isochrone-mcp npm package.
open-state-camping
MCP server "open-state-camping" as configured in JCrossman/can-fed-camp-mcp. Runs packages/bundle/standalone/server.js with node.