Skip to content

DocketTrail MCP server

com.dockettrail/dockettraildockettrail.comstreamable-httpv1.1.0Scanned

Healthcare transaction reviews, CON projects and nonprofit facility notices, with agency sources.

5 tools: 1 change things and 4 only read.

Tools: 0 delete, 0 irreversible, 1 write, 4 read.
  • Reads private data · 3
  • Reads text others write · 1
  • 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.
Govern this server →

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 DocketTrail MCP server can do

The DocketTrail MCP server is published by dockettrail.com, a domain the MCP Registry verified. It has 5 tools. It can create or change data (1 tool: review_stats), but cannot delete data. 4 tools only read.

3 tools read private data (get_proceeding, list_changes and find_organization); 1 tool brings in text other people can write (search_proceedings).

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, and its tools changed 2 times since Anlyon Radar first saw them.

Last scanned Nov 19, 2026, version 1.1.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.

5 tools

Changes things 1Claude Code: ask
  • review_statsHow reviews end and how long they take, computed from the records: per program, outcomes in the agency's own words with counts, shares (waived, taken to a cost and market impact re…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
    How reviews end and how long they take, computed from the records: per program, outcomes in the agency's own words with counts, shares (waived, taken to a cost and market impact review, approved with conditions, follow-up reviews) and durations in days (median, 25th to 75th percentile, range, n) over proceedings carrying both agency dates; deals reviewed in more than one state; the organizations in the most proceedings. Where n is under 5 the cases are listed instead of a median. Each figure names the list (href) behind it; the method is at https://dockettrail.com/stats#method. Every result points at the records it was computed from (href), each of which carries its source_url. Nothing is estimated or predicted. Covers healthcare transaction reviews (OR, CA, MA, NM, WA, MN), certificate-of-need projects (WA, IA, IL, FL, NC, HI, MO, GA, SC, VA, KY, DE, DC) and nonprofit health facility notices (CA, GA) only (see https://dockettrail.com/coverage for what is tracked and what was checked and not tracked). Every result is a public agency record, in the agency's own words, with source_url (the agency page it was read from) and the day DocketTrail observed it (observed_day, first_seen_at, last_checked_at; UTC). Nothing here is legal advice, and absence from the data is not a claim that no review exists.

    Annotations the server declares

    • title: How reviews go
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
Only reads 4Show 4 read-only tools
  • find_organizationFind an organization by name (its canonical name or any name it files under, as the agency printed it), or open one by slug to see its transactions, the names it files under in eac…Reads private dataNo findings

    Why it is in this group

    • The name "find_organization" says "find": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "find" and "file": it reads files.
    Description, as the server wrote it
    Find an organization by name (its canonical name or any name it files under, as the agency printed it), or open one by slug to see its transactions, the names it files under in each state and how each was matched. Organizations are linked across states only from a reviewed list, never by a name that looks alike. Covers healthcare transaction reviews (OR, CA, MA, NM, WA, MN), certificate-of-need projects (WA, IA, IL, FL, NC, HI, MO, GA, SC, VA, KY, DE, DC) and nonprofit health facility notices (CA, GA) only (see https://dockettrail.com/coverage for what is tracked and what was checked and not tracked). Every result is a public agency record, in the agency's own words, with source_url (the agency page it was read from) and the day DocketTrail observed it (observed_day, first_seen_at, last_checked_at; UTC). Nothing here is legal advice, and absence from the data is not a claim that no review exists.

    Annotations the server declares

    • title: Find an organization
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_proceedingOne transaction by the slug of its DocketTrail page (the transaction_slug of a search result): every state proceeding in it with the agency's wording and source link, the full trai…Reads private dataNo findings

    Why it is in this group

    • The name "get_proceeding" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "document": it reads documents.
    Description, as the server wrote it
    One transaction by the slug of its DocketTrail page (the transaction_slug of a search result): every state proceeding in it with the agency's wording and source link, the full trail of dated events (as the agency published or printed them), documents, and the changes DocketTrail observed. Covers healthcare transaction reviews (OR, CA, MA, NM, WA, MN), certificate-of-need projects (WA, IA, IL, FL, NC, HI, MO, GA, SC, VA, KY, DE, DC) and nonprofit health facility notices (CA, GA) only (see https://dockettrail.com/coverage for what is tracked and what was checked and not tracked). Every result is a public agency record, in the agency's own words, with source_url (the agency page it was read from) and the day DocketTrail observed it (observed_day, first_seen_at, last_checked_at; UTC). Nothing here is legal advice, and absence from the data is not a claim that no review exists.

    Annotations the server declares

    • title: Get a proceeding
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • list_changesWhat changed, newest first: new proceedings, the agency's wording changed (before and after, verbatim), new events, new documents.Reads private dataNo findings

    Why it is in this group

    • The name "list_changes" says "list": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "document": it reads documents.
    Description, as the server wrote it
    What changed, newest first: new proceedings, the agency's wording changed (before and after, verbatim), new events, new documents. Dated by the day DocketTrail observed the change on a check of the agency's page, not the day it happened. Without a key: the last 30 days, filtered by state, program and kind. A founding key reads the full history and adds org, agency, q and since. Covers healthcare transaction reviews (OR, CA, MA, NM, WA, MN), certificate-of-need projects (WA, IA, IL, FL, NC, HI, MO, GA, SC, VA, KY, DE, DC) and nonprofit health facility notices (CA, GA) only (see https://dockettrail.com/coverage for what is tracked and what was checked and not tracked). Every result is a public agency record, in the agency's own words, with source_url (the agency page it was read from) and the day DocketTrail observed it (observed_day, first_seen_at, last_checked_at; UTC). Nothing here is legal advice, and absence from the data is not a claim that no review exists.

    Annotations the server declares

    • title: List changes
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • search_proceedingsList healthcare transaction reviews, certificate-of-need projects and nonprofit health facility notices (one row per state proceeding, newest development first): parties as filed, …Reads text others writeNo findings

    Why it is in this group

    • The name "search_proceedings" says "search": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "list" and "review": it reads comments, which other people can write.
    Description, as the server wrote it
    List healthcare transaction reviews, certificate-of-need projects and nonprofit health facility notices (one row per state proceeding, newest development first): parties as filed, the agency and program, its status in its own words, stage, latest dated event, the agency page (source_url) and the DocketTrail page (url). Filter by state, program and status; a founding key adds org, agency, q (keyword) and since. Use get_proceeding for one transaction in full. Covers healthcare transaction reviews (OR, CA, MA, NM, WA, MN), certificate-of-need projects (WA, IA, IL, FL, NC, HI, MO, GA, SC, VA, KY, DE, DC) and nonprofit health facility notices (CA, GA) only (see https://dockettrail.com/coverage for what is tracked and what was checked and not tracked). Every result is a public agency record, in the agency's own words, with source_url (the agency page it was read from) and the day DocketTrail observed it (observed_day, first_seen_at, last_checked_at; UTC). Nothing here is legal advice, and absence from the data is not a claim that no review exists.

    Annotations the server declares

    • title: Search proceedings
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

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 outbound.

Reads private data3
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
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.

Tools listed without sign-in

Looked at Nov 19, 2026, 17:23 UTC, unchanged since Nov 5, 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.

    Matched text

    https://dockettrail.com/mcp: tools/list returned 5 tools to an anonymous client, including review_stats (write)

    What this check looks for

Posture changes

  1. Nov 5, 2026
    • Tools that change things, listed without credentials: 0 to 1

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.

  1. Tools5 changed.~5 changedView diff
  2. Tools1 added, 4 changed.+1 added~4 changedView diff
  3. PostureRemote posture changed. Tools that change things, listed without credentials: 0 -> 1.View diff
    • Tools that change things, listed without credentials: 0 to 1

Install

Pinned to version 1.1.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http dockettrail https://dockettrail.com/mcp
claude mcp add --transport http dockettrail https://dockettrail.com/mcp

Run 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.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__dockettrail__search_proceedings",
      "mcp__dockettrail__get_proceeding",
      "mcp__dockettrail__list_changes",
      "mcp__dockettrail__find_organization"
    ],
    "ask": [
      "mcp__dockettrail__review_stats"
    ],
    "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 dockettrail. Review it before you use it.

Capability tags behind 4 rules
  • mcp__dockettrail__search_proceedings untrusted-input
  • mcp__dockettrail__get_proceeding private-data
  • mcp__dockettrail__list_changes private-data
  • mcp__dockettrail__find_organization 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/com.dockettrail/dockettrail/verify?hash=6e983afa1ca920a2dee60f3ff74a447341214c0bebdd491fb95ff720f380ebe3" | jq -e '.changed == false'

Pinned hash 6e983afa1ca9, from Nov 19, 2026, 02:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.dockettrail/dockettrail/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.dockettrail/dockettrail
[![Anlyon Radar](https://radar.anlyon.com/badge/com.dockettrail/dockettrail.svg)](https://radar.anlyon.com/servers/com.dockettrail/dockettrail)

Source: MCP Registry. Synced Nov 5, 2026, 06:17 UTC.

DocketTrail MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the DocketTrail MCP server safe?

No scan can promise that. What its definitions show: 5 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 DocketTrail MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the DocketTrail 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 DocketTrail MCP server have?

5 tools: 1 write, 4 read. review_stats, search_proceedings, get_proceeding, list_changes and find_organization.

Does the DocketTrail MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the DocketTrail MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the DocketTrail MCP server changed its tools?

Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 19, 2026. Every change is on this page and in its Atom feed.