Robin Saige we check the tools AI agents call

agentstack mcp

io.github.inity13/agentstack-mcp

Deterministic reasoning stack for AI agents: simulate, decide & compute, plus cross-domain tools.

— the operator's own registry description reported

Publisher io.github.inity13 · first seen 2026-08-12 · endpoint https://agentstack-mcp.pages.dev/mcp

allow
verdict
mid-fast-solo
cluster
ok_tools
answers
24
tools served

Dependency rating derived

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

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

Does it answer? Q1 · observed
answersalive_tools
latency46 ms
vs populationfast
protocolcurrent
authopen
Can it be used? Q4 · observed
tools24
vs populationmid
capabilities1
harnessB
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_efbfd164b4871ad71b153823 · 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?kind unknown ● evidence ↓
Q3Can it be checked?V n/a for this kind ◐evidence ↓
Q4Did it hold?harness B · truth not yet run · no drift ●evidence ↓
Q5What company does it keep?mid-fast-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
computational7deterministic transformsself-checkable by re-computation and known-answer tests
unclassified7not classifiable from its textTier-1 only until its tools describe themselves
action4changes the worldno true answer exists; we check the CONTRACT (destructive/read-only/idempotent declarations, error legibility) and never fire real actions
retrieval-public4serves public factstruth-checkable against a public source — the V-ladder applies in full
orchestration1routes other toolsidentity + fronted-service disclosure checks (gateway vs costume)
predictive1claims about the futurescoreable only in retrospect — the archive scores yesterday's predictions against today's outcome

Tools last seen observed

calc_business_days calc_compound_growth calc_currency_convert calc_depreciation calc_irr calc_list_metrics calc_loan_amortization calc_metric calc_npv decide decide_compare_two decide_list_methods decide_score decide_sensitivity evaluate_options_with_scenarios health_check list_capabilities plan_to_valuation sim_break_even sim_compare sim_list_templates sim_run sim_sensitivity stress_test_decision

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 B — usable, with rough edges.

legibility checktools passingok
name is clear & specific24/24
has a description24/24
description is substantive24/24
parameters are typed24/24
parameters are described5/245/24

24 of 24 tools graded · 24 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
tariff-dutyunmappedunverifiableus-hts

Protocol conformance observed

2025-06-18
protocol version
session model
1.0.0-edge
server version AgentStack

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:59:37Zok_tools200462025-06-18
2026-08-12T05:34:50Zok_tools200262025-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.inity13/agentstack-mcp.svg)](https://robinsaige.com/s/io.github.inity13/agentstack-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