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/philpof102-svg/mainstreetWrote 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/philpof102-svg/mainstreet/mainstreet)<a href="https://agentmods.dev/mcp/philpof102-svg/mainstreet/mainstreet"><img src="https://agentmods.dev/badge/mcp/philpof102-svg/mainstreet/mainstreet/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/philpof102-svg/mainstreet/mainstreet"><img src="https://agentmods.dev/badge/mcp/philpof102-svg/mainstreet/mainstreet.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
mainstreet 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
{
"mainstreet": {
"url": "https://avisradar-production.up.railway.app/mcp",
"type": "streamable-http"
}
}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 a8dbfb60f4da
mainstreet is an MCP server published in the GitHub repository philpof102-svg/mainstreet (2 stars, last pushed 12d 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
x402-seller
Rug-check & launch radar for trading agents: composite honeypot score, EVM+Solana, keyless x402. Remote server at x402-seller-m8nx.onrender.com.
crypto-prices
Live USD crypto spot prices by ticker (BTC, ETH, SOL, …) for AI agents. x402 pay-per-call. Remote server at api.agishub.com.
agentservices
52 paid x402 API endpoints for AI agents — crypto, data, DeFi, market intelligence. Remote server at agentservices.to.
aegis-protocol
Trustless escrow for AI agent-to-agent transactions on Base L2 with ERC-8004 identity and USDC. Runs locally from the @aegis-protocol/mcp-server npm package. Needs 4 environment variables to run.
whale-data-mcp
Signed settled outcomes (Polymarket, sports, Kalshi) + whale signals as agent tools, paid via x402. Runs locally from the @predge/whale-data-mcp npm package. Needs 7 environment variables to run.
fiatdock
Cash out an AI agent's USDC to a real bank account (non-custodial, licensed provider) — plus first-party Base chain data, token safety, and a marketplace where agents pay each other per call in USDC via x402, auto-paid from your wallet. Runs locally from the fiatdock-mcp npm package. Needs 3 environment variables to…