Skip to content
MCP server

WASM magic version, bytes discarded

Remote MCP server that checks whether WebAssembly magic and version bytes are valid

Install
Platforms
API
Runs
Remotely
Version
1.0.0
Listing updated
today

Similar MCP servers

About WASM magic version, bytes discarded

WASM magic version, bytes discarded is an MCP server for developer tools. It runs as a hosted remote server, so there is nothing to install locally.

wasm-ok is a remote Model Context Protocol server that tells an AI client whether a WebAssembly module header has a valid magic number and version. The server is reached over streamable HTTP at a hosted endpoint, so there is nothing to install locally.

The name and listing describe it as discarding the submitted bytes after the check, so only the verdict is meant to come back. The README gives no tool names, schema or response format, so the exact interface should be read from the endpoint itself.

It suits developers and agent builders who want a small, single-purpose validation step for WebAssembly inputs inside an automated workflow. It is one of a series of narrow single-check servers published under the same repository.

Install

Run in a terminal

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

Add to Settings → Connectors → Add custom connector

https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/wasm-ok/mcp
Install in CursorOpens Cursor, which asks you to confirm. Or add it by hand:

Add to ~/.cursor/mcp.json

{
  "mcpServers": {
    "wasm-ok": {
      "url": "https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/wasm-ok/mcp"
    }
  }
}
Install in VS CodeOpens VS Code, which asks you to confirm. Or add it by hand:

Add to .vscode/mcp.json

{
  "servers": {
    "wasm-ok": {
      "type": "http",
      "url": "https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/wasm-ok/mcp"
    }
  }
}

Add to ~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "wasm-ok": {
      "serverUrl": "https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/wasm-ok/mcp"
    }
  }
}

Add to your client's MCP settings (most use this shape)

{
  "mcpServers": {
    "wasm-ok": {
      "type": "http",
      "url": "https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/wasm-ok/mcp"
    }
  }
}

Using several servers? Build one config file with the MCP config generator.

What it does

Remote streamable HTTP endpoint
The server is hosted and reached over streamable HTTP, so MCP clients can connect without a local install.
WebAssembly header check
It checks the magic number and version bytes of a WebAssembly module header.
Input bytes discarded
The listing states that the submitted value is discarded after the check.
Single-purpose tool scope
It does one narrow validation job rather than a general WebAssembly toolkit.

Good for

  • Validate that a WebAssembly file header is well formed before passing it to a runtime
  • Add a quick format check to an agent pipeline that handles uploaded .wasm files
  • Give an AI assistant a lightweight way to confirm a module's magic and version bytes

WASM magic version, bytes discarded FAQ

Does it need to be installed locally?

The listing gives a hosted remote endpoint over streamable HTTP and lists no packages, so it is used by connecting to that endpoint.

Does it keep the bytes that are submitted?

The listing says the value is discarded, which is the stated intent of the check.

How do I add WASM magic version, bytes discarded to Claude Code?

Run this command in your terminal: claude mcp add --transport http wasm-ok https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/wasm-ok/mcp

What are the best alternatives to WASM magic version, bytes discarded?

The closest alternatives to WASM magic version, bytes discarded are WebP magic-byte check, file discarded, WebM EBML check, file discarded, XML well-formed check, body discarded, WAV RIFF check, file discarded and WSDL operation count, body discarded.

Where this comes from

  • Description: written from the project's README and its MCP Registry entry.
  • Install steps: from the official MCP Registry entry.

How AIPoweredBot checks servers