Skip to main content
Glama
521,841 tools. Updated 2026-09-06 12:28

"WebAssembly" matching MCP tools:

  • Search WebAssembly instructions by free-text query against mnemonic, category, or opcode hex. Get ranked results to find the correct instruction when the exact name is unknown.
    MIT
  • Enumerate WebAssembly instructions with optional filters for category, version, prefix, or trapping behavior. Returns sorted rows with basic info for further detail.
    MIT
  • Retrieve structured JSON for a WebAssembly instruction by mnemonic or binary opcode, including opcode bytes, category, stack signature, and trap conditions.
    MIT
  • Enumerate WebAssembly spec clauses for navigation across core, js-api, and web-api specs. Filter by path, anchor prefix, depth, and titled-only.
    MIT

Matching MCP Servers

  • Look up a WebAssembly type or type form by name to retrieve its classification, sibling members, defining prose, formal references, and spec URL.
    MIT
  • Retrieve a WebAssembly spec clause by its id or anchor from core, js-api, or web-api. Get the clause title, cleaned prose, cross-references, formal references, and rendered URL.
    MIT
  • List WebAssembly proposals from the proposals repository. Filter by status, phase, champion, or affected specification.
    MIT
  • Run Python code securely in a WebAssembly sandbox to execute scripts and return output. Supports pure Python without external dependencies.
    Apache 2.0
  • Search across WebAssembly spec sections (core, JS API, Web API) by clause anchors, titles, or prose. Returns ranked hits with matched type and snippet for body matches, to locate sections before retrieving details.
    MIT
  • Execute JavaScript code in a secure WebAssembly sandbox to run untrusted code safely and return console logs with evaluated expressions.
    Apache 2.0
  • Runs WebAssembly binaries (.wasm) using Wasmtime; if Wasmtime is unavailable, indicates the capability.
    MIT
  • Simulate a Xahau Hook by running its real WebAssembly bytecode in a local VM against a mock transaction and ledger state, reporting the accept or reject decision, state writes, and emitted transactions.
    MIT
  • Run WebAssembly modules in memory via exported function calls. Pass Base64-encoded WASM binary and function name with optional numerical arguments to execute.
    MIT
  • Execute WebAssembly modules in a secure sandbox with controlled access to filesystem, network, and crypto via host adapters. Supports execution limits and deterministic replay.
    MIT
  • Re-execute WebAssembly modules with recorded replay tokens to reproduce runtime behavior deterministically. Replays non-deterministic host responses for debugging and verification against known execution traces.
    MIT
  • Inspect WebAssembly modules by analyzing sections, imports, exports, names, and producers with a local dependency-free structural parser.
    MIT