Back to MCP Trust Indexm8ven
C
Warning
74/100
2 days ago

un-default

Enables scanning, fixing, and providing feedback on text for inclusive language, offering clearer alternatives and tunable rules.

→ NomadBuilder/anti-default· listed on glama

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

NomadBuilder

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

Glama

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

// key findings
🚨
Secret credentials may flow to a network call
1 flow detected: TELEMETRY_GIST_TOKEN. We can’t prove the destination matches the brand the credential belongs to.
🔐
You'll be asked for 1 credential: TELEMETRY_GIST_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.
configBASE_PATHSubpath (DarkAI): STATIC_EXPORT=true =/un-default npm run build
configSTATIC_EXPORTSubpath (DarkAI): =true BASE_PATH=/un-default npm run build
configUN_DEFAULT_USAGE_PATH
configTELEMETRY_GIST_ID
🔐 secretTELEMETRY_GIST_TOKEN
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployNEXT_PUBLIC_BASE_PATH
deployNEXT_PUBLIC_CHROME_STORE_URL
deployNEXT_PUBLIC_GTM_ID
// 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

3/3 tools missing one or more hints — un_default_scan (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); un_default_fix (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); un_default_feedback (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.

Tests exist

No test files found

Add tests that exercise each declared tool.

Secrets stay with their owner

1 secret/sensitive value flow into network calls (TELEMETRY_GIST_TOKEN → https://api.github.com/gists/)

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

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 4 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/nomadbuilder-anti-default-u4w0qh?variant=verified)](https://m8ven.ai/mcp/nomadbuilder-anti-default-u4w0qh)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 494f9828fcff7a9530194e66ce8b1f218782937f
code hash: d46d0cbfa581028d778a718b3c752794261ef4e25f5de3e845c004a594f87879
verified: 8/17/2026, 9:17:10 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