Status
LIVE
Plaintiff-side verdict and settlement wire: firm leaderboard across $11B+ in publicly announced results, verdict search by firm/state/amount, and the legal press wire.
https://plaintiffwire.com/mcp · streamable_http · auth: none · freeOne paste. Your agent works out which client it is running in and writes its own config — no key, no login step. Raw text at /connect/plaintiffwire.txt.
Connect the PlaintiffWire MCP server to this agent's host client.
Server: https://plaintiffwire.com/mcp — MCP streamable HTTP, public and read-only.
No authentication: do NOT add an API key, an Authorization header, or an OAuth flow.
There is no login step.
Step 1 — Identify which client you are running in (Claude Code, Codex CLI, Cursor,
VS Code, Windsurf, Gemini CLI, or other).
Step 2 — Install for that client only. If a "plaintiffwire" MCP entry already exists, replace
it. When editing a JSON config file, read it first and merge the new entry — never
overwrite other entries.
- Claude Code:
claude mcp add --transport http --scope user plaintiffwire https://plaintiffwire.com/mcp
- Codex CLI:
codex mcp add plaintiffwire --url https://plaintiffwire.com/mcp
- Cursor — merge into ~/.cursor/mcp.json:
{"mcpServers":{"plaintiffwire":{"url":"https://plaintiffwire.com/mcp"}}}
- VS Code:
code --add-mcp '{"name":"plaintiffwire","type":"http","url":"https://plaintiffwire.com/mcp"}'
(if `code` is not on PATH, merge {"servers":{"plaintiffwire":{"type":"http","url":"https://plaintiffwire.com/mcp"}}} into .vscode/mcp.json)
- Windsurf — merge into ~/.codeium/windsurf/mcp_config.json:
{"mcpServers":{"plaintiffwire":{"serverUrl":"https://plaintiffwire.com/mcp"}}}
- Gemini CLI:
gemini mcp add -s user -t http plaintiffwire https://plaintiffwire.com/mcp
- Other clients: register a streamable-HTTP server at the URL above via your host's
standard mechanism. If you cannot run commands or edit files in this environment
(e.g. Claude Desktop), tell the user to add the URL under Settings → Connectors →
Add custom connector on claude.ai.
Step 3 — Read the config file back to verify it was written, then tell the user to start a
new session (running sessions do not reload MCP config).
There is no login and no key. In the new session, call tools/list and report the tool
names back to the user to confirm the connection.
Tools you should see: verdict_leaderboard, search_verdicts, recent_releases, search_releases
Record: https://legalmcps.com/server/plaintiffwire
Retrieved from the live endpoint by the register's own MCP probe — not self-reported.
verdict_leaderboardLaw firms ranked by total publicly announced verdict/settlement dollars: total, result count, and largest single result per firm.search_verdictsSearch tracked verdicts and settlements by firm name, state, and/or minimum amount (USD). Returns firm, amount, result type, state, case description, and date.recent_releasesLatest published releases on the wire: verdicts, settlements, filings, and firm news with links.search_releasesSearch published releases by keyword (title/summary), tort tag, and/or state.This badge reflects the current check result — it turns gray if the endpoint stops answering. Vendors are welcome to embed it.
<a href="https://legalmcps.com/server/plaintiffwire"><img src="https://legalmcps.com/badge/plaintiffwire.svg" alt="Verified live on the Legal MCP Register" width="220" height="64"></a>