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/strale-io/straleWrote 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/strale-io/strale/mcp-server-strale)<a href="https://agentmods.dev/mcp/strale-io/strale/mcp-server-strale"><img src="https://agentmods.dev/badge/mcp/strale-io/strale/mcp-server-strale/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/strale-io/strale/mcp-server-strale"><img src="https://agentmods.dev/badge/mcp/strale-io/strale/mcp-server-strale.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
strale 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
{
"strale": {
"command": "npx",
"args": [
"-y",
"strale-mcp"
],
"env": {
"STRALE_API_KEY": ""
}
}
}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 · 12 lines scan A 728e65adfbfb
strale is an MCP server published in the GitHub repository strale-io/strale (5 stars, last pushed 3d 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
django-admin-mcp
Django admin MCP integration - expose Django admin models to MCP clients. Runs locally from the django-admin-mcp Python package. Needs 1 environment variable to run.
developers-mcp
Access Mastercard Developers APIs, documentation, and API specifications through MCP. Runs locally from the @mastercard/developers-mcp npm package.
stitchapi-docs
StitchAPI documentation search, running locally over MCP stdio. Bundled docs, no network calls per query — the offline/air-gapped counterpart to the hosted stitchapi.dev/api/mcp server. Runs locally from the @stitchapi/docs-mcp npm package.
bankapi-v1-azurecontainerapps
MCP server "bankapi-v1-azurecontainerapps", hosted remotely at app.bravestone-75bd2261.germanywestcentral.azurecontainerapps.io, as configured in erwinkramer/bank-api.
bankapi-v1-local
MCP server "bankapi-v1-local", hosted remotely at localhost, as configured in erwinkramer/bank-api.
mcp-server
350+ production-ready APIs through one MCP server — weather, geocoding, validation, financial data. Remote server at api.apiverve.com.