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/lucasastorian/edgarmcpWrote 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/lucasastorian/edgarmcp/mcp-sec-edgar)<a href="https://agentmods.dev/mcp/lucasastorian/edgarmcp/mcp-sec-edgar"><img src="https://agentmods.dev/badge/mcp/lucasastorian/edgarmcp/mcp-sec-edgar/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/lucasastorian/edgarmcp/mcp-sec-edgar"><img src="https://agentmods.dev/badge/mcp/lucasastorian/edgarmcp/mcp-sec-edgar.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
mcp-sec-edgar 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
{ "mcp-sec-edgar": { "command": "uvx", "args": [ "mcp-sec-edgar" ] } }
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 · 8 lines scan A f003055a83ba
mcp-sec-edgar is an MCP server published in the GitHub repository lucasastorian/edgarmcp (0 stars, last pushed 2mo ago), licensed Apache-2.0. 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
robokassa
MCP server for Robokassa payment API — generate payment URLs, check invoice status. 2 tools. MD5 signature auth. Runs locally from the @theyahia/robokassa-mcp npm package. Needs 4 environment variables to run.
robokassa-mcp
MCP server for Robokassa payment API — generate payment URLs, check invoice status. First MCP for R. Runs locally from the @theyahia/robokassa-mcp npm package. Needs 1 environment variable to run.
sber-mcp
MCP server for Sberbank API — accounts, statements. Bearer token auth. Runs locally from the @theyahia/sber-mcp npm package. Needs 1 environment variable to run.
netsuite-mcp-workbuddy
MCP server "netsuite-mcp-workbuddy" as configured in Bolton-Z/ns-mcp-china. Launched with netsuite-mcp-workbuddy.
tegro-money
MCP server for Tegro.Money — connect Claude, Cursor and other AI tools to the Tegro.Money payment API (balances, shops, orders, payouts, rates). Read-only, secure, your API key never leaves your machine. Runs locally from the @tegroton/tegro-money-mcp npm package. Needs 2 environment variables to run.
catalyst-edge-mcp
Audited SEC catalyst signals for agents — ranked filing intel with a public track record. Free tier. Remote server at catalystedgescanner.com.