Back to MCP Trust Indexm8ven
F
Warning
34/100
21 hours ago

mcpsynth

→ teostereciu/mcpsynth· listed on github_code

Warning. Serious findings were identified. Review the full report before connecting. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

Code 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

teostereciu

Source: github_code

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

GitHub

M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.

// key findings
🚨
Secret credentials may flow to a network call
25 flows detected: ALPHAVANTAGE_API_KEY, JIRA_API_TOKEN, EBAY_AUTH_HEADER. We can’t prove the destination matches the brand the credential belongs to.
🚨
Hardcoded credentials detected
1 live-looking API key in source: 1 Shopify app secret
🔐
You'll be asked for 9 credentials: ALPHAVANTAGE_API_KEY, ALPHA_VANTAGE_API_KEY, CLOCKIFY_API_KEY, CONFLUENCE_SPACE_KEY, CONFLUENCE_ACCESS_TOKEN, CONFLUENCE_API_TOKEN, CONFLUENCE_BEARER_TOKEN, EBAY_REFRESH_TOKEN, EBAY_ACCESS_TOKEN
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.
🔐 secretALPHAVANTAGE_API_KEY
configALPHAVANTAGE_TIMEOUT
🔐 secretALPHA_VANTAGE_API_KEY
🔐 secretCLOCKIFY_API_KEY
configCONFLUENCE_BASE_URL
🔐 secretCONFLUENCE_SPACE_KEY
configAPI_VERSION
🔐 secretCONFLUENCE_ACCESS_TOKEN
🔐 secretCONFLUENCE_API_TOKEN
configCONFLUENCE_EMAIL
🔐 secretCONFLUENCE_BEARER_TOKEN
configEBAY_APP_ID
configEBAY_CERT_ID
configEBAY_ENVIRONMENT
configEBAY_AUTH_HEADER
configEBAY_MARKETPLACE_ID
🔐 secretEBAY_REFRESH_TOKEN
configEBAY_API_BASE
configEBAY_APIM_BASE
configEBAY_SANDBOX
🔐 secretEBAY_ACCESS_TOKEN
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployPORT
// 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

4356/4356 tools missing one or more hints — get_current_weather_by_city (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_current_weather_by_coords (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_current_weather_by_city_id (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +4353 more. 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.

Tool inputs are validated

4080/4107 tool handlers declare input schemas (99%)

Declare an inputSchema with zod/joi/yup on every tool definition.

No hardcoded API keys

1 live-looking API key in source: 1 Shopify app secret

Move secrets to environment variables (process.env.X) or your secret manager.

Tool test coverage

Only 3/4356 tools referenced in tests (0%)

Write tests that reference each tool by name so every tool has at least one test.

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 5 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/teostereciu-mcpsynth-jdhgaz?variant=verified)](https://m8ven.ai/mcp/teostereciu-mcpsynth-jdhgaz)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 4d6c087e40e32edb8d86e8f7468c86627bf779bd
code hash: e9dcedd709a5a0ac0d0b1502fa30c6a77b51e8e41d9055b7311b7aae8a86e707
verified: 8/19/2026, 1:58:39 AM
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