ai.clarx/mcp
NPM · @CLARXAI/MCP · SCANNED AUG 3
Score agent manifests, generate CI workflows, and pull Clarx scan findings into your IDE.
Available components
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 →
Supply Chain Security87
- No malware found by supply-chain analysis.Pass
- Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
- 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 26 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability71
- AI-judged instruction clarity (good).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 Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · @clarxai/mcp
claude mcp add ai-clarx-mcp -- npx -y @clarxai/mcp
codex mcp add ai-clarx-mcp -- npx -y @clarxai/mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ai-clarx-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"@clarxai/mcp"
],
"enabled": true
}
}
} openclaw mcp add ai-clarx-mcp --command npx --arg -y --arg @clarxai/mcp
mcp_servers:
ai-clarx-mcp:
command: "npx"
args: ["-y", "@clarxai/mcp"] {
"mcpServers": {
"ai-clarx-mcp": {
"command": "npx",
"args": [
"-y",
"@clarxai/mcp"
]
}
}
} 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.
- 2 Aug 26 +48
- Provenance: unverified → fail ▼ security
- Install scripts: unverified → pass ▲ security
- Known CVEs: unverified → partial ▲ security
- Tool coverage: unverified → 100 ▲ functional
- License: unverified → pass ▲ functional
- Dependency health: unverified → partial ▲ functional
- Maintenance: unverified → pass ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Stability: unverified → 0.23 ▲ functional
- Schema quality: unverified → good ▲ functional
- Licence: MIT functional
- 1 Aug 26 +15
- Malware scan: unverified → pass ▲ security
- 31 Jul 26 −40
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 28 Jul 26 +22
- Tool coverage: unverified → 100 ▲ functional
- First check of Schema quality: unverified functional
- First check of Tool coverage: 100 functional
- First check of Schema quality: fail functional
- First check of Schema quality: fail functional
- 27 Jul 26 18
First indexed and scored.
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 3 Aug 2026 · Analysed npm/@clarxai/[email protected]
Provenance none
Ecosystem: npm · Outcome: none
Dependencies 95 packages
95 packages in the resolved dependency tree · 95 deprecated · 29 stale.
The dependency tree was only partially resolved, so these counts may be incomplete.
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.
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.