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.
npx agentmods add mcp/autonomad1/computeback-mcp/computebackgit clone --depth 1 https://github.com/Autonomad1/computeback-mcpWrote 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/autonomad1/computeback-mcp/computeback)<a href="https://agentmods.dev/mcp/autonomad1/computeback-mcp/computeback"><img src="https://agentmods.dev/badge/mcp/autonomad1/computeback-mcp/computeback.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
computeback 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 3d 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
{
"computeback": {
"command": "npx",
"args": [
"-y",
"@autonomad1/computeback-mcp"
],
"env": {
"COMPUTEBACK_API_URL": "https://www.computeback.com/api",
"BASE_RPC_URL": "https://mainnet.base.org",
"AGENT_DID": "",
"AGENT_HMAC_SECRET": ""
}
}
}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.
- 3d ago First seen · 15 lines scan A 99137f946a98
computeback is an MCP server published in the GitHub repository Autonomad1/computeback-mcp (0 stars, last pushed 3mo 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
sap-mcp
Solana-native MCP gateway for SAP, DeFi tools, SNS identity, and x402 payments. Runs locally from the @oobe-protocol-labs/sap-mcp-server npm package. Needs 2 environment variables to run.
nestegg-calculators
90+ pure finance calculators: loans, investing, bonds, options, tax. Stateless, stores nothing. Remote server at nestegg.money.
vertex-o
MCP server "vertex-o", hosted remotely at {company}.vertexinc.com, as configured in vivy-yi/finance-skills.
monarch-mcp
MCP server for Monarch Money personal finance. Runs locally from the monarch-mcp-jamiew Python package. Needs 4 environment variables to run.
wfirma-mcp
Unofficial read-only MCP server for the wFirma API v2: invoices, contractors, expenses, payments. Runs locally from the wfirma-mcp npm package. Needs 3 environment variables to run.
oddsrail
MCP server giving AI trading agents access to prediction markets (Polymarket, Kalshi) with on-chain builder-code attribution and trading signals. Runs locally from the oddsrail Python package. Needs 4 environment variables to run.