About Agent Tools
Agent Tools is a utility API bundle for AI agents, also available as a REST API. It covers network lookups, email checks, and web extraction, with per-call x402 micropayments.
Key features
- 01DNS and mail security audits
- 02WHOIS, IP, and URL lookups
- 03Email address validation
- 04QR generation and web text extraction
- 05HTTP security header analysis
- 06Website technology detection
Use cases
- 01Audit a domain's DNS and mail security
- 02Validate email addresses and domains
- 03Inspect website availability and security headers
- 04Extract webpage text or generate QR codes for agents
MCP support
It provides nine tools through an MCP server using streamable HTTP. Tool calls use x402 micropayments; initialization, tool listing, and ping are free.
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://tools.beethoven2024.com/mcpclaude mcp add --transport http wingedguardian-agent-tools https://tools.beethoven2024.com/mcp{"mcpServers":{"wingedguardian-agent-tools":{"type":"http","url":"https://tools.beethoven2024.com/mcp"}}}Open in Cursor{"servers":{"wingedguardian-agent-tools":{"type":"http","url":"https://tools.beethoven2024.com/mcp"}}}Open in VS Code{"mcpServers":{"wingedguardian-agent-tools":{"type":"http","url":"https://tools.beethoven2024.com/mcp"}}}{"mcpServers":{"wingedguardian-agent-tools":{"serverUrl":"https://tools.beethoven2024.com/mcp"}}}Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.
Tools
Details
From the project READMEAgent 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
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.