1. Conduid
  2. Developer Tools
  3. Bloomfilter
MCP server · Developer Tools

Bloomfilter

MCP server for Bloomfilter, a domain registration service for AI Agents.

70Good

Scored just now · breakdown

About Bloomfilter

Bloomfilter is an MCP server published by BloomFilter-Labs in the Developer Tools category: mCP server for Bloomfilter, a domain registration service for AI Agents.

The repository has 10 stars and 2 forks, with the last commit 7 months ago. Six months or more without a commit doesn't mean the server is broken, but check the open issues before depending on it in production.

Install

From source
git clone https://github.com/BloomFilter-Labs/mcp-server-bloomfilter

This server has no ConduID identity, so agent calls to it are not receipted. Pin the version you install and review the source before granting it credentials.

Tools (10)

add_dns_recordAdd a DNS record to a domain you own. Costs $0.10 USDC per record.

Parameters not published.

delete_dns_recordDelete a DNS record from a domain you own. Costs $0.10 USDC.

Parameters not published.

get_accountGet account information — wallet address, domain count, total spent.

Parameters not published.

get_domain_infoGet detailed information about a registered domain (status, expiry, nameservers, etc.).

Parameters not published.

get_pricingGet domain registration, renewal, and transfer pricing. Omit tld for all TLDs, or specify one.

Parameters not published.

list_dns_recordsList all DNS records for a domain you own.

Parameters not published.

register_domainRegister a new domain name. Requires USDC payment via x402. Handles async provisioning automatically.

Parameters not published.

renew_domainRenew an existing domain registration. Requires USDC payment via x402.

Parameters not published.

search_domainsSearch for available domain names. Returns availability and pricing for each TLD.

Parameters not published.

update_dns_recordUpdate an existing DNS record. Costs $0.10 USDC. Use list_dns_records to find the record_id.

Parameters not published.

Ask AI

✦

Ask AI about Bloomfilter

Powered by Claude · Grounded in docs

I know everything about Bloomfilter. Ask me about installation, configuration, usage, or troubleshooting.

Security checks

Static checks derived from the repository just now. Heuristics on the source, not an audit.

  • ✓README presentThe repository ships documentation.
  • ✓License declaredUsable under a stated license.
  • !Tests presentNo tests found. Behaviour changes may go unnoticed between versions.
  • ✓Dependencies pinnedA lockfile pins dependency versions.
  • ✓No dynamic code executionSource scan found no eval, dynamic Function, or shell execution.
  • !Scoped permissionsDoesn't declare a permission scope. Assume it can do anything its process can.

Releases

v0.1.2Glass Table Girls · 24 Feb 2026Changed enhance DNS record tool descriptions for sequential operations
v0.1.1Wicked Games · 22 Feb 2026Changed Added `mcpName` field to package.json for MCP Registry compatibility
v0.1.0House of Balloons · 21 Feb 2026Initial release of `@bloomfilter/mcp-server`, an MCP server that lets AI agents register ICANN domains, manage DNS records, and handle payments autonomously via the Bloomfilter API. Tools Free (no wallet required)** `search_domains`: check…

README

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

  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

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

README fetched from the repository just now. The original is authoritative.

Questions

About Bloomfilter

How do I install Bloomfilter?

No package has been published for this server, so install it from source: clone the repository and follow its README.

Is Bloomfilter safe to use with an AI agent?

Its trust score is 70 out of 100 (good). It passes 4 of the 6 static security checks run so far; the failures are listed above. It has no ConduID identity yet, so agent calls to it are not receipted.

Is Bloomfilter still maintained?

The last commit was 7 months ago. That's long enough that you should check whether the maintainer is responding to issues before depending on it.