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/rhein1/agoragentic-integrationsWrote 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/rhein1/agoragentic-integrations/agoragentic)<a href="https://agentmods.dev/mcp/rhein1/agoragentic-integrations/agoragentic"><img src="https://agentmods.dev/badge/mcp/rhein1/agoragentic-integrations/agoragentic.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
agoragentic 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 8d 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
{
"agoragentic": {
"command": "npx",
"args": [
"-y",
"agoragentic-mcp"
],
"env": {
"AGORAGENTIC_API_KEY": "",
"AGORAGENTIC_MCP_URL": "",
"AGORAGENTIC_BASE_URL": ""
}
}
}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.
- 8d ago First seen · 14 lines scan A 6e019e7e4425
agoragentic is an MCP server published in the GitHub repository rhein1/agoragentic-integrations (36 stars, last pushed 2d 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-30.
Other mcp servers, from other repositories
x402-data-gateway
Twelve x402 tools for data, audits, Morpho decisions, and opportunity preflight on Base. Remote server at agents.samedaydesk.com.
xfuel-mcp
Submit AI inference to XFuel, pay per task (USDC via x402 or TFUEL), fetch/verify ZK proofs. Runs locally from the xfuel-mcp npm package. Needs 6 environment variables to run.
verification
Twelve tools: token, wallet, contract and site security. Two free, the rest $1 in USDC over x402. Remote server at centry.cybercentry.co.uk.
hive-mcp-vault
A2A ZK wallet recovery — guardian swarm, no seed phrase, HiveLaw enforcement. Remote server at hive-mcp-vault.onrender.com.
xenarch-mcp
Xenarch — x402 MCP server for AI agent payments. Non-custodial, USDC on Base L2. Runs locally from the @xenarch/agent-mcp npm package. Needs 4 environment variables to run.
vedetta
MCP server for Vedetta — pay-per-call crypto sentiment, divergence verdicts, and live analyst reads over x402 (USDC on Base). Descriptive market analysis only — not financial advice. Runs locally from the vedetta-mcp npm package. Needs 3 environment variables to run.