
Agent Tools
- Updated May 26, 2026
- WingedGuardian/agent-tools
Agent Tools is an MCP server that exposes nine utilities—DNS, WHOIS, email, IP, URL, headers, QR, text, and tech—with optional x402 on Base.
About
Agent Tools is a remote MCP server bundling nine utilities—DNS, WHOIS, email, IP, URL, headers, QR, text, and tech detection—for assistants that need quick network and content facts while integrating features or debugging deployments. It is exposed as streamable-http at tools.beethoven2024.com/mcp and advertises x402 on Base, which matters for developers experimenting with paid agent tool access without standing up their own microservices. Canonical shelf is build → integrations because you register the endpoint while composing agent workflows, though DNS and header checks also help during ship security reviews. Highlights enumerate all nine tool families per the registry description. Beginner-friendly setup if your MCP host supports remote servers; intermediate if you adopt x402 payment flows. Contrast with single-purpose WHOIS MCPs: this is a swiss-army remote bundle, not a deep CRM or memory layer.
- Nine agent utility tools: DNS, WHOIS, email, IP, URL, headers, QR, text, tech
- Hosted streamable-http MCP at tools.beethoven2024.com/mcp
- x402 payment rail on Base for metered agent tool access
- Covers email validation and HTTP header inspection use cases
- Remote-first; no required local API key in published server.json
Agent Tools by the numbers
- Data as of Jul 7, 2026 (Skillselion catalog sync)
claude mcp add --transport http agent-tools https://tools.beethoven2024.com/mcpAdd your badge
Show developers this MCP server is listed on Skillselion. Paste this into your README.
| Transport | HTTP |
|---|---|
| Auth | None |
| Last updated | May 26, 2026 |
| Repository | WingedGuardian/agent-tools ↗ |
What it does
Expose nine network and text utility tools—DNS, WHOIS, email, IP, URL, headers, QR, text, and tech detection—to your agent with optional x402 payments on Base.
Who is it for?
Agent developers who want a hosted utility bundle and may use x402 on Base instead of maintaining their own lookup APIs.
Skip if: Skip if you require only on-prem stdio tools, deep CRM integrations, or guaranteed free tier without x402 payment mechanics.
What you get
One remote MCP endpoint answers DNS, WHOIS, headers, and related utility calls so integration debugging stays in the agent.
- DNS, WHOIS, IP, and URL lookup results via MCP
- Email, header, QR, text, and tech detection outputs
- Single remote endpoint for nine documented utility categories
By the numbers
- Nine utility tool categories named in server description
- Remote MCP URL https://tools.beethoven2024.com/mcp (streamable-http)
- x402 payment support on Base noted in registry description
README.md
Agent Tools
Agent-native utility API bundle. 9 endpoints exposed as both REST API and MCP server (streamable-http), with x402 micropayments. Live at tools.beethoven2024.com.
For AI agents (Claude, Cursor, custom): Add this MCP server to your config and use 9 utility tools instantly.
For developers: Standard REST API. Use any subdomain example below as a working sample.
Try it now
As MCP server (Claude, Cursor, agents)
{
"mcpServers": {
"agent-tools": {
"url": "https://tools.beethoven2024.com/mcp"
}
}
}
As REST API
curl https://tools.beethoven2024.com/health
# {"status":"ok","version":"0.1.0"}
curl "https://tools.beethoven2024.com/v1/dns/health?domain=example.com"
# Full DNS + mail security audit (requires x402 payment)
What's in the bundle
| Tool | Endpoint | What it does | Price |
|---|---|---|---|
qr_generate |
/v1/qr/generate |
QR code generation (PNG/SVG, 64–2048px) | $0.001 |
dns_health |
/v1/dns/health |
DNS records + SPF/DMARC mail security audit | $0.003 |
email_validate |
/v1/email/validate |
Format, MX, disposable domain, role account, SMTP probe | $0.005 |
ip_lookup |
/v1/ip/lookup |
Geolocation, ISP, proxy/hosting detection, reverse DNS | $0.005 |
url_health |
/v1/url/health |
Status code, redirect chain, SSL cert, response time | $0.003 |
whois_lookup |
/v1/whois/lookup |
Registrar, creation/expiration dates, nameservers, status | $0.005 |
headers_analyze |
/v1/headers/analyze |
HTTP security headers audit with 0–100 score (HSTS, CSP, etc.) | $0.003 |
extract_text |
/v1/extract/text |
Clean text extraction from webpages (strips HTML, nav, ads) | $0.005 |
tech_detect |
/v1/tech/detect |
Website technology stack — frameworks, CMS, CDN, analytics | $0.005 |
Free: /health, /, /docs (OpenAPI), and MCP protocol methods initialize / tools/list / ping. All 9 tools require x402 payment via both MCP (tools/call) and REST (/v1/*).
Why these endpoints
Every endpoint solves a problem agents can't easily do locally:
- Network infrastructure (DNS, WHOIS, headers, URL health, IP) — needs internet probes, can't be done in-process
- Specialized parsing (QR, email validation with SMTP, tech detection) — domain-specific logic agents shouldn't reimplement
- Web extraction (text extraction) — clean text from messy HTML is hard
8 of 9 endpoints are fully self-hosted (zero upstream API cost). Only IP geolocation uses an external free-tier API.
Payment
x402 (machine-to-machine micropayments)
Every paid endpoint returns HTTP 402 Payment Required with the price spec when no payment is included. x402-capable agents handle this automatically:
- Agent calls endpoint → receives 402 with payment_requirements (network, amount, recipient address)
- Agent signs EIP-3009
transferWithAuthorizationfor USDC on Base - Agent retries with
X-PAYMENTheader - Service verifies payment via facilitator, executes, returns result
Settlement happens on-chain on Base. Sub-2-second confirmation.
Runs on Base mainnet by default. Set AGENT_TOOLS_TESTNET=true to use Base Sepolia with the public testnet facilitator.
Traditional billing
Coming soon: API key + Stripe usage billing for human developers and businesses.
Tech stack
- Python 3.12 + FastAPI
- MCP SDK (
mcpv1.27) — streamable-http transport - x402 SDK (
x402[fastapi,evm]>=v2.11) — USDC micropayments on Base - 8/9 endpoints self-hosted (no upstream API cost)
- Single-process deploy, ~62MB memory footprint
Self-host
Fly.io
git clone https://github.com/WingedGuardian/agent-tools.git
cd agent-tools
fly launch --copy-config
fly secrets set AGENT_TOOLS_PAY_TO=0xYourAddress AGENT_TOOLS_TESTNET=false
fly deploy
Docker
git clone https://github.com/WingedGuardian/agent-tools.git
cd agent-tools
cp .env.example .env
# Edit .env with your wallet address
docker compose up -d
Manual
pip install ".[all]"
AGENT_TOOLS_PAY_TO=0xYourAddress uvicorn agent_tools.app:app --host 0.0.0.0 --port 8000
Configuration
| Variable | Required | Default | Description |
|---|---|---|---|
AGENT_TOOLS_PAY_TO |
No | (empty) | EVM wallet address for receiving USDC payments. Leave empty to run free/dev mode. |
AGENT_TOOLS_TESTNET |
No | true |
true = Base Sepolia testnet (default — works with public x402.org facilitator). false = Base mainnet (requires mainnet-capable facilitator). |
Discovery / registries
- GitHub: https://github.com/WingedGuardian/agent-tools
- Smithery: (pending registration)
- Glama: (pending registration)
- x402-list: (pending registration)
- npm: (pending publish)
Keywords
x402, micropayments, USDC, Base, agent-native, MCP, Model Context Protocol, streamable-http, agentic, AI agent tools, DNS lookup API, WHOIS API, email validation API, QR code API, URL health API, web scraping API, tech detection API, security headers analyzer
License
MIT
Recommended MCP Servers
How it compares
Multi-tool remote MCP utility hub, not a single-domain WhoisJSON specialist or local CLI.
FAQ
Who is Agent Tools MCP for?
Developers and agent authors who need DNS, WHOIS, email, URL, and header utilities from one hosted MCP endpoint.
When should I use Agent Tools MCP?
Use it while wiring integrations, validating infrastructure, or researching sites when you want nine utilities without custom scripts.
How do I add Agent Tools to my agent?
Register the streamable-http remote https://tools.beethoven2024.com/mcp in your MCP client and follow x402-on-Base payment docs if your host requires it.