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/streamlined-analytics/django-stateless-mcp/django-stateless-mcp-examplegit clone --depth 1 https://github.com/Streamlined-Analytics/django-stateless-mcpWrote 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/streamlined-analytics/django-stateless-mcp/django-stateless-mcp-example)<a href="https://agentmods.dev/mcp/streamlined-analytics/django-stateless-mcp/django-stateless-mcp-example"><img src="https://agentmods.dev/badge/mcp/streamlined-analytics/django-stateless-mcp/django-stateless-mcp-example.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
django-stateless-mcp-example 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 5d 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
{
"django-stateless-mcp-example": {
"type": "http",
"url": "http://127.0.0.1:8000/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.
- 5d ago First seen · 6 lines scan A 016f426b28e7
django-stateless-mcp-example is an MCP server published in the GitHub repository Streamlined-Analytics/django-stateless-mcp (1 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
unraid
Rust MCP server and CLI for Unraid GraphQL operations across NAS, Docker, VM, and storage workflows. Runs locally from the @dinglebear/unraid npm package. Needs 6 environment variables to run.
unraid-mcp
MCP Server for Unraid API - provides tools to interact with an Unraid server's GraphQL API. Runs locally from the unraid-mcp Python package. Needs 3 environment variables to run.
unraid-mcp
MCP Server for Unraid API - provides tools to interact with an Unraid server's GraphQL API. Runs locally from the unraid-mcp Python package. Needs 2 environment variables to run.
swiss-academic-libraries-mcp
MCP Server für Schweizer Wissenschaftsbibliotheken: swisscovery (SRU), e-rara/e-periodica/e-manuscripta (OAI-PMH) und Open-Access-Rechtsliteratur (sui generis, ex/ante, Repositorium.ch). Kein API-Key erforderlich. Runs locally from the swiss-academic-libraries-mcp Python package.
swiss-housing-mcp
MCP server for the Swiss Federal Register of Buildings and Dwellings (GWR/RegBL) — buildings, dwellings, construction pipeline. Runs locally from the swiss-housing-mcp Python package.
termdat-mcp
MCP server for TERMDAT — the terminology database of the Swiss Federal Administration. Runs locally from the termdat-mcp Python package.