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/magna-nz/backstoryWrote 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/magna-nz/backstory/backstory)<a href="https://agentmods.dev/mcp/magna-nz/backstory/backstory"><img src="https://agentmods.dev/badge/mcp/magna-nz/backstory/backstory/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/magna-nz/backstory/backstory"><img src="https://agentmods.dev/badge/mcp/magna-nz/backstory/backstory.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
backstory 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 10d 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
{
"backstory": {
"command": "Backstory",
"args": [],
"env": {}
}
}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.
- 10d ago First seen · 7 lines scan A 727a16517c25
backstory is an MCP server published in the GitHub repository magna-nz/backstory (5 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
fuse
MCP server "fuse" as configured in Litenova-Solutions/Fuse. Launched with Fuse.
dotnet-template-mcp
MCP server "dotnet-template-mcp" as configured in YuliiaKovalova/dotnet-template-mcp. Launched with DotnetTemplateMCP -y.
projgraph
MCP server "projgraph" as configured in HandyS11/ProjGraph. Launched with ProjGraph.Mcp.
resharper-cli-mcp
MCP server "resharper-cli-mcp" as configured in andypgray/resharper-cli-mcp. Launched with Zphil.ReSharperCli. Needs 9 environment variables to run.
generator-agent
MCP server "generator-agent" as configured in Azure/azure-sdk-for-net. Launched with dotnet run --project sdk/tools/Azure.GeneratorAgent/src/Azure.GeneratorAgent.csp.
mcp-server
Unified MCP server for Ignite UI — documentation, API, and CLI scaffolding. Runs locally from the @igniteui/mcp-server npm package.