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/Un3x/ai-success-storyWrote 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/un3x/ai-success-story/aiss-consult-ai-success-story)<a href="https://agentmods.dev/mcp/un3x/ai-success-story/aiss-consult-ai-success-story"><img src="https://agentmods.dev/badge/mcp/un3x/ai-success-story/aiss-consult-ai-success-story/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/un3x/ai-success-story/aiss-consult-ai-success-story"><img src="https://agentmods.dev/badge/mcp/un3x/ai-success-story/aiss-consult-ai-success-story.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
ai-success-story 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 11d 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
{
"ai-success-story": {
"type": "http",
"url": "https://ai-success-story-20f19ed7769b.herokuapp.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.
- 11d ago First seen · 6 lines scan A 4dc534c90d38
ai-success-story is an MCP server published in the GitHub repository Un3x/ai-success-story (0 stars, last pushed 3mo 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
workrail-dev
MCP server "workrail-dev", hosted remotely at localhost, as configured in EtienneBBeaulac/workrail.
sui-mcp
Read-only Sui blockchain analytics: 59 tools, protocol-aware tx decoding, no API keys or wallet. Runs locally from the sui-analytics-mcp npm package. Needs 6 environment variables to run.
opm-mcp
MCP server "opm-mcp" as configured in ojaogezi/opm-mcp. Launched with opm-mcp.
reportflow-mcp
Generate PDF reports from Re:port Flow templates via Claude and other AI agents. Runs locally from the reportflow-mcp npm package. Needs 4 environment variables to run.
model-council
An MCP server that lets your assistant consult other LLMs — ask them, compare their answers, and synthesize a conclusion. Runs locally from the model-council-mcp Python package. Needs 9 environment variables to run.
netmon
MCP server "netmon" as configured in Netmon-Services/netmon-mcpd. Launched with https://github.com/Netmon-Services/netmon-mcpd/releases/download/v0.1.9/netmon-m.