Docs

names.dev MCP

names.dev exposes an agent-native MCP server at /api/mcp. Read tools are open in dev; production deployments gate access behind MCP_BEARER_TOKENS and every write tool requires a one-shot human approval token.

Discovery

curl -H "Authorization: Bearer $TOKEN" \
     https://names.dev/api/mcp

Local development uses http://localhost:3000/api/mcp.

Read-only tools (v1)

find_namesscore_namecheck_identity_surfacescheck_domainscheck_handlescheck_namespacescheck_app_store_namecheck_ios_bundle_idcheck_google_play_namecheck_android_packagesearch_inventoryestimate_valuewatch_namecreate_identity_report

Write tools (require approval)

register_domainprepare_offermake_offersetup_dnsverify_inventorylist_name_for_salecreate_names_manifestlaunch_identity

v1 of names.dev deliberately refuses every write call. The approval token is minted by the UI in response to an explicit human confirmation, signed with HMAC-SHA256 over (id | scope | subject | expiresAt), and stored single-use server-side.

Public package status

npm, PyPI, and MCP Registry publication are intentionally held until the Streamable HTTP transport, auth token UX, versioned tool schemas, privacy copy, and release provenance are stable. The current endpoint is production protected and suitable for private beta testing.