Skarp CRA (ozzynxe/cra) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 47 tools. No publisher has claimed this listing.

Back to MCP Trust Indexm8ven
C
Emerging
74/100
11 days ago

Skarp CRA

An MCP server that helps software makers meet EU Cyber Resilience Act obligations, including scope classification, Article 13(2) risk assessment, Annex I requirements with evidence, vulnerability and incident tracking with Article 14 reporting clocks, and Annex VII technical file assembly.

→ ozzynxe/cra· 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

ozzynxe

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: SKARP_AUTH_ME_URL. We can’t prove the destination matches the brand the credential belongs to.
🔐
You'll be asked for 2 credentials: CRA_ADMIN_TOKEN, SKARP_JWT_SECRET
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.
configCRA_PORT
configCRA_RELEASE
configCRA_SWEEP_LOOKAHEAD_HOURS
configCRA_OSV_URL
configCRA_ADVISORY_TIMEOUT
configCRA_KEV_TTL_SECONDS
configCRA_OSV_ADVISORY_TTL_SECONDS
configCRA_OSV_ADVISORY_CACHE_MAX
configCRA_EPSS_TTL_SECONDS
configCRA_EURLEX_TIMEOUT
configCRA_EURLEX_TTL_REPEALED
configCRA_EURLEX_TTL_IN_FORCE
configCRA_EURLEX_TTL_UNKNOWN
configCRA_ENV
configCRA_ADVISORY_SCAN_ENABLED
configCRA_ADVISORY_ALERTS_ENABLED
configCRA_ADVISORY_SWEEP_SECONDS
🔐 secretCRA_ADMIN_TOKEN
configCRA_TOKEN_PREFIX
configCRA_ALERTS_FROM
configCRA_ALERTS_SES_REGION
configCRA_APP_ORIGIN
configCRA_ENTITLEMENTS_ENFORCED
configCRA_PARTIES
configCRA_ALLOWED_HOSTS
configCRA_HOST
configCRA_LOG_LEVEL
configCRA_OAUTH_REDIRECT_HOSTS
configCRA_RATE_LIMIT_OFF
configCRA_RELEASE_SCAN_MAX_AGE_DAYS
configCRA_MAX_CONCURRENT_SESSIONS
configCRA_SIGNUP_ENABLED
configCRA_SIGNUP_INVITE_CODE
🔐 secretSKARP_JWT_SECRET
configSKARP_AUTH_ME_URL
configCRA_STATUTORY_BUCKET
configAWS_REGION
configCRA_STATE_DIR
configCRA_STOREthem loses the record of who changed what. follows DATABASE_URL
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployDATABASE_URL
deploySENTRY_DSN
deploySENTRY_TRACES_SAMPLE_RATE
deployREDIS_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

47/47 tools missing one or more hints — cra_overview (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); list_products (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_compliance_status (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +44 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.

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 2 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/ozzynxe-cra-15mwxp)](https://m8ven.ai/mcp/ozzynxe-cra-15mwxp)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: dcdcecd167437030ee4a7a0ccd1ef385091e510a
code hash: 2c873b5c5eef651763895852fc1723a1f9d7c450a933a3c72fe788ccbd1c64e1
verified: 8/12/2026, 7:45:21 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