Robin Saige we check the tools AI agents call

Well

io.github.WellApp-ai/well-mcp

Connect your AI to your Well financial data - invoices, companies, contacts.

— the operator's own registry description reported

Publisher io.github.WellApp-ai · first seen 2026-08-12 · endpoint https://api.wellapp.ai/v1/mcp

allow
verdict
mid-slow-solo
cluster
ok_tools
answers
26
tools served

Dependency rating derived

allow
allow — alive & usable · action ● · V n/a
allow — because answers ●, 26 tools legible (band A) ●, no confirmed drift in 2 probes ●; not yet checked: truth (1 attempts unverifiable, 0 disagreements)

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

Does it answer? Q1 · observed
answersalive_tools
latency540 ms
vs populationslow
protocolcurrent
authopen
Can it be used? Q4 · observed
tools26
vs populationmid
capabilities2
harnessA
Did it hold when checked? Q3–Q4 · derived
identitysolo
servers on its host1
verifiabilityunassessed
duplicate inventoryno
drift events0
answers true0/0 agree

🔏 Signed receipt rr_8340f76265ec3415891acfac · 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?action ● evidence ↓
Q3Can it be checked?V n/a for this kind ◐evidence ↓
Q4Did it hold?harness A · truth not yet run · no drift ●evidence ↓
Q5What company does it keep?mid-slow-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 (2 events)
datetypewhat changed
2026-08-14inventorytools 25 → 26
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
action16changes the worldno true answer exists; we check the CONTRACT (destructive/read-only/idempotent declarations, error legibility) and never fire real actions
retrieval-public7serves public factstruth-checkable against a public source — the V-ladder applies in full
computational1deterministic transformsself-checkable by re-computation and known-answer tests
generative1creates contentno answer key exists; disclosure + stability checks, never truth verdicts
predictive1claims about the futurescoreable only in retrospect — the archive scores yesterday's predictions against today's outcome

Tools last seen observed

well_add_contact_channel well_create_company well_create_invoice_document well_create_invoice_from_data well_create_person well_delete_company well_delete_invoice well_delete_person well_get_cash_position well_get_cost_structure well_get_entity well_get_investment_holdings well_get_runway well_get_schema well_invoke_connector_tool well_list_connector_tools well_list_connectors well_list_workspaces well_query_records well_remove_contact_channel well_resolve_reconciliation_task well_resolve_register_diff_gap well_run_register_diff well_update_company well_update_invoice well_update_person

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 & specific26/26
has a description26/26
description is substantive26/26
parameters are typed26/26
parameters are described22/2622/26

26 of 26 tools graded · 26 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 yet confirmed — 1 attempt(s) currently unverifiable (rate limits, walls, or unmappable schemas — never counted against the server) · 0 disagreements.

claim classkeyverdictprimary source
fx-ratesEURUSDunverifiableecb-fx

Protocol conformance observed

2025-06-18
protocol version
session model
1.0.0
server version well-financial-mcp

Capabilities: resources 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:59:18Zok_tools2005402025-06-18
2026-08-12T05:34:31Zok_tools2003412025-06-18

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/io.github.WellApp-ai/well-mcp.svg)](https://robinsaige.com/s/io.github.WellApp-ai/well-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