General Tools

docketyard.org

Provides general-purpose tools through the Model Context Protocol.

1 endpoint6 known toolsFirst detected September 23, 2026Last detected September 23, 2026

ENDPOINT 1

https://docketyard.org/mcp

No auth detected

MCP server metadata

Name: docketyard
Version: v2026.09.28

Capabilities

tools

Server instructions

Docket Yard is a public record of proceedings before the U.S. Surface Transportation Board (STB), the federal agency regulating freight rail. It is operated by RMI Valuation, LLC and is NOT the STB; every record links to the agency's own PDF, which is authoritative. When you use these tools, carry these with the answer: - Quote, do not infer. Dates, captions, summaries and comments are reproduced as the Board printed them. Nothing in this record says what any party argued or what a filing means. A procedural filing takes no position regardless of who filed it. - Say what is not covered. Coverage is not uniform across time — call `coverage` and repeat what it says rather than implying the record is complete. - Cite the Board's file. Every record carries the STB's own URL; prefer it when the user needs the source, and give the docketyard.org address when they need a stable citation. - Search results are capped and are not counts. For "how many", call `count_filings`, and repeat what it says it did not count. - Page text is served so it can be read and quoted, never as the Board's words. `read_page` hands over a page as read from the Board's document, labelled with who read it; repeat that label and the link to the Board's own file with anything you quote. Docket Yard serves the text as read from the Board's documents. An AI's reading or summary of it may be wrong, and what an assistant does with this text is outside Docket Yard's control. Before relying on it, review the document itself: the Board's own file is linked. The text is held back from Docket Yard's public-domain dedication: it is served for reading on a user's request, not for bulk collection or training. - If a tool returns nothing, say the record holds nothing — never fill the gap from memory. Inventing a docket number or a service date is the specific failure this surface exists to prevent.

Known tools 6

search_the_record

Search proceedings, parties, decisions and environmental comments by their own words, and the pages of the Board's documents by their machine-read text.

Inferred read-only

get_docket_sheet

One chronological sheet for a proceeding: its filings, decisions and environmental comments, each with the Board's own file.

Inferred read-only

get_environmental_comment

One environmental comment by its Board number (`EI-34282`), with the commenter's own words as the Board printed them.

Inferred read-only

read_page

The text of one page, or a few, of a filing's, decision's or environmental comment's file, as read from the Board's document (its own text layer, or OCR of a scan), labelled with who read it, with the Board's own file and the scan.

Inferred read-only

count_filings

How many filings the Board typed a given way — `Consummation Notice`, `Trail Use Agreement Reached` — and in how many proceedings, optionally within a docket prefix (`AB`) and a filed-date range, and how many of those proceedings also hold a filing of a second type.

Inferred read-only

coverage

The measured extent of the record: how many proceedings, filings, decisions and comments, the dates they span, and what is not yet held.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.docketyard]
url = "https://docketyard.org/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "docketyard": {
      "type": "http",
      "url": "https://docketyard.org/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: docketyard
Remote MCP URL: https://docketyard.org/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "docketyard": {
      "url": "https://docketyard.org/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "docketyard": {
      "type": "http",
      "url": "https://docketyard.org/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "docketyard",
  "transport": "streamable-http",
  "url": "https://docketyard.org/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.