mcp-pordego: Jarvis Nelson Osorio's security scanner for MCP servers

By Jarvis Nelson Osorio · November 16, 2026

The Model Context Protocol made it easy to give agents tools. It also made it easy to give them too much. As Jarvis Nelson Osorio puts it in the project's README, today every MCP setup is "give the agent the whole server and hope." There is no check that a tool description did not smuggle instructions, no alarm when npx floats on @latest, and nothing stopping a personal access token from sitting in plaintext in mcp.json.

mcp-pordego is his open-source response. The name comes from Esperanto: pordego means gate. It is a security scanner for the MCP servers your agents already use.

Black-and-white portrait of Jarvis Nelson Osorio (Jarvis Osorio) wearing a dark scarf
Jarvis Nelson Osorio (Jarvis Osorio), black-and-white portrait with a scarf.

What it scans mcp-pordego audits MCP configurations in Claude Desktop, Claude Code, Cursor and VS Code. Running pnpm scan auto-discovers configs from the usual places — claude_desktop_config.json, .mcp.json and ~/.claude.json, .cursor/mcp.json, and .vscode/mcp.json — or you can point it at a specific file with --config.

It is written in TypeScript, requires Node.js 20+ and pnpm, and is released under the Apache License 2.0. The current version is 0.1.1.

Static rules (config only) - unpinned-npx (high): an npx package without an exact version, or pinned to @latest - unpinned-uvx (high): uvx or pipx run without ==version - unpinned-docker (high): an image tagged :latest, or with no tag or digest - unpinned-git (high): a git URL without a commit SHA - inline-secret (high): a secret-looking value in env, args or headers - remote-http-no-tls (high): plain http:// to a non-loopback host - broad-fs-root (medium): a filesystem server rooted at /, ~ or home - shell-server (medium): a name or package that suggests shell or exec capability

Live mode With --live, the scanner spawns each stdio server and calls only initialize and tools/list — never tools/call. That lets it inspect tool descriptions and schemas without executing anything. High-severity live rules include injection phrases, hidden characters, exfiltration URLs and freeform-exec schemas. Medium and low rules cover hidden markup, cross-tool references, freeform path or URL schemas, tool-name collisions, missing read-only hints and oversized descriptions.

Detection is heuristic, and the README says so. Rules are plain TypeScript modules, which makes them easy to read and extend.

Jarvis Osorio (Jarvis Nelson Osorio) in sunglasses and a teal polo under terrace umbrellas
Jarvis Osorio (Jarvis Nelson Osorio) relaxing on a terrace.

Built for CI The scanner exits 1 on high-severity findings and 2 on config or integrity errors, so it drops straight into a pipeline: fail the build when someone adds an unpinned server or pastes a token into a config.

Install The package is not on npm yet, so do not run npx mcp-pordego. Instead:

git clone https://github.com/JarvisOsorio/mcp-pordego.git
cd mcp-pordego
pnpm install && pnpm build
pnpm scan

Or download the v0.1.1 release asset, mcp-pordego.cjs, from the GitHub releases page and run node mcp-pordego.cjs scan.

What is next v0.1 ships the scanner. A policy gateway, lockfile, redaction proxy, audit log and replay are designed in SPEC.md, and the CLI already stubs those commands so the surface stays stable — but they are not part of this release. Jarvis Nelson Osorio is explicit about that line between shipped and planned.

Jarvis Osorio (Jarvis Nelson Osorio) in sunglasses and a dark jacket with a palm tree behind
Jarvis Osorio (Jarvis Nelson Osorio) in sunglasses under a palm tree.

If you run agents with MCP servers, a two-minute scan is cheap insurance. Read the project page on jarvisosorio.com and the source on GitHub.

Links