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/BotHireAgent/BotHireMCPServerWrote 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/bothireagent/bothiremcpserver/bothire)<a href="https://agentmods.dev/mcp/bothireagent/bothiremcpserver/bothire"><img src="https://agentmods.dev/badge/mcp/bothireagent/bothiremcpserver/bothire/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/bothireagent/bothiremcpserver/bothire"><img src="https://agentmods.dev/badge/mcp/bothireagent/bothiremcpserver/bothire.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
bothire 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
{
"bothire": {
"command": "npx",
"args": [
"-y",
"bothire-mcp"
],
"env": {}
}
}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 · 10 lines scan A 6c198cd3fc1a
bothire is an MCP server published in the GitHub repository BotHireAgent/BotHireMCPServer (0 stars, last pushed 1mo 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-base-mcp
Read-only Base mainnet reader. Verifies x402 payment settlements + AFTA federation status. Runs locally from the @tensorfeed/x402-base-mcp npm package. Needs 1 environment variable to run.
stipend
Non-custodial USDC wallet on Base with spending limits enforced in code, not in a prompt. Runs locally from the stipend npm package.
onyx-mcp
Ed25519-signed ground-truth oracle — 63 paid x402 tools live on Base mainnet. Remote server at onyx-actions.onrender.com.
haiku-mcp-server
DeFi execution for AI agents — swap, lend, bridge, and yield across 22 chains. Runs locally from the haiku-mcp-server npm package. Needs 2 environment variables to run.
haiku
MCP server for Haiku API - enables AI agents to execute any blockchain transactions. Runs locally from the haiku-mcp-server npm package. Needs 1 environment variable to run.
x402-tools-mcp
22 x402 pay-per-call utility tools for AI agents — scrape, validate, embed, store, moderate, notify, convert, prevent loops. No accounts, no API keys. USDC on Base via the x402 protocol. Runs locally from the @melis-ai/x402-tools-mcp npm package. Needs 2 environment variables to run.