Robin Saige we check the tools AI agents call

MegaChad

io.github.megachadxyz/megachad

Burn-to-create looksmaxxing engine on MegaETH. 14 MCP tools for DeFi, NFTs, and burns.

— the operator's own registry description reported

Publisher io.github.megachadxyz · first seen 2026-08-12 · endpoint https://megachad.xyz/api/mcp

allow
verdict
rich-solo
cluster
ok_tools
answers
38
tools served

Dependency rating derived

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

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

Does it answer? Q1 · observed
answersalive_tools
latency118 ms
vs populationtypical
protocolcurrent
authopen
Can it be used? Q4 · observed
tools38
vs populationhigh
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_683fa83c590fa9dcddca39f0 · 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?V0 take its word ◐evidence ↓
Q4Did it hold?harness A · truth not yet run · no drift ●evidence ↓
Q5What company does it keep?rich-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-public15serves public factstruth-checkable against a public source — the V-ladder applies in full
action14changes the worldno true answer exists; we check the CONTRACT (destructive/read-only/idempotent declarations, error legibility) and never fire real actions
unclassified5not classifiable from its textTier-1 only until its tools describe themselves
orchestration4routes other toolsidentity + fronted-service disclosure checks (gateway vs costume)

Tools last seen observed

build_amm_add_liquidity_tx build_amm_swap_tx build_execute_tx build_propose_tx build_queue_tx build_staking_tx build_veto_tx build_vote_tx chat_with_megachad cross_chain_looksmaxx gasless_burn_info get_activity_feed get_agent_index get_agent_info get_amm_quote get_bridge_info get_chadboard get_emission_schedule get_gallery get_governance_proposal get_identity get_looksmaxx_plan get_looksmaxx_requirements get_megachad_stats get_megaeth_protocols get_nft_inventory get_nft_metadata get_portfolio get_price get_protocol_registry get_protocol_safety get_referral_stats get_staking_position get_swap_quote get_wallet_info list_governance_proposals register_early_access register_referral_agent

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 & specific38/38
has a description38/38
description is substantive38/38
parameters are typed38/38
parameters are described38/38

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

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:51Zok_tools2001182025-06-18
2026-08-12T05:35:08Zok_tools2002002025-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.megachadxyz/megachad.svg)](https://robinsaige.com/s/io.github.megachadxyz/megachad)

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