Should my agent depend on the MCP server app.toofi/dental-planning?

Verdict: allow — stale-mid-solo — safe to depend on As of 2026-08-15T11:28:18Z: a dated observation with receipts, not a warranty.

Toofi Dental Planning MCP

app.toofi/dental-planning

Agent-native dental planning MCP for plan drafts, presentations, and price estimates.

— the operator's own registry description reported

Publisher app.toofi · first seen 2026-08-12 · endpoint https://toofi.app/mcp

allow

verdict

stale-mid-solo

cluster

ok_tools

answers

tools served

Dependency rating derived

allow — stale-mid-solo — safe to depend on

Cluster stale-mid-solo · distinctiveness 0.495 (moderate). Every figure is a percentile or class within the 11,094-server census — see the whole spectrum.

Reach — can an agent get to it?

answersalive_tools

latency284 ms

vs populationtypical

protocolbehind

authopen

Use — can it use it?

tools32

vs populationmid

capabilities3

harnessA

Trust — can it rely on it?

identitysolo

servers on its host1

verifiabilityunassessed

duplicate inventoryno

drift events0

answers trueno primary

🔏 Signed receipt rr_d5943ae25ecdd8c007cdca41 · 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.

Tools last seen

claim_agent_checkout_key create_agent_checkout_session discover_capabilities example_en example_pl example_ru example_sk example_ua example_uk generate_dental_treatment_plan_pdf generate_patient_presentation generate_price_estimate generate_treatment_plan_draft get_agent_billing_quote get_agent_credit_balance get_demo_patient get_demo_plan get_demo_presentation get_dental_plan_operation_status get_example_result get_patient get_plan get_status import_price_csv list_audit_receipts list_demo_patients list_demo_plans list_patients list_plans lookup_dental_procedures preview_plan_draft_schema start_pano_markup

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 check	tools passing	ok
name is clear & specific	32/32	✓
has a description	32/32	✓
description is substantive	31/32	31/32
parameters are typed	32/32	✓
parameters are described	25/32	25/32

32 of 32 tools graded · 32 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

2026-05-12

server version toofi

Capabilities: prompts resources tools

Drift

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

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)

date	type	what changed
2026-08-12	outcome	first probe: ok_tools

raw probe records

probed (UTC)	outcome	http	ms	protocol
2026-08-14T19:57:47Z	ok_tools	200	284	2025-03-26
2026-08-12T05:33:04Z	ok_tools	200	198	2025-03-26

Watch or embed this verdict

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/app.toofi/dental-planning.svg)](https://robinsaige.com/s/app.toofi/dental-planning)

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