Building for composable agentic services: nameIntel x402 via MCP

dudemanAtl1 pts1 comments

NameIntel(1) — name(8) intelligence for the agent economy

live<br>· us-east-1

v1.0.0<br>mcp-registry: io.nameintel/server<br>x402: bypass→enforce

/health<br>/changelog

Volume 1 · Issue 1 · May 2026 · Silverback CTO

filed under /branding /mcp /x402 /geo

Issue №1 · The agent-economy edition

Clear to launch.<br>A name intelligence<br>service for AI agents.

NameIntel is a remote MCP server and REST API that scores any candidate brand name across five dimensions — domain availability, USPTO trademark conflict, social-handle availability, SEO strength, and AI findability[1] — in a single call. Every endpoint is priced in USDC and settled over the x402 micropayment protocol on Base and Solana. There are no API keys to provision, no accounts to register, and no rate-limit forms to fill out. Payment is authentication.

$ claude mcp add nameintel

read the spec<br>openapi.json

▪ remote MCP (Streamable HTTP)<br>▪ USDC · Base + Solana<br>▪ Industry-first GEO score<br>▪ Self-describing 402s

§1 · transaction trace

live

// step 1 — call without payment

$ curl -X POST https://api.nameintel.io/api/v1/score \

-H "content-type: application/json" \

-d '{"name": "Lumina"}'

// step 2 — server returns the menu

HTTP/2 402 Payment Required

content-type: application/json

"error": "Payment Required",

"requested": { "price": "0.05", "currency": "USDC" },

"payment": { "chain": "base", "header": "X-PAYMENT" },

"menu": [ /* full price list */ ]

// step 3 — sign the payload, retry

$ curl --header "X-PAYMENT: $(sign $REQ)" ...

// step 4 — succeed

HTTP/2 200 OK

{ "name": "Lumina", "composite": 78,

"verdict": "clear to launch with .io",

"sub": { "domain": 62, "tm": 71, "social": 80, "seo": 82, "geo": 81 } }

total: $0.05 USDC · settle:<br>api.cdp.coinbase.com/platform/v2/x402

↑ what an agent sees, in real time.

5 dimensions · 1 call<br>$0.01 trademark check<br>$0.05 full score<br>USDC · Base + Solana<br>no signup · no API keys<br>remote MCP — Streamable HTTP<br>io.nameintel/server<br>live in the MCP registry

5 dimensions · 1 call<br>$0.01 trademark check<br>$0.05 full score<br>USDC · Base + Solana<br>no signup · no API keys<br>remote MCP — Streamable HTTP<br>io.nameintel/server<br>live in the MCP registry

§ 2

The five<br>dimensions.

Most naming tools check one or two signals and call it research. NameIntel returns every signal in a single call, weighted into a composite zero-to-one-hundred score, with a sub-score and a one-sentence verdict for each dimension. The whole call returns in under ten seconds.

dimension

measures

data source

endpoint

01

Domain

availability + pricing

.com, .io, .ai, .app, .co, .dev and other TLDs. Premium and auction detection.

RDAP · Route 53

/check/domain

02

Trademark

USPTO conflict screen

Exact matches, similar marks, Nice-class analysis, risk level. Live filings + pending applications.

USPTO TSDR

/check/trademark

03

Social

handle availability · 12+ platforms

X / Instagram / TikTok / LinkedIn / YouTube / GitHub / Threads / Reddit / Pinterest / Facebook / Bluesky / Twitch.

HTTP HEAD · parallel

/check/social

04

SEO

keyword strength · competition

Search-friendliness, generic-term collision, and competition risk for the candidate.

internal

/score

05

GEO score<br>industry-first

AI findability rating

How likely the name surfaces correctly in ChatGPT, Perplexity, Claude, and Gemini answers. Entity collision · semantic distinctiveness · corpus saturation · phonetic clarity.

Claude · Bedrock

/check/geo

Composite

weighted, 0–100, plus verdict

All five sub-scores rolled into a single number, plus a one-sentence verdict and a per-dimension risk callout.

Promise.allSettled

/score

“Nobody else scores names for AI findability. As AI-generated answers increasingly decide which brands a consumer ever hears of, this becomes the load-bearing dimension of naming — and the one we measure first.”

— from the GEO design memo, 2026

§ 3 · For Claude Desktop, Claude Code, any MCP client

Three steps.<br>No accounts.

No .mcpb to download. No keys to register. No environment variables to plumb. Paste one URL, fund a wallet, score names.

01 ▸

Add the server.

One terminal command. Or paste https://mcp.nameintel.io/mcp into Claude Desktop → Settings → Connectors.

02 ▸

Fund a wallet, wire up payments.

Base or Solana, $5 USDC covers roughly a hundred full scores. Whatever you don’t spend, you keep.

One-line setup for Claude clients via the Coinbase Payments MCP:<br>npx @coinbase/payments-mcp --client claude --auto-config

03 ▸

Ask Claude to score a name.

Payment is the authentication. There’s nothing else to set up.

install · claude code<br>single command

# 1. One-time: install the Coinbase Payments MCP so your agent can sign x402.<br>$ npx @coinbase/payments-mcp --client claude --auto-config

# 2. Add NameIntel to Claude Code:<br>$ claude mcp add --transport http nameintel https://mcp.nameintel.io/mcp

# Or, in any MCP-capable client, point it at:<br>https://mcp.nameintel.io/mcp # Streamable HTTP

# Verify with the official MCP registry:<br>$ curl...

nameintel claude score payment http name

Related Articles