MCP Standards Server (williamzujkowski/mcp-standards-server) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 21 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
C
Warning
74/100

MCP Standards Server

A Model Context Protocol (MCP) server that provides intelligent, context-aware access to development standards, enabling LLMs to automatically select and apply appropriate standards based on project requirements.

→ williamzujkowski/mcp-standards-server· 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

⚡ 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

williamzujkowski

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

Glamanot scored here

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.

// key findings
🚨
Code appears obfuscated
2 files are unreadable to a human reviewer. Cannot audit what they do.
🔐
You'll be asked for 3 credentials: GITHUB_TOKEN, MCP_JWT_SECRET, SECRET_KEY
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// tools this server exposes21 tools

These names and descriptions are the publisher's own, read from the source code. We print them as written. Our assessment is the findings above, not this list.

get_applicable_standards

Get applicable standards based on project context

validate_against_standard

Validate code against a specific standard

search_standards

Search standards using semantic search

get_standard_details

Get detailed information about a specific standard

list_available_standards

List all available standards

suggest_improvements

Suggest improvements based on applicable standards

sync_standards

Synchronize standards from repository

get_optimized_standard

Get a token-optimized version of a standard

auto_optimize_standards

Automatically optimize multiple standards within a token budget

progressive_load_standard

Get a progressive loading plan for a standard

estimate_token_usage

Estimate token usage for standards in different formats

get_sync_status

Get current synchronization status

generate_standard

Generate a new standard based on template and context

validate_standard

Validate a standard document for completeness and quality

list_templates

List available standard templates

get_cross_references

Get cross-references for a standard or concept

generate_cross_references

Generate cross-references between standards

get_standards_analytics

Get analytics and usage statistics for standards

track_standards_usage

Track usage of specific standards or sections

get_recommendations

Get recommendations for standards improvement or gaps

get_metrics_dashboard

Get performance metrics dashboard

// 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.
configREACT_APP_API_URL
configMCP_STANDARDS_DATA_DIR
configMCP_DISABLE_SEARCH
configMCP_CONFIG_PATH
configHTTP_HOST
configHTTP_PORT
configHTTP_ONLY
configLOG_LEVEL
configWEB_HOST
🔐 secretGITHUB_TOKEN
configDATA_DIR
configNO_COLORDisable colored output in CLI
configMCP_AUTH_ENABLED
🔐 secretMCP_JWT_SECRET
configMCP_MASK_ERRORS
configENVIRONMENT
configHOSTNAME
configLOG_FORMAT
configLOG_FILE
configLOG_DIR
🔐 secretSECRET_KEY
configMCP_TEST_MODE
configPYTEST_CURRENT_TEST
configHF_DATASETS_OFFLINE
// 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

21/21 tools missing one or more hints — get_applicable_standards (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); validate_against_standard (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); search_standards (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +18 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.

No eval / new Function

1 eval() or new Function() call — dynamic code execution

Replace eval / Function with explicit parsing or safer alternatives.

Readable source code

2 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 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/williamzujkowski/mcp-standards-server?variant=verified)](https://m8ven.ai/mcp/williamzujkowski/mcp-standards-server)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: c068f867d5458a076935d9bd903c20f5c986d604
code hash: e61e8cb6f39f18b06ca55f6321056305af4fcc52ec1bddcde02c421a33454342
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