Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/spawnpoint-inc/spawnpoint-pluginWrote 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/spawnpoint-inc/spawnpoint-plugin/spawnpoint-spawnpoint)<a href="https://agentmods.dev/mcp/spawnpoint-inc/spawnpoint-plugin/spawnpoint-spawnpoint"><img src="https://agentmods.dev/badge/mcp/spawnpoint-inc/spawnpoint-plugin/spawnpoint-spawnpoint/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/spawnpoint-inc/spawnpoint-plugin/spawnpoint-spawnpoint"><img src="https://agentmods.dev/badge/mcp/spawnpoint-inc/spawnpoint-plugin/spawnpoint-spawnpoint.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
spawnpoint 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 2d 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
{
"spawnpoint": {
"type": "http",
"url": "https://app.getspawnpoint.com/mcp"
}
}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.
- 2d ago First seen · 6 lines scan A caba8e5268a8
spawnpoint is an MCP server published in the GitHub repository spawnpoint-inc/spawnpoint-plugin (0 stars, last pushed yesterday), 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-10-17.
Other mcp servers, from other repositories
plyo-mcp
Save, publish, restore and back up AI-built projects on Plyo, for people who build with AI. Runs locally from the plyo-mcp npm package. Needs 1 environment variable to run.
layero
MCP server "layero", hosted remotely at mcp.layero.ru, as configured in LayeroInfra/layero-claude.
openpouch
openpouch 🦘 MCP server — agent-native deploy tools for any MCP-capable harness (Claude Code, Codex, Cursor, Windsurf, …). stdio, open standard. No approve tool — production approval stays human-only. Runs locally from the @openpouch/mcp npm package.
openpouch
Agent-native hosting: deploy any folder to a live URL in one command. No approve tool. Runs locally from the @openpouch/mcp npm package.
docs-langchain
MCP server "docs-langchain", hosted remotely at docs.langchain.com, as configured in langchain-ai/langchain.
component-explorer
MCP server "component-explorer" as configured in microsoft/vscode. Launched with npm exec --no -- component-explorer mcp -p ./test/componentFixtures/component-ex.