Robin Saige we check the tools AI agents call

Bankruptcy Observer

com.bankruptcyobserver/mcp

US business bankruptcy MCP: filings, dockets, documents, case summaries. Free tier + subscription.

— the operator's own registry description reported

Publisher com.bankruptcyobserver · first seen 2026-08-12 · endpoint https://mcp.bankruptcyobserver.com/mcp

allow
verdict
stale-mid-solo
cluster
ok_tools
answers
18
tools served

Dependency rating derived

allow
allow — alive & usable · retrieval-public ● · V1 shows its work ◐
allow — because answers ●, 18 tools legible (band A) ●, no confirmed drift in 2 probes ●; not yet checked: truth (0 runs)

Cluster stale-mid-solo · distinctiveness 0.248 (typical). Every figure is a percentile or class within the 11,094-server censussee the whole spectrum.

Does it answer? Q1 · observed
answersalive_tools
latency347 ms
vs populationtypical
protocolbehind
authopen
Can it be used? Q4 · observed
tools18
vs populationmid
capabilities1
harnessA
Did it hold when checked? Q3–Q4 · derived
identitysolo
servers on its host1
verifiabilityunassessed
duplicate inventoryno
drift events0
answers trueno primary

🔏 Signed receipt rr_f60f430cfa9e984086d2b2b8 · ed25519 · key rs-rcpt-2026-08 — this rating is tamper-evident; an agent gets the full signature from check_server and can verify it against the published key.

Q1Does it answer?alive & usable — 2 probes ●evidence ↓
Q2What is it?retrieval-public ● evidence ↓
Q3Can it be checked?V1 shows its work ◐evidence ↓
Q4Did it hold?harness A · truth not yet run · no drift ●evidence ↓
Q5What company does it keep?stale-mid-solo · 1 on its host (context, not verdict) ◐evidence ↓

● observed · ◐ derived · ○ reported — the verdict synthesizes Q1–Q4; Q5 is context. Methodology →

History observed

Every probe we made, oldest → newest (2 shown, 2026-08-12 → 2026-08-14). Green answered · amber answered-but-walled · red no useful answer. A gap in our cadence is a gap in coverage, not evidence about the server.

changelog (1 events)
datetypewhat changed
2026-08-12outcomefirst probe: ok_tools

What kind of tools these are derived

Verification only means something relative to a tool's NATURE — an email-sender has no "true answer", a generator has no answer key. Classification evidence: classified from tool names/descriptions/annotations WE OBSERVED. What checking applies to each kind (the full methodology →):

naturetoolsmeaning what checking applies
retrieval-public12serves public factstruth-checkable against a public source — the V-ladder applies in full
action4changes the worldno true answer exists; we check the CONTRACT (destructive/read-only/idempotent declarations, error legibility) and never fire real actions
computational1deterministic transformsself-checkable by re-computation and known-answer tests
unclassified1not classifiable from its textTier-1 only until its tools describe themselves

Tools last seen observed

add_monitored_case_tool check_subscription_tool get_case_by_case_number_tool get_case_by_ein_tool get_case_summary_tool get_cases_by_date_range_tool get_cases_by_industry_tool get_cases_by_naics_tool get_cases_by_state_tool get_docket_entries_tool get_document_cost_tool get_document_tool get_recent_developments_tool list_monitored_cases_tool list_plans_tool purchase_plan_tool refresh_docket_tool search_bankruptcy_cases_tool

Harness readiness observed

Can an agent's harness pick this tool and call it correctly? Graded on the three things an agent reads — name, description, typed parameters. Band A — an agent can pick and call these reliably.

legibility checktools passingok
name is clear & specific18/18
has a description18/18
description is substantive16/1816/18
parameters are typed18/18
parameters are described9/189/18

18 of 18 tools graded · 18 with a captured input schema. RS-008, Tier-1 — no domain knowledge, applies to any tool. “Alive” is not the same as “usable”.

Truth checks observed

Not in the Tier-2 trade lane, or not yet checked. Tier-2 re-derives a server's answers against published primary sources — see truth checks.

Protocol conformance observed

2025-03-26
protocol version
session model
1.1.0
server version bko-mcp

Capabilities: tools

Drift observed

No confirmed drift on record. Baseline set 2026-08-14; changes appear here after human review.

raw probe records
probed (UTC) outcomehttpmsprotocol
2026-08-14T19:57:57Zok_tools2003472025-03-26
2026-08-12T05:33:13Zok_tools2004272025-03-26

Watch or embed this verdict

verdict badge

Operators: put the live verdict in your README — it updates with every census, links back here, and is a dated observation, never a warranty:

[![Robin Saige verdict](https://robinsaige.com/badge/com.bankruptcyobserver/mcp.svg)](https://robinsaige.com/s/com.bankruptcyobserver/mcp)

Depend on it? Subscribe to its change feed — outcome changes and confirmed drift, no account needed. Building on it? The full dossier as JSON — verdict, rating, truth checks, history — stable enough to gate CI on.

← overview