com.casemargin/casemargin-mcp-server
NPM · CASEMARGIN-MCP-SERVER · SCANNED AUG 13
Turn a support ticket into a structured case brief, or score its L2 escalation readiness.
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 Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 30 of 95 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to Casemargin/casemargin-mcp-server). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 7 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability69
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 125 tokens (~62/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 Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
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 · casemargin-mcp-server
claude mcp add com-casemargin-casemargin-mcp-server -- npx -y casemargin-mcp-server
codex mcp add com-casemargin-casemargin-mcp-server -- npx -y casemargin-mcp-server
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-casemargin-casemargin-mcp-server": {
"type": "local",
"command": [
"npx",
"-y",
"casemargin-mcp-server"
],
"enabled": true
}
}
} openclaw mcp add com-casemargin-casemargin-mcp-server --command npx --arg -y --arg casemargin-mcp-server
mcp_servers:
com-casemargin-casemargin-mcp-server:
command: "npx"
args: ["-y", "casemargin-mcp-server"] {
"mcpServers": {
"com-casemargin-casemargin-mcp-server": {
"command": "npx",
"args": [
"-y",
"casemargin-mcp-server"
]
}
}
} 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.
- 11 Aug 26 −1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 7 Aug 26 +5
- Known CVEs: partial → pass ▲ security
- Security disclosure: fail → pass ▲ functional
- Dependency health: partial → 0.85 functional
- 6 Aug 26 +29
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- First check of Schema quality: pass functional
- First check of Schema quality: good functional
- First check of Tool coverage: 100 functional
- First check of Tool coverage: 100 functional
- First check of Schema quality: fail functional
- 5 Aug 26 45
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 13 Aug 2026 · Analysed npm/casemargin-mcp-server@1.0.2
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | Casemargin/casemargin-mcp-server |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/Casemargin/casemargin-mcp-server/.github/workflows/publish.yml@refs/tags/v1.0.2 |
| Rekor log index | 2343332389 |
| Predicate type | https://slsa.dev/provenance/v1 |
| Subject digest | sha512:47e7682a87a790f3a25f02542626addc4984cbd806298ce6292a259f988f9aff70263683b1b1eb9dab8a9a238039fd37d4b02946d7479352b80040625 |
Dependencies 95 packages
| Packages resolved | 95 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
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.
check_escalation_readiness Check escalation readiness ~65
Analyze whether a support ticket is ready to escalate to L2. Returns a readiness score (0-100), dimensional breakdown, predicted L2 questions, and missing items.
| Name | Type | Req | Description |
|---|---|---|---|
| ticket_content | string | yes | The support ticket notes to evaluate for L2 escalation readiness |
| Name | Type | Req | Description |
|---|---|---|---|
| dimensions | object | yes | – |
| missing_items | array | yes | – |
| overall_score | number | yes | – |
| predicted_l2_questions | array | yes | – |
| readiness | string | yes | – |
No examples provided.
generate_case_brief Generate case brief ~60
Generate a structured case brief from a support ticket thread. Returns an assessment, what has been tried, current status, and recommended next step.
| Name | Type | Req | Description |
|---|---|---|---|
| ticket_content | string | yes | The full support ticket thread — customer messages, agent replies, internal notes |
| Name | Type | Req | Description |
|---|---|---|---|
| full_brief | object | yes | – |
| metadata | object | yes | – |
| quick_scan | object | yes | – |
No examples provided.