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

Back to MCP Trust IndexM8ven
C
Emerging
74/100
8 days ago

codifier-mcp

A self-hosted MCP server that maintains a registry of project rules, enabling chats to query which rules apply to them in one call. It manages rule lifecycle with scopes, expiry, approval batches, and immutable history.

→ alcor6502/codifier-mcp· listed on glama

Emerging. No concerning findings. Grades remain capped until the project builds reputation through adoption. 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

alcor6502

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
✅
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
✅
Open source with a license and README
Anyone can audit the code, the license is declared, and the publisher documents what it does.
🔐
You'll be asked for 2 credentials: WEB_UI_PASSWORD, JWT_SIGNING_KEY
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.
configBIND_HOSTso a container installed earlier keeps behaving as it did),
configHTTP_MODE(stateless on a new install; the code's fallback stays stateful
configADMIN_AUTH_CODE_DURATIONWEB_PORT (empty means 9443), (minutes a one-time
configBACKUP_DIR/db/backup
configFASTMCP_HOMEFASTMCP_HOME is not under /data: tokens would not survive
configTASK_LINK_DAYScode stays good), (days a closing button keeps working,
configDB_DIRUnder Show more settings: (/db — move the mount, not this),
🔐 secretWEB_UI_PASSWORDopens the page that promulgates rules. There is no
🔐 secretJWT_SIGNING_KEYsigns the tokens the service issues. It must stay stable
configBASE_URL⚠ The callback must equal + /auth/callback exactly, scheme and
configWEB_PORTtable already declares: the host of BASE_URL, on , over http —
configPLAYWRIGHT_BROWSERS_PATH
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deploySMTP_HOST
deploySMTP_PORT
deploySMTP_USER
deploySMTP_PASSWORD
deploySMTP_FROM
deploySMTP_SECURITY
deployPORT
// 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

16/16 tools missing one or more hints — reference_guide (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); project_info (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); rules_list (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +13 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.

Secrets not logged

1 secret value sent to log.info

Redact or omit secret values from log output.

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 3 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 Score](https://m8ven.ai/badge/mcp/alcor6502/codifier-mcp)](https://m8ven.ai/mcp/alcor6502/codifier-mcp)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: ac7525c3c67dbd01d04906f83b591c50a391fe67
code hash: 93fd0688c22de5c02695840e53f47ab6d9211dde1fa2e67add40c265317e95c5
verified: 9/2/2026, 11:32:05 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