DocketTrail

At a glance

Runs where

On their server. What you send to it goes to them.

What you need

Nothing: it answered without a login

Tools

5 tools

Its own safety labels

5 read-only

Memory it takes

About 2,600 tokens of your AI's memory, just for its tool descriptions

Largest answer

About 107.8 KB in our test

Tools that look alike

3 pairs of tools with nearly the same description, so the AI may pick the wrong one

Speed

Average answer in our test: 1.3 s

Tokens are an estimate: the characters in its tool names, descriptions and inputs, divided by 4. The exact number depends on your AI model. Safety labels are what the server says about itself. From our latest test, 5 Nov 2026.

Is DocketTrail MCP server safe?

• None of the hidden-instruction wordings we know were found in its 5 tool descriptions.
• Its error messages showed no secrets or internal details.
• All 5 of its tools are labeled read-only.
• Overall it scored 82/100 on 5 Nov 2026.

A test can only see what the server shows from outside, not what it does with your data behind the scenes. Connect servers from makers you trust.

What this test does not check

• Its source code and packages.
• What a tool quietly does behind the scenes, such as writing a file or calling another service.
• Instructions hidden inside live tool answers. We only look for those in tool descriptions.
• Hidden instructions worded in a way our list doesn't know yet.
• Tools that could change something. Those are read, never run.

What QAmcp can and can't see · How to tell if an MCP server is safe · Hidden instructions · Prompt injection

Known security advisories

It lists no public code, so there is nothing to look up in GitHub Security Advisories or OSV.dev. QAmcp tests how a server behaves. It does not scan source code.

What it can do

5 tools, in the server's own words.

Test results

Safe mode: only tools labeled read-only were run. How the test works

• !
  Ready for the newest MCP version

  1 warning

  • !Uses an older MCP version (2025-11-25). It works today, but it isn't on the July 2026 version (2026-07-28) yet.
  note
• !
  Every tool is described

  3 warnings

  • !search_proceedings and list_changes have nearly the same description (69% of their words are shared; the only difference: "list", "row", "development" vs "change", "changed", "new"), so an AI may not know which to pick
  • !get_proceeding and list_changes have nearly the same description (68% of their words are shared; the only difference: "slug", "search", "link" vs "changed", "newest", "new"), so an AI may not know which to pick
  • !get_proceeding and find_organization have nearly the same description (64% of their words are shared; the only difference: "proceeding", "search", "wording" vs "find", "organization", "name"), so an AI may not know which to pick
  note
• !
  Tools work with good inputs

  1 warning

  • !review_stats: Answered with about 108 KB of text. Many AI apps cut off tool answers this big, so the AI may never see the end of it.
  • and 4 more
  note
• !
  Fast enough

  1 warning

  • !review_stats: Slowest tool: review_stats (2.2 s): users will notice the wait
  • and 3 more
  note
• !
  Follows MCP best practices (not scored yet)

  1 tip (not scored)

  • !4 tools answer with structured data but don't declare its shape (outputSchema): search_proceedings, list_changes, find_organization, review_stats. If those answers change shape, nothing can catch it; with a schema, every answer is checked.
  note
• ✓
  ConnectsConnected in 647 ms
  pass
• ✓
  Lists its toolsFound 5 tools
  pass
• ✓
  Tools are labeled safe or dangerousEvery tool has a safety label
  pass
• ✓
  No known hidden instructionsNone of the hidden-instruction wordings we know were found in tool descriptions. New wordings can get past this check.
  pass
• ✓
  Bad inputs give a clean error

  All good

  • ✓search_proceedings: Refused wrong type for "state" with a clear error
  • ✓get_proceeding: Refused missing required input "slug" with a clear error
  • ✓get_proceeding: Refused wrong type for "slug" with a clear error
  • ✓list_changes: Refused wrong type for "state" with a clear error
  • ✓find_organization: Refused wrong type for "name" with a clear error
  • ✓review_stats: Refused wrong type for "state" with a clear error
  pass
• ✓
  Tools work together

  4 chains working

  • ✓review_stats → find_organization: find_organization found what review_stats returned (slug = "davita-inc-total-renal-care-wa")
  • ✓search_proceedings → get_proceeding: get_proceeding found what search_proceedings returned (slug = "wa-fkc-cowlitz")
  • ✓search_proceedings → find_organization: find_organization found what search_proceedings returned (slug = "fkc-cowlitz-wa")
  • ✓list_changes → get_proceeding: get_proceeding found what list_changes returned (slug = "wa-davita-9")
  pass
• ✓
  No secrets leakedChecked 18 error messages: no secrets or internal details
  pass

Test it yourself

Free and open source. Same checks, same score.

Show this score on GitHub

Free for every server in the directory. Paste this into your README: the badge shows the score from our latest test.

Score over time

• 5 Nov 202682

One test so far. New tests will show here.

Reviews

Coming soon: reviews from people who use DocketTrail, signed in with GitHub, one per person. Reviews never change the score.