Bloomfilter

io.github.EronmmerPublished by GitHub account Eronmmerv0.1.1Updated Oct 25, 2026

Service that lets AI Agents search, register, and configure domains

VerifiedSTDIODesktop onlyCloud & InfrastructureFinanceBusiness & Commerce

Overview

AI-generated overview

A local MCP server that lets an assistant search, register and renew domain names and manage DNS records through the Bloomfilter API, paying in USDC from a Base

What you can do
Search domain availability across multiple TLDs and get registration, renewal and transfer pricing without a wallet. Look up details of registered domains such as status, expiry, nameservers and lock state. Register new domains and renew existing ones, with USDC payment handled automatically. List, add, update and delete DNS records of many types for a domain. View the wallet address, domain count and total spent on the account.
When to use it
Useful when you want an assistant to check domain availability and pricing, or to register domains and edit DNS records directly from a chat client without a dashboard or credit card. Best suited to users who already hold USDC on Base and are comfortable letting an agent spend it.
Requirements
Runs locally over stdio, launched by an MCP client, typically via npx with Node.js 20 or newer. Requires the BLOOMFILTER_PRIVATE_KEY environment variable holding a hex-encoded wallet private key funded with USDC on Base for paid operations; without it only search and pricing work. Optional BLOOMFILTER_API_URL and BLOOMFILTER_NETWORK variables override the API endpoint and network. Network access to the Bloomfilter API is needed.
Before you install
The server needs a wallet private key in BLOOMFILTER_PRIVATE_KEY, which gives it signing power over that wallet; use a dedicated wallet holding only the USDC you are willing to spend. Paid actions spend real money: domain registration and renewal, plus a per-change fee for DNS record changes. Registering, renewing and adding, updating or deleting DNS records all change state and can break a live domain. Payments and sign-in are handled through third parties, the Bloomfilter API and the Base x402

Installation

In SourceWeft

  1. Open Bloomfilter in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

@bloomfilter/mcp-server

[Image]

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

bash
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:

json
{	"mcpServers": {		"bloomfilter": {			"command": "npx",			"args": ["-y", "@bloomfilter/mcp-server"],			"env": {				"BLOOMFILTER_PRIVATE_KEY": "0x..."			}		}	}}

Config file location by client

ClientConfig file
Claude Desktopclaude_desktop_config.json
Claude Code~/.claude/settings.json
Cursor.cursor/mcp.json
Windsurf~/.codeium/windsurf/mcp_config.json
VS Code + Copilot.vscode/mcp.json
ClineVia Cline MCP settings UI
JetBrains IDEsSettings > Tools > AI Assistant > MCP

Any MCP-compatible client that supports stdio servers will work.

Environment variables

VariableRequiredDefaultDescription
BLOOMFILTER_PRIVATE_KEYFor paid operations-EVM private key (hex). Used for x402 payments and wallet-based auth.
BLOOMFILTER_API_URLNohttps://api.bloomfilter.xyzAPI 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:

  1. The API responds with HTTP 402 and a payment requirement
  2. The MCP server signs a USDC payment with your wallet
  3. 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

bash
git clone https://github.com/BloomFilter-Labs/mcp-server-bloomfilter.gitcd mcp-server-bloomfilternpm installnpm run build

Requires Node.js 20+.

License

MIT

Source: README.md at commit 6b5fe18

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.1LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts