io.github.YawLabs/mcp-compliance
NPM · @YAWLABS/MCP-COMPLIANCE · SCANNED AUG 7
CLI tool and MCP server that tests MCP servers for spec compliance
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
- Known CVEs were checked across the 97 of 101 dependencies we could resolve, so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Dependency health was assessed across the 97 of 101 dependencies we could resolve, so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency23
- Repository check failed: no source repository is declared. 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 16 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability77
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 252 tokens (~126/item across 2 items; 2 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management40
- Stability observed for 12 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 · @yawlabs/mcp-compliance
claude mcp add yawlabs-mcp-compliance -- npx -y @yawlabs/mcp-compliance
codex mcp add yawlabs-mcp-compliance -- npx -y @yawlabs/mcp-compliance
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"yawlabs-mcp-compliance": {
"type": "local",
"command": [
"npx",
"-y",
"@yawlabs/mcp-compliance"
],
"enabled": true
}
}
} openclaw mcp add yawlabs-mcp-compliance --command npx --arg -y --arg @yawlabs/mcp-compliance
mcp_servers:
yawlabs-mcp-compliance:
command: "npx"
args: ["-y", "@yawlabs/mcp-compliance"] {
"mcpServers": {
"yawlabs-mcp-compliance": {
"command": "npx",
"args": [
"-y",
"@yawlabs/mcp-compliance"
]
}
}
} 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.
- 7 Aug 26 +1
- Security disclosure: fail → pass ▲ functional
- 6 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 5 Aug 26 0
- Security disclosure: unverified → fail ▼ functional
- 4 Aug 26 +1
- Security disclosure: fail → unverified ▼ functional
- 3 Aug 26 +4
- Stability: unverified → 0.27 ▲ functional
- 2 Aug 26 +44
- Provenance: unverified → fail ▼ security
- Install scripts: unverified → pass ▲ security
- Known CVEs: unverified → partial ▲ security
- Malware scan: unverified → pass ▲ security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Security disclosure: unverified → fail ▼ functional
- Maintenance: unverified → pass ▲ functional
- MCP protocol: unverified → pass ▲ functional
- License: unverified → pass ▲ functional
- Schema quality: unverified → excellent ▲ functional
- Dependency health: unverified → partial ▲ functional
- Licence: MIT functional
- 1 Aug 26 +15
- Dependency health: partial → unverified ▼ functional
- Tool coverage: unverified → 100 ▲ functional
- 31 Jul 26 −39
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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 7 Aug 2026 · Analysed npm/@yawlabs/[email protected]
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Dependencies 97 packages
| Packages resolved | 97 |
|---|---|
| Deprecated | 97 |
| Stale | 29 |
| Tree resolution | Partial |
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.
mcp_compliance_explain ~54
Explain what a specific compliance test ID checks and why it matters.
| Name | Type | Req | Description |
|---|---|---|---|
| testId | string | yes | The test ID to explain (e.g., "transport-post", "lifecycle-init", "tools-schema") |
No output schema declared.
No examples provided.
mcp_compliance_test ~198
Run the full MCP compliance test suite against a server URL. Returns grade (A-F), score, and detailed results for all 88 tests covering transport, lifecycle, tools, resources, prompts, errors, schema validation, and security.
| Name | Type | Req | Description |
|---|---|---|---|
| auth | string | – | Authorization header value (e.g., "Bearer tok123") |
| headers | object | – | Additional headers to include on all requests (e.g., {"X-Api-Key": "abc"}) |
| only | array | – | Only run tests matching these categories or test IDs |
| retries | integer | – | Number of retries for failed tests (default: 0, max: 10) |
| skip | array | – | Skip tests matching these categories or test IDs |
| timeout | integer | – | Request timeout in milliseconds (default: 15000, max: 300000) |
| url | string | yes | The MCP server URL to test (must be HTTP or HTTPS) |
No output schema declared.
No examples provided.