ai.clarx/mcp
NPM · @CLARXAI/MCP
Score agent manifests, generate CI workflows, and pull Clarx scan findings into your IDE.
Available components
Last scanned (1 hour ago)
Scores higher than 48% of npm servers
Category CI/CD and DevOps
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- Repository presence not verified: we could not reach the forge to check. This is a gap on our side, not a finding about the repository. View diagnostics → Unverified
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 77 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability78
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 413 tokens (~137/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 0
- Provenance: fail → unverified ▼ security
- 1 Nov 26 0
- Stability: 0.97 → pass security
- 31 Oct 26 0
- Stability: pass → 0.97 functional
- 25 Oct 26 0
- Stability: 0.97 → pass security
- 24 Oct 26 −4
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- 23 Oct 26 −1
- Stability: pass → 0.93 functional
- 17 Oct 26 0
- Stability: 0.97 → pass security
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/@clarxai/mcp@0.2.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
analyze_clarx_manifest Validate clarx-manifest.json ~89
Validate a clarx-manifest.json machine manifest against the Clarx engine schema. Returns recognized keys, errors, and suggestions for keys worth declaring (generated dirs, hubs, verification commands).
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | – | Raw JSON content. Pass this or file_path, not both. |
| file_path | string | – | Path to clarx-manifest.json (resolved against the server working directory). |
No output schema declared.
No examples provided.
analyze_manifest Score an agent manifest ~158
Score CLAUDE.md / AGENTS.md manifest content with the same rules as the Clarx manifest studio. Returns an overall quality estimate (0-100), per-pillar scores, findings with line numbers, and a section checklist. This is a manifest quality estimate — do not compare it to Clarx repo AI-readiness scores, which use a different rule system.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | – | Full markdown body of the manifest. Pass this or file_path, not both. |
| file_path | string | – | Path to the manifest file (resolved against the server working directory, typically the workspace root). Preferred — avoids inlining the file into the conversation. |
| include_outline | boolean | – | Include the heading outline (section tree with line numbers). |
No output schema declared.
No examples provided.
get_ci_workflow Generate Clarx CI workflow ~166
Generate a GitHub Actions workflow YAML that gates pull requests on the Clarx AI-readiness score (npx @clarxai/cli). Write the result to .github/workflows/clarx.yml.
| Name | Type | Req | Description |
|---|---|---|---|
| cli_version | string | – | @clarxai/cli version to pin. |
| ignore_patterns | array | – | Glob patterns to exclude from scoring, e.g. ['vendor/**']. |
| min_pillar_score | number|null | – | Optional per-pillar floor. |
| min_score | number | – | Fail the check when the overall score is below this (0-100). |
| upload_artifact | boolean | – | Attach a markdown report artifact to the run. |
| upload_sarif | boolean | – | Upload findings as SARIF to GitHub code scanning. |
No output schema declared.
No examples provided.
How do I install the ai.clarx/mcp server?
ai.clarx/mcp runs locally as an npm package, launched with npx -y @clarxai/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @clarxai/mcp
claude mcp add ai-clarx-mcp -- npx -y @clarxai/mcp
What is the ai.clarx/mcp server?
ai.clarx/mcp is listed in the public MCP registry as ai.clarx/mcp. Score agent manifests, generate CI workflows, and pull Clarx scan findings into your IDE. This page covers its npm package (@clarxai/mcp).
Is the ai.clarx/mcp server safe to use?
ai.clarx/mcp scores 74 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the ai.clarx/mcp server expose?
ai.clarx/mcp exposes 3 tools: analyze_manifest, analyze_clarx_manifest, get_ci_workflow. Their descriptions and schemas cost roughly 413 tokens of context every time the server is loaded.
Is the ai.clarx/mcp server still maintained?
ai.clarx/mcp is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the ai.clarx/mcp server under?
ai.clarx/mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.