People’s Court

ai.peoplescourtPublished by peoplescourt.aiOfficial publisherv0.1.2Updated Oct 27, 2026

Agentic commerce dispute resolution and AI arbitration for marketplaces. Read cases; draft filings.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowBusiness & Commerce

Overview

AI-generated overview

Remote MCP endpoint for People's Court that lets an assistant read commerce dispute cases and draft filings for AI-assisted arbitration.

What you can do
  • Read dispute cases from the People's Court platform
  • Draft filings for those cases
  • Support agentic commerce dispute resolution and AI arbitration workflows for marketplaces
When to use it
Useful when a marketplace or seller workflow needs an assistant to review existing dispute cases or prepare draft filings before human review. It is aimed at commerce dispute resolution rather than general legal advice.
Requirements
A remote streamable HTTP endpoint at mcp.peoplescourt.ai; OAuth authentication is required. No environment variables or headers are declared.
Before you install
OAuth grants the server access to your People's Court account, and drafted filings concern real disputes, so review anything it produces before submitting. The tool list is not published, so confirm what it can read or write after connecting.

Installation

In SourceWeft

  1. Open People’s Court in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/ai.peoplescourt%2Fpeoples-court/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "people-s-court": {
      "type": "http",
      "url": "https://mcp.peoplescourt.ai/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

2
  1. v0.1.2LatestOct 19, 2026
  2. v0.1.1Oct 16, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.