CaseMargin MCP — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Follow-up value is specific to CaseMargin ticket analysis and escalation-readiness tools: Do agents supply the actual ticket content while generated case analysis retains its stated lack of helpdesk integration?

Reviewed Oct 5, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

Prepare case briefs and check escalation readiness for support workflows.

What we know

Turn a support ticket into a structured case brief, or score its L2 escalation readiness. Exact operational authority remains unverified from first-party package documentation and must not be inferred. Source-derived feature labels are preliminary; obtain official runtime/tool evidence before applying uncertain fields.

Maintenance / activity evidence

casemargin-mcp-server 1.0.2 published 2026-08-05T09:12:12.999Z

Tracking evidence observed Oct 5, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: low.

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Permissions not yet verified. Complete write authority is not verified.
Authentication not yet verified.
Sensitive access: Support ticket content, Customer identifiers

Authority is not fully established. Do not treat unknown writes/auth as read-only or absent.

Full authority, access and evidence limits are available in Review context and Access & risk.

All limitations / Review context

Do agents supply the actual ticket content while generated case analysis retains its stated lack of helpdesk integration?

The bounded review of the publisher's documented CaseMargin ticket analysis and escalation-readiness tools and release notices identified no disclosed material condition preventing an accurately scoped public tracking entry. The resource's operational permissions remain uncertainty; this assessment does not certify installation safety.

Authority is not fully established. Do not treat unknown writes/auth as read-only or absent.
Sensitive access: Support ticket content, Customer identifiers
Complete write authority is not verified.
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited.
Documented tool authority and any remote data handling must be checked before installation or use.
Tool inventory, client matrix and permissions completeness were not requirements for this Radar tracking review.
repositoryIdentity: no confirmed package-to-repository binding
authentication: exact official auth and credential handling
writeActions: exact exposed tool mutation authority
dataHandling: provider destinations, retention and egress
cost: plans, pay-per-call charges, and payment authorization details
transport and actual executable entry point
Ticket ingestion and retention unverified
Any integration-side ticket modifications are unverified
Do not apply unverified auth, permissions, transport, lifecycle or write actions; preserve any better existing profile values.

Original activity observations

casemargin-mcp-server 1.0.2 published 2026-08-05T09:12:12.999Z

Technical identity

npm/casemargin-mcp-server

Exact implementation source: https://www.npmjs.com/package/casemargin-mcp-server ↗
Reviewed resource type: MCP Server
Package identity: npm:casemargin-mcp-server

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 5, 2026 · Latest source observation Oct 8, 2026

Package registry ↗
casemargin-mcp-server
Recorded package identity, distribution or download evidence.
Includes references whose attribution is not established.

Setup · Watchlist

Install & Agents

Publisher instructions.

Source evidence observed Oct 14, 2026.

Additional setup details required — see the specific gaps below.

Warning

Not runtime tested, no third-party installation, network authorization, paid calls, or mutation executed.
Do not claim production service is available based on README alone.
Official MCP client config includes API key; legal case data may be confidential
Official npm publisher package page README inspected for this exact npm identity; static research only. Some setup statements are conservatively summarized; no source code or live client execution checked. V2 review did not run any live client.
Check actual host syntax and supply credentials in secure client environment; do not paste placeholders verbatim.
Avoid write, payment, token transfer, publishing, sending, booking and remote account changes as tests.
Replace credential, action and registration placeholders; follow the matching publisher/client prerequisites. No execution performed.
Use the matching host, actual registration name and original installation environment; this does not revoke credentials.

Install / connect
Publisher instructions
Official MCP client config includes API key; legal case data may be confidential | Publisher npm README revisited on 2026-10-14; exact identity retained.
Reviewed setup example · Publisher instructions
npx -y casemargin-mcp-server
Configure / authenticate
MCP100 setup guide
Publisher-documented connection/installation path shown under install.commands. Check actual host syntax and supply credentials in secure client environment; do not paste placeholders verbatim. Official MCP client config includes API key; legal case data may be confidential Verify the correct host/transport from the publisher README; secure credentials in local client settings.
Required environment variables: CASEMARGIN_API_KEY
Check connection
Suggested check
Check that the registered MCP tools are discoverable in the client; run only publisher-described read-only status/health tools if provided. No runtime verification was performed.
Remove / uninstall / revoke
MCP100 setup guide
If your Claude Code MCP registration is named `casemargin-mcp-server`, run the client removal command. For Claude Desktop/Cursor/Codex or another registered name, remove the matching entry in that host’s MCP settings. Hosted OAuth disconnect and stopping a self-hosted process are separate; npx has no permanent global package install.
Remove named client registration · Claude Code only · MCP100 composed guide
claude mcp remove casemargin-mcp-server

Official Documentation & Sources

What it does

Turn a support ticket into a structured case brief, or score its L2 escalation readiness. Exact operational authority remains unverified from first-party package documentation and must not be inferred. Source-derived feature labels are preliminary; obtain official runtime/tool evidence before applying uncertain fields.

Capability: Productivity & Collaboration
Resource type: MCP Server
Best fit: Prepare case briefs and check escalation readiness for support workflows.

Representative uses

Structure a support ticket into a case brief
Assess L2 escalation readiness

Limitations

Ticket ingestion and retention unverified
Any integration-side ticket modifications are unverified
Do not apply unverified auth, permissions, transport, lifecycle or write actions; preserve any better existing profile values.

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: Not documented in the reviewed sources
Permissions: Not documented in the reviewed sources
Data handling: Not documented in the reviewed sources
Cost: Not documented in the reviewed sources
Risk and cautions: Authority is not fully established. Do not treat unknown writes/auth as read-only or absent.

Access scope and cautions

Write actions: Not verified
Sensitive access: Support ticket content Customer identifiers

The reviewed evidence does not establish the complete write authority of this MCP. Consult the unresolved evidence before granting write access.

FAQ

Based on reviewed evidence as of 2026-10-08. Watchlist tracking is not a recommendation or a security certification.

Which tasks are documented for this implementation?

The available discovery description lists: Structure a support ticket into a case brief; Assess L2 escalation readiness. These descriptions do not establish a fully verified tool inventory.

Can it modify data or perform write operations?

Not verified. The available evidence does not establish the complete write authority.

What data-handling boundary should I consider?

Recorded sensitive-access context: Support ticket content; Customer identifiers.

What limitations and risks should I check before use?

Authority is not fully established. Do not treat unknown writes/auth as read-only or absent. Ticket ingestion and retention unverified. Any integration-side ticket modifications are unverified. Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited. Documented tool authority and any remote data handling must be checked before installation or use.