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.
npx agentmods add mcp/waream2/stateless-mcp-starter/create-stateless-mcpgit clone --depth 1 https://github.com/waream2/stateless-mcp-starterWrote 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/waream2/stateless-mcp-starter/create-stateless-mcp)<a href="https://agentmods.dev/mcp/waream2/stateless-mcp-starter/create-stateless-mcp"><img src="https://agentmods.dev/badge/mcp/waream2/stateless-mcp-starter/create-stateless-mcp.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
create-stateless-mcp 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 4d 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
{ "create-stateless-mcp": { "command": "npx", "args": [ "-y", "create-stateless-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.
- 4d ago First seen · 9 lines scan A e15e3e39e0eb
create-stateless-mcp is an MCP server published in the GitHub repository waream2/stateless-mcp-starter (0 stars, last pushed 2mo 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-31.
Other mcp servers, from other repositories
mcp-pii-shield
MCP server "mcp-pii-shield" as configured in thegeekybeng/mcp-pii-shield. Runs locally from the @thegeekybeng/mcp-pii-shield npm package.
workbench-mcp
Remote-access MCP server: lets a Claude CLI on another machine read/write files, search code, run allow-listed commands and git over HTTP for a project. Runs locally from the workbench-mcp npm package.
strata
MCP server "strata" as configured in stratalib/strata. Runs C:\Users\user\Desktop\ALL PROJECTS\Recall V2\dist\src\mcp-server.js with node. Needs 1 environment variable to run.
example-mcp-sse
MCP server "example-mcp-sse" as configured in yigitkonur/example-mcp-sse. Runs locally from the example-mcp-sse npm package.
hypermnesia-mcp
Scientifically-grounded memory system based on computational neuroscience research. Runs locally from the hypermnesia-mcp Python package.
godot-mcp
MCP server for full Godot 4.x engine control with 165 tools for AI-driven game development. Runs locally from the @tugcantopaloglu/godot-mcp npm package.