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
Bare-Systems
Source: github_repo_search
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
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.
URSA_MCP_TRANSPORTURSA_MCP_HOSTURSA_MCP_PORTURSA_MCP_STREAMABLE_HTTP_PATHSHELLURSA_PRODUCTIONURSA_ENVset environment: production in ursa.yaml or export =production,URSA_MODESSH_AUTH_SOCKURSA_MINOR_APPROVAL_KEYURSA_SCAN_RANGEURSA_CP_URLURSA_URLURSA_API_TOKENURSA_COLLECTOR_ACTORTool 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
108/108 tools missing one or more hints — ursa_start_c2 (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); ursa_stop_c2 (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); ursa_c2_status (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +105 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
2 tools perform destructive updates without destructiveHint — ursa_start_c2 deletes at line 196 (os.unlink(C2_PID_FILE)); ursa_stop_c2 deletes at line 254 (os.unlink(C2_PID_FILE))
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
1 tool describes read intent but its handler mutates — get_my_network_info (line 781: proc = subprocess.run()
Rename the tool, rewrite the description, or move the side-effect into a separate clearly-named tool.
No eval / new Function
2 eval() or new Function() calls — dynamic code execution
Replace eval / Function with explicit parsing or safer alternatives.
Readable source code
1 file are minified or bundled, which is usually build output rather than concealment
Ship unminified, readable source.
Secrets not logged
1 secret value sent to print
Redact or omit secret values from log output.
Tool description accuracy
get_my_network_info: 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.
[](https://m8ven.ai/mcp/bare-systems/ursa)?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