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/vbkotecha/agentservices-apiWrote 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/vbkotecha/agentservices-api/agentservices)<a href="https://agentmods.dev/mcp/vbkotecha/agentservices-api/agentservices"><img src="https://agentmods.dev/badge/mcp/vbkotecha/agentservices-api/agentservices/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/vbkotecha/agentservices-api/agentservices"><img src="https://agentmods.dev/badge/mcp/vbkotecha/agentservices-api/agentservices.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
agentservices 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
{
"agentservices": {
"url": "https://agentservices.to/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.
- 1mo ago First seen · 6 lines scan A 704cef75893c
agentservices is an MCP server published in the GitHub repository vbkotecha/agentservices-api (2 stars, last pushed 16d 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
x402-seller
Rug-check & launch radar for trading agents: composite honeypot score, EVM+Solana, keyless x402. Remote server at x402-seller-m8nx.onrender.com.
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.
x402-data-gateway
Twelve x402 tools for data, audits, Morpho decisions, and opportunity preflight on Base. Remote server at agents.samedaydesk.com.
cinderwright-api
Cross-protocol agent payments hub. x402, MPP, L402/Lightning. 1551 services indexed. Runs locally from the cinderwright-mcp-server npm package.
mainstreet
Reputation oracle for AI agents on Base: SAFE/CAUTION/BLOCK + 0-100 score before you pay. x402+MCP. Remote server at avisradar-production.up.railway.app.
tryx402
The OpenRouter for agent payments: budget router, idempotency, cost ledger, and multi-currency billing over x402. Runs locally from the tryx402 Python package. Needs 2 environment variables to run.