perfectplaintiff.com injury lawsuit data MCP server
io.github.Phenotype-Brandvoz/perfectplaintiff-injury-lawsuit-dataPhenotype-Brandvozstreamable-httpv1.0.0Scanned
Sourced figures on U.S. injury lawsuits by state, court and case type, each with its source.
9 tools: 1 change things and 8 only read.
- Reads private data · 2
- Reads text others write · 0
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here changes things. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the perfectplaintiff.com injury lawsuit data MCP server can do
The perfectplaintiff.com injury lawsuit data MCP server is published by the GitHub account Phenotype-Brandvoz. It has 9 tools. It can create or change data (1 tool: how_to_cite), but cannot delete data. 8 tools only read.
2 tools read private data (list_datasets and query_dataset).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 18, 2026, version 1.0.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
9 tools
Changes things 1Claude Code: ask
how_to_citeThe credit line, the underlying sources and their reuse terms for a finding, a dataset or a law firm profile.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it The credit line, the underlying sources and their reuse terms for a finding, a dataset or a law firm profile.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- title: How to cite
Only reads 8Show 8 read-only tools
fetchThe full text of one search result: the figure in a sentence with its place, period, label and source, how it was calculated, the known limits, the page and the credit line.No findings
Why it is in this group
- The name "fetch" says "fetch": a word for reading.
Description, as the server wrote it The full text of one search result: the figure in a sentence with its place, period, label and source, how it was calculated, the known limits, the page and the credit line.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- title: Fetch one result
get_case_outcomesEvery published figure for one place and kind of case: cases filed and closed, trials, plaintiff wins at trial, the share settled and days to closing, each with its label and sourc…No findings
Why it is in this group
- The name "get_case_outcomes" says "get": a word for reading.
Description, as the server wrote it Every published figure for one place and kind of case: cases filed and closed, trials, plaintiff wins at trial, the share settled and days to closing, each with its label and source. Without a year: the latest year and multi-year figures.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- title: How cases ended in one place
get_findingOne finding as data: figure, statement, label (Sourced, Computed or Estimated), sources with the date retrieved and reuse terms, how it was calculated, limits, credit line, page an…No findings
Why it is in this group
- The name "get_finding" says "get": a word for reading.
Description, as the server wrote it One finding as data: figure, statement, label (Sourced, Computed or Estimated), sources with the date retrieved and reuse terms, how it was calculated, limits, credit line, page and CSV.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- title: Get one finding
get_law_firm_profileWhat named public sources state about one of 203 injury, mass tort and class action law firms: founding, offices, kinds of case, slogan and reported results.No findings
Why it is in this group
- The name "get_law_firm_profile" says "get": a word for reading.
Description, as the server wrote it What named public sources state about one of 203 injury, mass tort and class action law firms: founding, offices, kinds of case, slogan and reported results. Each row says who states it. Not a rating; a firm's claims are not checked.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- title: Public facts about a law firm
list_datasetsThe datasets in the data library with their files, columns and row counts: federal injury cases by court, state and year, class actions, multidistrict litigation, judges, tort clai…Reads private dataNo findings
Why it is in this group
- The name "list_datasets" says "list": a word for reading.
What it can reach
- private-dataThe description's first sentence says "file": it reads files.
Description, as the server wrote it The datasets in the data library with their files, columns and row counts: federal injury cases by court, state and year, class actions, multidistrict litigation, judges, tort claim payments and more. Filter by words.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- title: List the datasets
list_findingsThe newsroom's findings (one figure in a sentence each), for the nation, one of the states covered, or New York City, and optionally one kind of case.No findings
Why it is in this group
- The name "list_findings" says "list": a word for reading.
Description, as the server wrote it The newsroom's findings (one figure in a sentence each), for the nation, one of the states covered, or New York City, and optionally one kind of case.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- title: List the findings
query_datasetRows of one CSV file from the data library, filtered by column values.Reads private dataNo findings
Why it is in this group
- The name "query_dataset" says "query": a word for reading.
What it can reach
- private-dataThe description's first sentence says "file": it reads files.
- private-dataThe input names a file (input.file), and the tool reads: it reads files.
Description, as the server wrote it Rows of one CSV file from the data library, filtered by column values. Use list_datasets to get a file path and its columns. Returns at most 200 rows a call; use offset for more.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- title: Query a CSV file
searchFind figures about injury lawsuits (one sourced figure each), datasets and law firm profiles by words: a subject, a measure, a state, a firm.No findings
Why it is in this group
- The name "search" says "search": a word for reading.
Description, as the server wrote it Find figures about injury lawsuits (one sourced figure each), datasets and law firm profiles by words: a subject, a measure, a state, a firm. Returns ids to pass to fetch. Example: "plaintiff win rate at trial Texas", "Morgan & Morgan".
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- title: Search the data library
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged untrusted-input or outbound.
- Reads private data2
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 19, 2026, 17:19 UTC, unchanged since Nov 19, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 1
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://perfectplaintiff.com/mcp: tools/list returned 9 tools to an anonymous client, including how_to_cite (write)
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http perfectplaintiff-injury-lawsuit-data https://perfectplaintiff.com/mcpclaude mcp add --transport http perfectplaintiff-injury-lawsuit-data https://perfectplaintiff.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__perfectplaintiff-injury-lawsuit-data__search",
"mcp__perfectplaintiff-injury-lawsuit-data__fetch",
"mcp__perfectplaintiff-injury-lawsuit-data__list_findings",
"mcp__perfectplaintiff-injury-lawsuit-data__get_finding",
"mcp__perfectplaintiff-injury-lawsuit-data__list_datasets",
"mcp__perfectplaintiff-injury-lawsuit-data__query_dataset",
"mcp__perfectplaintiff-injury-lawsuit-data__get_case_outcomes",
"mcp__perfectplaintiff-injury-lawsuit-data__get_law_firm_profile"
],
"ask": [
"mcp__perfectplaintiff-injury-lawsuit-data__how_to_cite"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as perfectplaintiff-injury-lawsuit-data. Review it before you use it.
Capability tags behind 2 rules
- mcp__perfectplaintiff-injury-lawsuit-data__list_datasets private-data
- mcp__perfectplaintiff-injury-lawsuit-data__query_dataset private-data
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.Phenotype-Brandvoz/perfectplaintiff-injury-lawsuit-data/verify?hash=e293c6ae240c14ff99d3b610ab14eeffada84384091999c4134d9e9dfd9eb144" | jq -e '.changed == false'Pinned hash e293c6ae240c, from Nov 18, 2026, 23:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.Phenotype-Brandvoz/perfectplaintiff-injury-lawsuit-data/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.Phenotype-Brandvoz/perfectplaintiff-injury-lawsuit-data)Source: MCP Registry. Synced Nov 18, 2026, 23:17 UTC.
perfectplaintiff.com injury lawsuit data MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the perfectplaintiff.com injury lawsuit data MCP server safe?
- No scan can promise that. What its definitions show: 9 tools, 1 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the perfectplaintiff.com injury lawsuit data MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the perfectplaintiff.com injury lawsuit data MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the perfectplaintiff.com injury lawsuit data MCP server have?
- 9 tools: 1 write, 8 read. how_to_cite, search, fetch, list_findings, get_finding, list_datasets, query_dataset, get_case_outcomes and 1 more.
Does the perfectplaintiff.com injury lawsuit data MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the perfectplaintiff.com injury lawsuit data MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the perfectplaintiff.com injury lawsuit data MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 18, 2026.