ttsstt-mcp-server (ptbsare/ttsstt-mcp-server) is an MCP server listed on the M8ven Trust Index. It scores 67 out of 100, grade C. It declares 2 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
C
Caution
67/100

ttsstt-mcp-server

Enables speech-to-text and text-to-speech conversion using OpenAI-compatible APIs. Supports customizable models, voices, and output directories.

→ ptbsare/ttsstt-mcp-server· listed on glama

Caution. Specific findings reduced this grade. They are listed on the page. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

ptbsare

Source: Glama

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

⚡ Connect GitHub for Live Monitored

Install from

Glamanot scored here

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// key findings
🚨
Secret credentials may flow to a network call
2 flows detected: STT_API_KEY. We can’t prove the destination matches the brand the credential belongs to.
⚠️
Tool descriptions don’t match what handlers do
1 tool describes read intent but its handler mutates — tts (line 227: fs.writeFileSync(outputPath, Buffer.from(response.data)))
🔐
You'll be asked for 4 credentials: OPENAI_STT_API_KEY, OPENAI_TTS_API_KEY, STT_API_KEY, TTS_API_KEY
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
🔐 secretOPENAI_STT_API_KEYOPENAI_STT_URL, , OPENAI_STT_MODEL, OPENAI_STT_RESPONSE_FORMAT
configOPENAI_STT_MODELOPENAI_STT_URL, OPENAI_STT_API_KEY, , OPENAI_STT_RESPONSE_FORMAT
configOPENAI_STT_RESPONSE_FORMATOPENAI_STT_URL, OPENAI_STT_API_KEY, OPENAI_STT_MODEL,
configOPENAI_STT_URL, OPENAI_STT_API_KEY, OPENAI_STT_MODEL, OPENAI_STT_RESPONSE_FORMAT
🔐 secretOPENAI_TTS_API_KEYOPENAI_TTS_URL, , OPENAI_TTS_MODEL, OPENAI_TTS_VOICE, OPENAI_TTS_SPEED, OPENAI_TTS_PITCH, OPENAI_TTS_OUTPUT_DIR
configOPENAI_TTS_MODELOPENAI_TTS_URL, OPENAI_TTS_API_KEY, , OPENAI_TTS_VOICE, OPENAI_TTS_SPEED, OPENAI_TTS_PITCH, OPENAI_TTS_OUTPUT_DIR
configOPENAI_TTS_PITCHOPENAI_TTS_URL, OPENAI_TTS_API_KEY, OPENAI_TTS_MODEL, OPENAI_TTS_VOICE, OPENAI_TTS_SPEED, , OPENAI_TTS_OUTPUT_DIR
configOPENAI_TTS_SPEEDOPENAI_TTS_URL, OPENAI_TTS_API_KEY, OPENAI_TTS_MODEL, OPENAI_TTS_VOICE, , OPENAI_TTS_PITCH, OPENAI_TTS_OUTPUT_DIR
configOPENAI_TTS_URL, OPENAI_TTS_API_KEY, OPENAI_TTS_MODEL, OPENAI_TTS_VOICE, OPENAI_TTS_SPEED, OPENAI_TTS_PITCH, OPENAI_TTS_OUTPUT_DIR
configOPENAI_TTS_VOICEOPENAI_TTS_URL, OPENAI_TTS_API_KEY, OPENAI_TTS_MODEL, , OPENAI_TTS_SPEED, OPENAI_TTS_PITCH, OPENAI_TTS_OUTPUT_DIR
🔐 secretSTT_API_KEY(required)
configSTT_MODELwhisper-1
configSTT_RESPONSE_FORMATjson
configSTT_URL(required)
🔐 secretTTS_API_KEY(required)
configTTS_MODELtts-1
configTTS_OUTPUT_DIR./tts_output
configTTS_PITCH1.0
configTTS_SPEED1.0
configTTS_URL(required)
configTTS_VOICEalloy
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

2/2 tools missing one or more hints — stt (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); tts (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint). OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Descriptions match behaviour

1 tool describes read intent but its handler mutates — tts (line 227: fs.writeFileSync(outputPath, Buffer.from(response.data)))

Rename the tool, rewrite the description, or move the side-effect into a separate clearly-named tool.

Tests exist

No test files found

Add tests that exercise each declared tool.

Secrets stay with their owner

2 secrets sent to a request target we could not resolve (STT_API_KEY → dynamic, STT_API_KEY → dynamic) — often a configured endpoint, not necessarily third-party

Audit where credentials are sent. A NOTION_TOKEN should only reach api.notion.com — never a third-party host.

Secrets not written to files

1 secret value written to files

Avoid persisting secrets to disk. Keep them in memory or your secret manager.

Tool description accuracy

tts: description implies read-only but handler writes/deletes/executes

Update tool descriptions to accurately reflect all capabilities — especially write, delete, or execute operations.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 7 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Verified](https://m8ven.ai/badge/mcp/ptbsare/ttsstt-mcp-server?variant=verified)](https://m8ven.ai/mcp/ptbsare/ttsstt-mcp-server)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 8b119d6b95bcd5f3c852b2779b4a866d600be076
code hash: f85e9f347205128eff8420982fc02766912c119105ab88d7afe8a4d2b8d6b146
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client