ocentra-enforcer (ocentra/ocentra-enforcer) is an MCP server listed on the M8ven Trust Index. It scores 41 out of 100, grade D. It declares 50 tools. No publisher has claimed this listing.

D
Caution
41/100

ocentra-enforcer

MCP server for enforcing coding rules in Rust projects via scanning, routing, and explanation tools, designed for use with Codex, CI pipelines, and precommit hooks.

Caution. Specific findings reduced this grade. They are listed on the page. 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

ocentra

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 →

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.

⏳ This MCP is queued for scoring. Check back in a few minutes.
// key findings
🚨
Reads files from sensitive locations
Touches: Credentials, credentials
🔐
You'll be asked for 15 credentials: AZURE_CLIENT_SECRET, VT_API_KEY, ABUSEIPDB_API_KEY, URLSCAN_API_KEY, NVD_API_KEY, SPLUNK_PASSWORD, TAXII_PASSWORD, ABUSEIPDB_KEY, SPLUNK_HEC_TOKEN, GITLAB_TOKEN, THEHIVE_API_KEY, OPENCTI_TOKEN, VIRUSTOTAL_API_KEY, SHODAN_API_KEY, GREYNOISE_API_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.
configCARGO_BUILD_JOBS
configCARGO_INCREMENTAL
configComSpec
configOCENTRA_ENFORCER_MCP_FINGERPRINT_EXTRA
configOCENTRA_PARENT_ROOT
configAZURE_WORKSPACE_ID
configAZURE_TENANT_ID
configAZURE_CLIENT_ID
🔐 secretAZURE_CLIENT_SECRET
configAUTOPSY_CASE_DIR
🔐 secretVT_API_KEY
🔐 secretABUSEIPDB_API_KEY
🔐 secretURLSCAN_API_KEY
configCUCKOO_API
configCUCKOO_STORAGE
configSURICATA_OUTPUT_DIR
🔐 secretNVD_API_KEY
configSPLUNK_HOST
configSPLUNK_PORT
configSPLUNK_USERNAME
🔐 secretSPLUNK_PASSWORD
configTAXII_USER
🔐 secretTAXII_PASSWORD
configAWS_PROFILE
configAWS_DEFAULT_REGION
configKUBECONFIG
🔐 secretABUSEIPDB_KEY
configSKIP_TLS_VERIFY
configCUCKOO_URL
configSPLUNK_HEC_URL
🔐 secretSPLUNK_HEC_TOKEN
configSENTINEL_WORKSPACE_ID
🔐 secretGITLAB_TOKEN
configGITLAB_URL
configGITLAB_GROUP_ID
configTHEHIVE_URL
🔐 secretTHEHIVE_API_KEY
configOPENCTI_URL
🔐 secretOPENCTI_TOKEN
🔐 secretVIRUSTOTAL_API_KEY
🔐 secretSHODAN_API_KEY
🔐 secretGREYNOISE_API_KEY
configSPLUNK_URL
// 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

50/50 tools missing one or more hints — ocentra_enforcer_coordination_init (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); ocentra_enforcer_coordination_health (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); ocentra_enforcer_coordination_presence (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +47 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/50 tools referenced in tests (0%)

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

No access to sensitive paths

Reads sensitive paths: Credentials, credentials

Remove reads of sensitive system paths. If you genuinely need them, document why in the README.

Shell command execution

30 child_process calls — runs shell commands

Prefer library functions over shell-outs. If you must shell out, ensure all inputs are properly escaped.

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/ocentra/ocentra-enforcer?variant=verified)](https://m8ven.ai/mcp/ocentra/ocentra-enforcer)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: e762b2f9c05a028ec28dd801a7ce28e4025b3ba7
code hash: a0f0653052de030179230aa3d21026dcc8b6aa19d4968c5066be204106a31542
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