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/maxfain/basedagentsWrote 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/maxfain/basedagents/mcp-basedagents)<a href="https://agentmods.dev/mcp/maxfain/basedagents/mcp-basedagents"><img src="https://agentmods.dev/badge/mcp/maxfain/basedagents/mcp-basedagents/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/maxfain/basedagents/mcp-basedagents"><img src="https://agentmods.dev/badge/mcp/maxfain/basedagents/mcp-basedagents.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
basedagents 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
{
"basedagents": {
"command": "npx",
"args": [
"-y",
"@basedagents/mcp"
],
"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.
- 1mo ago First seen · 10 lines scan A 79012180945e
basedagents is an MCP server published in the GitHub repository maxfain/basedagents (2 stars, last pushed yesterday), 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
agoragentic
Triptych OS (Agent OS) MCP for governed routing, receipts, and USDC settlement on Base. Runs locally from the agoragentic-mcp npm package. Needs 3 environment variables to run.
t2000
MCP server "t2000", hosted remotely at mcp.t2000.ai, as configured in mission69b/t2000.
tab
Every tool a builder signs up for, on one tab: trials, burn, price drift. Local JSONL, zero deps. Runs locally from the scvd-tab npm package.
general-store
Evidence observatory for agentic commerce: x402 preflight, receipt checks, settlement attestations. Remote server at scvd.store.
scvd-store
MCP server "scvd-store", hosted remotely at scvd.store, as configured in seancrecord/scvd-general-store-repo.
samedaydesk
MCP server "samedaydesk", hosted remotely at agents.samedaydesk.com, as configured in epistemedeus/x402-url-extractor.