Robin Saige we check the tools AI agents call

wasm-mcp

io.github.xyzzylabs/wasm-mcp

Read-only MCP server for the WebAssembly spec: instructions, types, sections, search, proposals.

— the operator's own registry description reported

Publisher io.github.xyzzylabs · first seen 2026-08-12 · endpoint https://mcp.xyzzylabs.ai/wasm/mcp

allow
verdict
stale-mid-shared
cluster
ok_tools
answers
9
tools served

Dependency rating derived

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

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

Reach — can an agent get to it?
answersalive_tools
latency218 ms
vs populationtypical
protocolstale
authopen
Use — can it use it?
tools9
vs populationmid
capabilities1
harnessA
Trust — can it rely on it?
identityshared
servers on its host2
verifiabilityunassessed
duplicate inventoryno
drift events0
answers trueno primary

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

instruction_get instruction_list instruction_search proposal_list section_get section_list spec_search spec_version type_get

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 & specific9/9
has a description9/9
description is substantive9/9
parameters are typed9/9
parameters are described9/9

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

2024-11-05
protocol version
session model
0.2.16
server version wasm-mcp

Capabilities: 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)
datetypewhat changed
2026-08-12outcomefirst probe: ok_tools
raw probe records
probed (UTC) outcomehttpmsprotocol
2026-08-14T20:00:21Zok_tools2002182024-11-05
2026-08-12T05:35:33Zok_tools2001722024-11-05

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