Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add tsouth89/toolport/plugin install toolportWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/tsouth89/toolport/toolport-toolport)<a href="https://agentmods.dev/mcp/tsouth89/toolport/toolport-toolport"><img src="https://agentmods.dev/badge/mcp/tsouth89/toolport/toolport-toolport/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/tsouth89/toolport/toolport-toolport"><img src="https://agentmods.dev/badge/mcp/tsouth89/toolport/toolport-toolport.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
toolport scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 11d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"toolport": {
"command": "node",
"args": [
"${CLAUDE_PLUGIN_ROOT}/bin/launch-gateway.mjs"
]
}
}What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 11d ago First seen · 8 lines scan A ba4a540d2e56
toolport is an MCP server published in the GitHub repository tsouth89/toolport (202 stars, last pushed 7d ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other mcp servers, from other repositories
nauro
Human Controlled Project Truth: Keep your project's direction in human hands as agents do more of the work. Runs locally from the nauro Python package.
toolradar
MCP server for Toolradar — search, compare, and get pricing for 8,600+ software tools. Works with Claude Desktop, Claude Code, Cursor, and any MCP-compatible AI assistant. Runs locally from the toolradar-mcp npm package. Needs 1 environment variable to run.
project-memory-mcp
Persistent memory for AI coding agents — past bugs, decisions, and your corrections, in your repo. Runs locally from the @kaaustubh/project-memory-mcp npm package. Needs 1 environment variable to run.
contextprism
High-performance AST codebase context distiller and token optimizer for AI coding agents. Runs locally from the contextprism npm package.
aionai
A neutral, persistent working-state broker that keeps your AI coding tools (Claude, Cursor, …) on the same page — over MCP. Runs locally from the aionai Python package.
mavryn
The MCP control plane — one server to route them all. Runs locally from the mavryn npm package.