Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, email [email protected] and we’ll put it right.

io.github.telleroutlook/mcp-server

NPM · @WASMAGENT/MCP-SERVER · SCANNED AUG 3

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

Available components

npm · @wasmagent/mcp-server 70
−10 this week 70 Trust /100
Trust breakdown (6 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score →

Supply Chain Security95
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 2 of 4 dependencies flagged as unhealthy (2 deprecated). View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability71
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 187 tokens (~93/item across 2 items; 2 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
  • Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

npm · @wasmagent/mcp-server

# add to Claude Code
claude mcp add telleroutlook-mcp-server -- npx -y @wasmagent/mcp-server
# add to Codex CLI
codex mcp add telleroutlook-mcp-server -- npx -y @wasmagent/mcp-server
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "telleroutlook-mcp-server": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@wasmagent/mcp-server"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add telleroutlook-mcp-server --command npx --arg -y --arg @wasmagent/mcp-server
# ~/.hermes/config.yaml
mcp_servers:
  telleroutlook-mcp-server:
    command: "npx"
    args: ["-y", "@wasmagent/mcp-server"]
// mcp.json
{
  "mcpServers": {
    "telleroutlook-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@wasmagent/mcp-server"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 2 Aug 26 +17
    • Malware scan: unverified → pass ▲ security
    • Dependency health: 1.00 → 0.60 ▼ functional
    • Stability: unverified → 0.20 ▲ functional
  • 31 Jul 26 −9
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 −18
    • Malware scan: pass → unverified ▼ security
  • 27 Jul 26 +33
    • Tool coverage: unverified → 100 ▲ functional
    • First check of Schema quality: fail functional
    • First check of Tool coverage: 100 functional
    • First check of Schema quality: good functional
    • First check of Schema quality: pass functional
  • 26 Jul 26 47

    First indexed and scored.

    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 3 Aug 2026 · Analysed npm/@wasmagent/[email protected]

Provenance none

Ecosystem: npm · Outcome: none

Dependencies 4 packages

4 packages in the resolved dependency tree · 2 deprecated.

MCP tools — 2 exposed · ~187 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.

Tool Tokens
docs_search ~75

Look up the available downstream tools by name or substring. Call this BEFORE writing an execute_code script to learn what's available.

NameTypeReqDescription
namesarray—Optional list of exact tool names to fetch. Takes precedence over `query`.
querystring—Substring to filter tool names/descriptions. Empty/omitted returns all.

No output schema declared.

No examples provided.

execute_code ~112

Run a JavaScript snippet inside a sandboxed kernel. The snippet may call `callTool(name, args)` to invoke any downstream tool. Only the snippet's final return value (or the value assigned to `__finalAnswer__`) is returned to you — intermediate tool outputs stay in the sandbox. Use this to chain many tool calls in one round.

NameTypeReqDescription
codestringyesJavaScript source. May use top-level `await`. Must end with a return value or set `__finalAnswer__ = ...`.

No output schema declared.

No examples provided.