Docket Nexus
REMOTE · MCP.DOCKETNEXUS.COM · SCANNED SEP 25
Search public U.S. federal litigation: companies, cases, dockets and document metadata.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability79
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 787 tokens (~131/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management30
- Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the Docket Nexus MCP server?
Docket Nexus is a hosted endpoint at https://mcp.docketnexus.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.docketnexus.com
claude mcp add --transport http com-docketnexus-docketnexus 'https://mcp.docketnexus.com/mcp'
{
"mcpServers": {
"com-docketnexus-docketnexus": {
"url": "https://mcp.docketnexus.com/mcp"
}
}
} {
"servers": {
"com-docketnexus-docketnexus": {
"type": "http",
"url": "https://mcp.docketnexus.com/mcp"
}
}
} [mcp_servers.com-docketnexus-docketnexus] url = "https://mcp.docketnexus.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-docketnexus-docketnexus": {
"type": "remote",
"url": "https://mcp.docketnexus.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-docketnexus-docketnexus --url 'https://mcp.docketnexus.com/mcp' --transport streamable-http
mcp_servers:
com-docketnexus-docketnexus:
url: "https://mcp.docketnexus.com/mcp" {
"McpServers": {
"com-docketnexus-docketnexus": {
"Transport": "http",
"Url": "https://mcp.docketnexus.com/mcp"
}
}
} assistant mcp add com-docketnexus-docketnexus -t streamable-http -u 'https://mcp.docketnexus.com/mcp'
{
"mcpServers": {
"com-docketnexus-docketnexus": {
"type": "http",
"url": "https://mcp.docketnexus.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +3
- Schema quality: pass → fail ▼ functional
- Tool coverage: 0% → 100% ▲ functional
- Stability: unverified → 0.03 ▲ functional
- Schema quality: good → excellent functional
- Server version: 0.1.0-local → 1.0.0 functional
- “get_case” reworded the description of “case_url” cosmetic
- “get_case_docket” reworded the description of “case_url” cosmetic
- “get_case_docket” reworded the description of “cursor” cosmetic
- “get_case_docket” reworded the description of “limit” cosmetic
- “get_company” reworded the description of “slug” cosmetic
- “get_company_cases” reworded the description of “court” cosmetic
- “get_company_cases” reworded the description of “cursor” cosmetic
- “get_company_cases” reworded the description of “limit” cosmetic
- “get_company_cases” reworded the description of “nature_of_suit” cosmetic
- “get_company_cases” reworded the description of “slug” cosmetic
- “get_company_cases” reworded the description of “sort” cosmetic
- “get_document” reworded the description of “document_id” cosmetic
- “search_cases” reworded the description of “cursor” cosmetic
- “search_cases” reworded the description of “limit” cosmetic
- “search_cases” reworded the description of “query” cosmetic
- Tool “get_case” changed its title: Case detail cosmetic
- Tool “get_case_docket” changed its title: Case docket entries cosmetic
- Tool “get_company” changed its title: Company litigation profile cosmetic
- Tool “get_company_cases” changed its title: Cases involving a company cosmetic
- Tool “get_document” changed its title: Docket document metadata cosmetic
- Tool “search_cases” changed its title: Search federal cases cosmetic
- 16 Sept 26 69
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 25 Sept 2026 · Probed https://mcp.docketnexus.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=docketnexus.com | CN=WE1,O=Google Trust Services,C=US | 24 Sept 2026 | 23 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | f69294bf728622980e998f4f29dd923c |
| SANs: docketnexus.com, *.docketnexus.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.docketnexus.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| docketnexus.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.docketnexus.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.docketnexus.com/mcp | HTTPS enforced | 301 | https://mcp.docketnexus.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_case Case detail ~106
Get a public case by its Docket Nexus URL (https://docketnexus.com/case/.../): caption, court, docket number, dates, judge, cause, nature of suit, parties as shown on the case page, and disposition when recorded.
| Name | Type | Req | Description |
|---|---|---|---|
| case_url | string | yes | Full Docket Nexus case URL, e.g. https://docketnexus.com/case/<slug>-<id>/ . Returned as canonical_url by search_cases and get_company_cases. |
No output schema declared.
No examples provided.
get_case_docket Case docket entries ~110
List a public case's docket entries newest first, with document availability. Paginate with next_cursor. At most 50 per call. Entries the site does not publish are omitted and only counted.
| Name | Type | Req | Description |
|---|---|---|---|
| case_url | string | yes | Full Docket Nexus case URL, as accepted by get_case. |
| cursor | – | – | Opaque pagination token from a previous call's next_cursor. Omit for the first page. |
| limit | – | – | Entries to return, 1-50. Defaults to 50. |
No output schema declared.
No examples provided.
get_company Company litigation profile ~93
Get a public company's Docket Nexus profile by slug (e.g. 'acme-widgets-inc'): name, industry, number of linked cases, verified public-company identity when on the verified roster, and top case types and courts.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | Docket Nexus company slug, lowercase and hyphenated, as it appears in a /party/<slug>/ URL (e.g. '3m-company'). |
No output schema declared.
No examples provided.
get_company_cases Cases involving a company ~183
List public cases linked to a company, newest or oldest first, optionally filtered by nature of suit or court. Paginate with next_cursor. At most 25 per call.
| Name | Type | Req | Description |
|---|---|---|---|
| court | – | – | Filter to one court as shown on the company page (e.g. 'District Court, N.D. Alabama'). |
| cursor | – | – | Opaque pagination token from a previous call's next_cursor. Omit for the first page. |
| limit | – | – | Cases to return, 1-25. Defaults to 25. |
| nature_of_suit | – | – | Filter to one nature-of-suit category as shown on the company page (e.g. 'Product Liability'). |
| slug | string | yes | Docket Nexus company slug, as used by get_company. |
| sort | string | – | Order by case filing date. 'newest' (default) or 'oldest'. |
No output schema declared.
No examples provided.
get_document Docket document metadata ~82
Get public metadata for a docket document by its Docket Nexus document id: entry, date, description, page count, availability and parent case. Metadata only; no document text.
| Name | Type | Req | Description |
|---|---|---|---|
| document_id | integer | yes | Docket Nexus document id, as returned in a get_case_docket entry's document_id field. Metadata only is returned; document text is never served. |
No output schema declared.
No examples provided.
search_cases Search federal cases ~154
Search public cases by caption words, 'A v. B', or a federal docket number WITH its office prefix (e.g. 1:24-cv-01234). Results are newest first, at most 25 per call; paginate with next_cursor.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | – | – | Opaque pagination token from a previous call's next_cursor. Omit for the first page. |
| limit | – | – | Results to return, 1-25. Defaults to 25. |
| query | string | yes | Caption words, an 'A v. B' party pairing, or a federal docket number INCLUDING its office prefix (e.g. '1:24-cv-01234'). A docket number without the office prefix is refused. |
No output schema declared.
No examples provided.
What is the Docket Nexus MCP server?
Docket Nexus is an MCP server listed in the public MCP registry as com.docketnexus/docketnexus. Search public U.S. federal litigation: companies, cases, dockets and document metadata. This page covers its hosted endpoint (https://mcp.docketnexus.com/mcp).
Is the Docket Nexus MCP server safe to use?
Docket Nexus scores 76 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Docket Nexus MCP server expose?
Docket Nexus exposes 6 tools: get_company, get_company_cases, get_case, get_case_docket, get_document, search_cases. Their descriptions and schemas cost roughly 728 tokens of context every time the server is loaded.
Does the Docket Nexus MCP server require authentication?
No. We connected to Docket Nexus without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Docket Nexus MCP server still maintained?
Docket Nexus is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.