Skip to main content
Glama

Server Details

Agentic commerce dispute resolution and AI arbitration for marketplaces. Read authorized cases and served Awards, prepare filings and Answers for personal review, and submit authorized briefs and messages. Consent-based AI-only or AI-assisted human arbitration, with reasoned decisions and an optional paid human appeal.

Ownership verified

The last two health checks of this connector failed. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.

If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.

Status
Unhealthy
Uptime
0.0% over the last 24 hours
OAuth
Works in Glama
Last Tested
Transport
Streamable HTTP
URL
ChatGPT
–
Claude
–

TDQS

A3.9/5.0

Scored across 24 tools

Disambiguation3/5

Most tools separate cleanly by resource and action (prepare/confirm pairs for filings and answers, distinct get_* readers), but two overlaps are real: report_record_omissions and request_record_correction both submit person-approved correction text to the party's own Rule 4.8 Record summary, and get_case_record_manifest and prepare_case_record both prepare/poll the same export. The prepare/get/confirm/submit prefixes help, yet an agent must read several paragraphs of prose to learn which correction tool is the replacement for which.

Naming Consistency5/5

Every name is snake_case verb_noun with a small, stable verb set (get_, list_, prepare_, confirm_, submit_, file_, report_, request_, manage_, post_, quote_). The prepare/confirm symmetry across filing and answer workflows makes the lifecycle readable from names alone.

Tool Count3/5

24 tools sits at the heavy end for a single-domain server; the legal workflow is genuinely broad, but the count is inflated by redundant pairs (two Record-correction tools, two export-preparation tools) that could be consolidated. It is defensible but feels over-expanded rather than tightly scoped.

Completeness4/5

Coverage is broad across the lifecycle: case intake, answering, briefs, procedural requests, records, awards, invitations, messages, fees, and Rules. Gaps are mostly deliberate website-only handoffs, but there is a genuine dead end where a procedural request cannot be withdrawn or edited through MCP (only via the canonical API), and no tool lets a respondent formally respond/join a case.

Publisher details

Operator
Epistemic Labs Inc. · Publisher source
Vendor relationship
First-party · Publisher source
Privacy policy
Not provided
Trust center
Unknown
Restrictions
Requires a verified People’s Court account and OAuth authorization. Access is limited to authorized cases and approved scopes. Case-opening consent and applicable filing or appeal fees are handled on People’s Court. · Publisher source

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables autonomous AI agents to submit principal-bounded sealed offers for commercial or SLA disputes, settle overlapping offers deterministically at a midpoint or fair split, and receive verifiable signed settlement instructions or UNRESOLVED certificates while keeping confidential terms private.
      Apache 2.0
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI-powered consumer dispute resolution by providing tools for secure evidence storage with confidence scoring, autonomous negotiation, formal dispute notice generation, and consumer rights verification under the Consumer Protection Act.
      Apache 2.0
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.

    Resources