
Bloomfilter
- 9 repo stars
- Updated February 26, 2026
- BloomFilter-Labs/mcp-server-bloomfilter
Bloomfilter MCP is a MCP server that lets AI agents search, register, and configure domains using Bloomfilter on Base-paid USDC.
About
Bloomfilter MCP connects AI coding agents to Bloomfilter’s domain services so developers can secure names and tune DNS without context-switching to registrar UIs. The stdio server expects a hex-encoded BLOOMFILTER_PRIVATE_KEY for a wallet that holds USDC on Base to pay for registrations and DNS operations, with network defaulting to eip155:8453 unless you override BLOOMFILTER_NETWORK or the API base URL. That makes it a fit during Validate when you lock a brand and landing URL, Launch when distribution depends on a clean hostname, and Build when integrations require programmatic record updates. It is infrastructure MCP tooling, not a copywriting or SEO skill—you still own wallet funding and naming decisions. Version 0.1.1 is early but purpose-built for agent-led domain lifecycle tasks.
- Agent-driven domain search, registration, and DNS configuration through Bloomfilter APIs
- Requires BLOOMFILTER_PRIVATE_KEY for a wallet funded with USDC on Base mainnet (default eip155:8453)
- NPM @bloomfilter/mcp-server stdio transport; optional BLOOMFILTER_API_URL override
- Server version 0.1.1 from BloomFilter-Labs/mcp-server-bloomfilter
Bloomfilter by the numbers
- Data as of Jul 7, 2026 (Skillselion catalog sync)
claude mcp add --env BLOOMFILTER_PRIVATE_KEY=YOUR_BLOOMFILTER_PRIVATE_KEY --env BLOOMFILTER_API_URL=YOUR_BLOOMFILTER_API_URL --env BLOOMFILTER_NETWORK=YOUR_BLOOMFILTER_NETWORK bloomfilter -- npx -y @bloomfilter/mcp-serverAdd your badge
Show developers this MCP server is listed on Skillselion. Paste this into your README.
| repo stars | ★ 9 |
|---|---|
| Package | @bloomfilter/mcp-server |
| Transport | STDIO |
| Auth | Required |
| Last updated | February 26, 2026 |
| Repository | BloomFilter-Labs/mcp-server-bloomfilter ↗ |
What it does
Let your agent search, register, and configure domains via Bloomfilter using a USDC-funded wallet on Base instead of manual registrar dashboards.
Who is it for?
Crypto-comfortable developers who want agent-managed domains on Bloomfilter with USDC on Base.
Skip if: Skip if you refuse on-chain payments, need enterprise registrar contracts only, or cannot fund a Base USDC wallet.
What you get
After configuring the wallet key and MCP server, your agent can execute Bloomfilter domain and DNS operations programmatically for your branded URL.
- Domain availability checks and registrations via agent tools
- DNS configuration changes applied through Bloomfilter API
- Repeatable agent workflow for hostname updates during launch
By the numbers
- Server and npm package version 0.1.1
- Default API base https://api.bloomfilter.xyz
- Three configurable env vars documented (private key required; API URL and network optional)
README.md
@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-server
The 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 |
|---|---|
| Claude Desktop | claude_desktop_config.json |
| Claude Code | ~/.claude/settings.json |
| Cursor | .cursor/mcp.json |
| Windsurf | ~/.codeium/windsurf/mcp_config.json |
| VS Code + Copilot | .vscode/mcp.json |
| Cline | Via Cline MCP settings UI |
| JetBrains IDEs | Settings > Tools > AI Assistant > MCP |
Any MCP-compatible client that supports stdio servers will work.
Environment variables
| Variable | Required | Default | Description |
|---|---|---|---|
BLOOMFILTER_PRIVATE_KEY |
For paid operations | - | EVM private key (hex). Used for x402 payments and wallet-based auth. |
BLOOMFILTER_API_URL |
No | https://api.bloomfilter.xyz |
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_domains: Check if a domain is available and get pricing. Searches across multiple TLDs at once.get_pricing: Get registration, renewal, and transfer pricing for one or all supported TLDs.
Authenticated (wallet required)
get_domain_info: Get details about a registered domain: status, expiry, nameservers, lock state.register_domain: Register a new domain. Pays with USDC via x402 automatically. Handles async provisioning.renew_domain: Extend a domain registration. Same x402 payment flow.get_account: View wallet address, domain count, total spent.
DNS Management (wallet required, $0.10 USDC per mutation)
list_dns_records: List all DNS records for a domain.add_dns_record: Add a DNS record (A, AAAA, CNAME, MX, TXT, NS, SRV, CAA, FORWARD).update_dns_record: Update an existing DNS record by ID.delete_dns_record: Delete 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 build
Requires Node.js 20+.
License
MIT
Recommended MCP Servers
How it compares
Domain and DNS MCP on Bloomfilter, not a static landing-page generator or SEO audit skill.
FAQ
Who is io.github.Eronmmer/bloomfilter for?
It is for developers using MCP agents who want Bloomfilter to handle domain search, purchase, and DNS with a funded Base USDC wallet.
When should I use io.github.Eronmmer/bloomfilter?
Use it when validating or launching a product and you need programmatic domain registration and DNS configuration from your agent.
How do I add io.github.Eronmmer/bloomfilter to my agent?
Install @bloomfilter/mcp-server, set BLOOMFILTER_PRIVATE_KEY for a USDC-funded wallet on Base, optionally set API URL or network, and add the stdio server to MCP config.