MCP.Market

Telleroutlook MCP server

by telleroutlook·io.github.telleroutlook/mcp-server·v1.1.1·5 stars

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

A86/100grade A
What users say
No reviews yet
Be the first
Safety scan
A86/100

full report

Adoption
Growing

5 stars199 downloads/wk

Reviews

Write one

Nobody has reviewed Telleroutlook yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Telleroutlook tools (2, 1 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • docs_search

    Look up the available downstream tools by name or substring.

  • execute_codewrite action

    Run a JavaScript snippet inside a sandboxed kernel.

Public scan report

scanner v0.1.9 · 2026-09-26 · same rubric, same numbers if you re-run it

no findings
  • Code scan19 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 9 days ago15/15
  • Maintainer identitynamespace and repository owner differ4/10
Overall 86/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Telleroutlook compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
86/100
higher than 72% of 48,255 servers
Tools
2
the typical server has 7
Tools that change things
50%
typical: 0%. Fewer write tools means less an agent can break
GitHub stars
5
more than 83% of 28,688 servers
Downloads a week
199
more than 75% of 12,191 servers with a package

What its tools let an agent do: 1 read · 1 run or deploy

Install Telleroutlook in Claude Code, Cursor or VS Code

Runs npx -y @wasmagent/mcp-server on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add mcp-server -- npx -y @wasmagent/mcp-server
Add to Cursor

What the publisher says

From the Telleroutlook repository's README, as published. We do not edit it. Read it on GitHub

wasmagent-js

WasmAgent adds a verifiable evidence layer to agent tool use: protect tool calls, record what happened, audit the result, and admit trusted traces into downstream systems.

Protect → Record → Audit → Admit · Sync — agent↔UI shared state

Start in 30 seconds

Pick your entry point:

Trust Pack — 30-minute end-to-end: docs/quickstarts/trust-pack-30min.md

Quickstart

Three paths — pick the one that fits your use case:

Path 1 — Protect: MCP runtime firewall

Wrap any MCP server: vet tools before execution, enforce policy per call, track taint across results.

npm install @wasmagent/mcp-firewall
import { evaluatePolicy, snapshotTool, taintObservation, vetTool } from "@wasmagent/mcp-firewall";

const entry = {
  name: "read_file",
  description: "Read a file from disk",
  inputSchema: { type: "object", properties: { path: { type: "string" } } },
};
const args = { path: "/tmp/report.txt" };
const consentRecords = [];

// Before calling a tool
const snap     = snapshotTool(entry, "my-server");   // hash descriptor at registration
const vetting  = vetTool(entry);                     // static scan: injection / exfil / rug-pull
const decision = evaluatePolicy(entry.name, args, vetting, consentRecords);

if (decision.decision === "deny")   throw new Error(`Blocked: ${decision.reasons.join("; ")}`);
if (decision.decision === "ask_user") {
  // surface consent UI, then call recordConsent(...)
}

// After receiving result
const rawResult = "example report contents";
const obs = taintObservation(entry.name, rawResult);  // boundary-tagged, safe to assemble into prompt

→ Security pack · OWASP Agentic Top 10 · Attack demos

Path 2 — Record: AEP evidence export

Emit a signed evidence record after every agent run — consumable by trace-pipeline for audit and training.

npm install @wasmagent/aep
import { AEPEmitter } from "@wasmagent/aep";

const emitter = new AEPEmitter({ run_id: "run-001", model_id: "claude-sonnet-4-6" });

// During the run — add tool call evidence
emitter.addAction({ tool_name: "bash", outcome: "pass", exit_code: 0 });

// At the end — emit the record
const record = emitter.build();
// record satisfies aep/v0.3 JSON Schema — ready for evomerge validate-aep

→ AEP schema · trace-pipeline 10-min tutorial

Path 3 — Execute: Sandboxed code execution

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Telleroutlook: common questions

Is Telleroutlook MCP server safe?
Yes, by our scan: it is graded A (86/100). Read the Telleroutlook safety report
How do I install Telleroutlook?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Telleroutlook need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Telleroutlook maintained?
The last commit was 48 days ago (2026-09-17). The latest release is v1.1.1.
How does Telleroutlook compare with other MCP servers?
safety score 86/100 (higher than 72% of 48,255 servers); tools 2 (the typical server has 7); tools that change things 50% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.