The Bloomfilter MCP server enables AI agents to autonomously search, register, and manage domain names and DNS records using USDC payments on Base via the x402 protocol.
Domain Search & Pricing (free, no wallet required)
search_domains: Check availability and pricing across multiple TLDs simultaneouslyget_pricing: Retrieve registration, renewal, and transfer pricing for one or all supported TLDs
Domain Management (wallet required)
register_domain: Register a new domain for 1–10 years with automatic USDC paymentrenew_domain: Extend an existing domain registration for 1–10 yearsget_domain_info: Fetch domain details including status, expiry, nameservers, and lock stateget_account: View wallet address, number of registered domains, and total amount spent
DNS Record Management (wallet required, $0.10 USDC per mutation)
list_dns_records: View all DNS records for a domain you ownadd_dns_record: Add a new record (A, AAAA, CNAME, MX, TXT, NS, SRV, CAA, FORWARD)update_dns_record: Modify an existing DNS record by IDdelete_dns_record: Remove a DNS record by ID
Authentication is handled automatically via SIWE (Sign-In With Ethereum) using an EVM private key, and works with any MCP-compatible client (Claude Desktop, Cursor, Windsurf, VS Code, etc.).
Utilizes Ethereum-compatible wallets for authentication via Sign-In with Ethereum (SIWE) and handles domain registration payments using USDC on the Base network.
@bloomfilter/mcp-server
MCP server for Bloomfilter, search & register domain names and manage DNS records from AI agents.
Bloomfilter is a domain registration and configuration API that uses x402 for payments. Point your AI agent at the Bloomfilter API, give it a wallet with some USDC, and it can autonomously search, register, and configure domains.
No login, no credit card, no dashboard. Just HTTP requests and a crypto wallet.
This MCP server wraps the Bloomfilter API so that any MCP-compatible client (Claude Desktop, Cursor, Windsurf, custom agents, etc.) can use it as a tool provider.
Quick Start
BLOOMFILTER_PRIVATE_KEY=0x... npx @bloomfilter/mcp-serverThe server communicates over stdio (JSON-RPC). It's meant to be launched by an MCP client, not run standalone.
Configuration
Add this JSON to your MCP client's config file:
{
"mcpServers": {
"bloomfilter": {
"command": "npx",
"args": ["-y", "@bloomfilter/mcp-server"],
"env": {
"BLOOMFILTER_PRIVATE_KEY": "0x..."
}
}
}
}Config file location by client
Client | Config file |
| |
| |
| |
| |
| |
Via Cline MCP settings UI | |
Settings > Tools > AI Assistant > MCP |
Any MCP-compatible client that supports stdio servers will work.
Environment variables
Variable | Required | Default | Description |
| For paid operations | - | EVM private key (hex). Used for x402 payments and wallet-based auth. |
| No |
| API base URL. |
Without a private key, only search_domains and get_pricing work. Everything else requires a wallet.
Tools
The server exposes 10 tools:
Free (no wallet needed)
search_domainsCheck if a domain is available and get pricing. Searches across multiple TLDs at once.get_pricingGet registration, renewal, and transfer pricing for one or all supported TLDs.
Authenticated (wallet required)
get_domain_infoGet details about a registered domain: status, expiry, nameservers, lock state.register_domainRegister a new domain. Pays with USDC via x402 automatically. Handles async provisioning.renew_domainExtend a domain registration. Same x402 payment flow.get_accountView wallet address, domain count, total spent.
DNS Management (wallet required, $0.10 USDC per mutation)
list_dns_recordsList all DNS records for a domain.add_dns_recordAdd a DNS record (A, AAAA, CNAME, MX, TXT, NS, SRV, CAA, FORWARD).update_dns_recordUpdate an existing DNS record by ID.delete_dns_recordDelete a DNS record by ID.
How Payments Work
Bloomfilter uses the x402 protocol, an HTTP-native payment standard. When a tool triggers a paid API call, the server handles payment negotiation automatically:
The API responds with HTTP 402 and a payment requirement
The MCP server signs a USDC payment with your wallet
The API verifies the payment and completes the request
All payments are in USDC on Base (an Ethereum L2). You need USDC in the wallet corresponding to your private key.
Authentication
The server authenticates with the Bloomfilter API using SIWE (Sign-In With Ethereum). This happens automatically on the first authenticated tool call. No setup needed beyond providing your private key.
Documentation
Full API reference and guides at docs.bloomfilter.xyz.
Building from Source
git clone https://github.com/BloomFilter-Labs/mcp-server-bloomfilter.git
cd mcp-server-bloomfilter
npm install
npm run buildRequires Node.js 20+.
License
MIT