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)<a href="https://agentmods.dev/mcp/spawnpoint-inc/spawnpoint-plugin/spawnpoint"><img src="https://agentmods.dev/badge/mcp/spawnpoint-inc/spawnpoint-plugin/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"><img src="https://agentmods.dev/badge/mcp/spawnpoint-inc/spawnpoint-plugin/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 1mo 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": { "url": "https://app.getspawnpoint.com/mcp", "type": "streamable-http" } }
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.
- 1mo ago First seen · 6 lines scan A 3875fb5acdda
spawnpoint is an MCP server published in the GitHub repository spawnpoint-inc/spawnpoint-plugin (0 stars, last pushed today), 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-31.
Other mcp servers, from other repositories
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.
my-mcp-server-remote
MCP server "my-mcp-server-remote", hosted remotely at my-mcp-server.your-account.workers.dev, as configured in secondsky/claude-skills.
dokploy-mcp
Dokploy MCP server for Codex, Cursor, and Claude with compact stdio and hosted HTTP modes. Runs locally from the @vibetools/dokploy-mcp npm package. Needs 3 environment variables to run.
sec
AWS Well-Architected Security Assessment Tool MCP Server. Runs locally from the awslabs.well-architected-security-mcp-server Python package.
dokploy-mcp
MCP server for Dokploy — dynamically generates 420+ tools from OpenAPI spec with correct x-api-key auth. Runs locally from the @sattva/dokploy-mcp npm package.
iac
An Infrastructure as Code MCP server that provides CloudFormation template validation, compliance checking, and deployment troubleshooting capabilities. Runs locally from the awslabs.aws-iac-mcp-server Python package.