armory (depthsecurity/armory) is an MCP server listed on the M8ven Trust Index. It scores 82 out of 100, grade B. It declares 70 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
B
Warning
82/100
5 days ago

armory

Armory is a tool meant to take in a lot of external and discovery data from a lot of tools, add it to a database and correlate all of related information.

→ depthsecurity/armory· 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

depthsecurity

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
🚨
Code appears obfuscated
4 files are unreadable to a human reviewer. Cannot audit what they do.
🔐
You'll be asked for 2 credentials: ARMORY_API_KEY, ARMORY_WEB_PASSWORD
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.
configARMORY_API_URL
🔐 secretARMORY_API_KEY
configARMORY_HOME
configARMORY_CONFIG
config_ARGCOMPLETE
configCOMP_LINE
configARMORY_WEB_BIND
configARMORY_WEB_PORT
configARMORY_WEB_USERNAME
🔐 secretARMORY_WEB_PASSWORD
configARMORY_API_EXEC_ENABLED
configARMORY_STRUCTURED_OUTPUT
// 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

70/70 tools missing one or more hints — get_stats (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); search (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); list_hosts (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +67 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 test coverage

Only 0/70 tools referenced in tests (0%)

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

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

4 files are minified or bundled, which is usually build output rather than concealment

Ship unminified, readable source.

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/depthsecurity/armory?variant=verified)](https://m8ven.ai/mcp/depthsecurity/armory)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 269cd850c885bbb783dfb4315c2d4bd88080fda5
code hash: 2cc031284baf8ab179472d69d39046cc1d91ac88860c6fb4c848e12f6bd07916
verified: 9/5/2026, 8:38:22 PM
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