Ext Ops Panel
Open dashboard
Comparison

WebAssembly magic-byte check, file discarded vs io.github.telleroutlook/mcp-server

WebAssembly magic-byte check, file discarded is an MCP server published by sadri-dridi. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.telleroutlook/mcp-server is an MCP server published by telleroutlook. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-28. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
MarketplaceWebAssembly magic-byte check, file discardedio.github.telleroutlook/mcp-server
Official MCP Registry Listed
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 1.1.1
Downloads/month (npm): 1 326
Downloads/week (npm): 112
Forks (GitHub): 1
Stars (GitHub): 7
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

WebAssembly magic-byte check, file discarded vs io.github.telleroutlook/mcp-server
FactWebAssembly magic-byte check, file discardedio.github.telleroutlook/mcp-server
Marketplaces that list it11
Stars (GitHub) (differs)0 (worse)7 (better)
Forks (GitHub) (differs)0 (worse)1 (better)
Last releaseNot publishedNot published
Where it runs (differs)Remote server (agent-observatory-sensor.nolimit-observatory.workers.dev/s/wasm-magic/mcp)On your machine (@wasmagent/mcp-server)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
LicenceNot statedNot stated
Repository (differs)github.com/sadri-dridi/named-mcp-utilitiesgithub.com/wasmagent/wasmagent-js
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded 6 days agono remote endpoint we check

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

WebAssembly magic-byte check, file discarded

In its own words, on Official MCP Registry:

WebAssembly magic-byte check, file discarded

io.github.telleroutlook/mcp-server

In its own words, on Official MCP Registry:

WasmAgent MCP server — WASM-sandboxed code execution with capability manifests and Tasks API.

How to run each

WebAssembly magic-byte check, file discarded As a remote MCP server

Claude Code
claude mcp add --transport http wasm-magic https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/wasm-magic/mcp

io.github.telleroutlook/mcp-server As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio io-github-telleroutlook-mcp-server -- npx -y @wasmagent/mcp-server

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only WebAssembly magic-byte check, file discarded has a remote endpoint we check. How we check endpoints

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: WebAssembly magic-byte check, file discarded · What it can do: io.github.telleroutlook/mcp-server · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built