Robin Saige we check the tools AI agents call

Molt2Meet

io.github.molt2meet-org/molt2meet

Dispatch real-world physical tasks to verified human operators. Escrow or direct-settlement.

— the operator's own registry description reported

Publisher io.github.molt2meet-org · first seen 2026-08-12 · endpoint https://molt.molt2meet.com/mcp

allow
verdict
rich-slow-solo
cluster
ok_tools
answers
54
tools served

Dependency rating derived

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

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

Does it answer? Q1 · observed
answersalive_tools
latency398 ms
vs populationslow
protocolcurrent
authopen
Can it be used? Q4 · observed
tools54
vs populationhigh
capabilities2
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_a30dfcc70d297a10e16d8e7b · 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?rich-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 (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
action25changes the worldno true answer exists; we check the CONTRACT (destructive/read-only/idempotent declarations, error legibility) and never fire real actions
retrieval-public16serves public factstruth-checkable against a public source — the V-ladder applies in full
unclassified7not classifiable from its textTier-1 only until its tools describe themselves
orchestration4routes other toolsidentity + fronted-service disclosure checks (gateway vs costume)
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

acknowledge_direct_settlement_task add_contact_method add_service_interest add_task_review approve_physical_task_completion approve_reschedule approve_task_review cancel_physical_task cancel_task_with_settlement check_task_funding checkout_wallet_deposit create_api_key dispatch_physical_task dispute_direct_settlement_task fund_task fund_wallet get_agent_profile get_bank_transfer_details get_decision_requests get_legal_documents get_pending_actions get_physical_task_details get_support_requests get_task_events get_task_history get_task_proofs get_waitlist_status get_wallet_balance get_wallet_transactions join_country_waitlist list_countries list_currencies list_locales list_physical_tasks list_reschedule_requests list_service_capabilities list_service_categories list_service_interests list_wallets open_task_dispute publish_task register_agent reject_reschedule reject_task_review reply_to_support_request request_reschedule request_task_quote resolve_decision_request revoke_api_key submit_support_request test_task_webhook update_agent_profile update_task_location update_task_webhook

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 & specific54/54
has a description54/54
description is substantive54/54
parameters are typed54/54
parameters are described54/54

54 of 54 tools graded · 54 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-06-18
protocol version
session model
1.0.0
server version Molt2Meet

Capabilities: logging 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:52Zok_tools2003982025-06-18
2026-08-12T05:35:09Zok_tools2003942025-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.molt2meet-org/molt2meet.svg)](https://robinsaige.com/s/io.github.molt2meet-org/molt2meet)

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