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
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
Upsonic
Source: github_topic
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 →
Install from
M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.
UPSONIC_TELEMETRYAZURE_OPENAI_ENDPOINTAZURE_OPENAI_API_KEYOPENAI_API_KEYGOOGLE_AI_API_KEYGEMINI_API_KEYAWS_ACCESS_KEY_IDAWS_PROFILEGOOGLE_API_KEYHF_TOKENHUGGINGFACE_HUB_TOKENASQAV_API_KEYASQAV_API_URLPROMPTLAYER_API_KEYUPSONIC_OTEL_HEADERSUPSONIC_OTEL_SAMPLE_RATETool 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
174/174 tools missing one or more hints — mcp (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); dangerous_action (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); safe_action (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +171 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.
Destructive tools are labelled
1 tool perform destructive updates without destructiveHint — delete_file deletes at line 817 (shutil.rmtree(str(resolved)))
Add destructiveHint:true to any tool whose handler calls .delete(), .upsert(), .update(), unlink, rm, DELETE, DROP, REPLACE INTO, or any operation that overwrites existing data.
Descriptions match behaviour
2 tools describe read intent but their handlers mutate — edit_file (line 352: resolved.write_text(new_content, encoding="utf-8")); edit_file (line 211: resolved.write_text(new_content, encoding="utf-8"))
Rename the tool, rewrite the description, or move the side-effect into a separate clearly-named tool.
Tool inputs are validated
151/161 tool handlers declare input schemas (94%)
Declare an inputSchema with zod/joi/yup on every tool definition.
Tool handlers catch errors
97/161 tool handlers wrap calls in try/catch (60%)
Wrap each tool handler body in try/catch and return a structured error response.
License file
No license file
Add a LICENSE file (MIT, Apache-2.0, etc.).
Tests exist
No test files found
Add tests that exercise each declared tool.
No access to sensitive paths
Reads sensitive paths: credentials.json
Remove reads of sensitive system paths. If you genuinely need them, document why in the README.
Shell command execution
3 child_process calls — runs shell commands
Prefer library functions over shell-outs. If you must shell out, ensure all inputs are properly escaped.
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.
[](https://m8ven.ai/mcp/upsonic-upsonic-1ow6ni)?variant=verified from the URL.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