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/RipperMercs/tensorfeed-x402-base-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/rippermercs/tensorfeed-x402-base-mcp/x402-base-mcp)<a href="https://agentmods.dev/mcp/rippermercs/tensorfeed-x402-base-mcp/x402-base-mcp"><img src="https://agentmods.dev/badge/mcp/rippermercs/tensorfeed-x402-base-mcp/x402-base-mcp/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/rippermercs/tensorfeed-x402-base-mcp/x402-base-mcp"><img src="https://agentmods.dev/badge/mcp/rippermercs/tensorfeed-x402-base-mcp/x402-base-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
x402-base-mcp 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
{
"x402-base-mcp": {
"command": "npx",
"args": [
"-y",
"@tensorfeed/x402-base-mcp"
],
"env": {
"TENSORFEED_RPC_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.
- 1mo ago First seen · 12 lines scan A 5c0a139f2efd
x402-base-mcp is an MCP server published in the GitHub repository RipperMercs/tensorfeed-x402-base-mcp (2 stars, last pushed 14d 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
evmole
Local structured analysis of deployed EVM runtime bytecode. Runs locally from the evmole-mcp npm package.
evm-mcp-server
MCP server for interacting with EVM-compatible blockchains - supports 22 tools and 10 prompts across 60+ networks. Runs locally from the @mcpdotdirect/evm-mcp-server npm package.
evm-mcp-http
MCP server for interacting with EVM-compatible blockchains - supports 22 tools and 10 prompts across 60+ networks. Runs locally from the @mcpdotdirect/evm-mcp-server npm package.
warden402-mcp
Pre-execution safety for AI agents on Base. Guard a token, tx or address: block/review/clear. Runs locally from the warden402-mcp npm package. Needs 1 environment variable to run.
x402-mcp-bridge
Put a wallet in front of any x402-paid MCP server: pay per call, or buy time and ride a ZEAM :: Pass line. Stock MCP clients cannot construct x402 payments; this one does, and proxies your existing client through it. Runs locally from the @zeam-labs/x402-mcp-bridge npm package.
stipend
Non-custodial USDC wallet on Base with spending limits enforced in code, not in a prompt. Runs locally from the stipend npm package.