Developer Tools
nomok.app
Checks whether a name or handle is available across domains and 70+ platforms, and suggests available variants.
ENDPOINT 1
https://nomok.app/mcp
MCP server metadata
- Name
- nomok
- Version
- 919831a
Use check_name to check one name on 70+ platforms (domains, social networks, marketplaces…), check_domains to compare several name ideas on domain extensions, suggest_names for available variants. Report "manual" and "unknown" results as unverified, never as available. Results are live checks, cached 10 minutes.
Known tools 3
check_nameChecks whether a name/handle is available on 70+ platforms at once: domain names (.
Inferred read-onlycheck_domainsChecks domain name availability for up to 10 names on chosen extensions (DNS + RDAP registry lookup).
Inferred read-onlysuggest_namesGenerates common variants of a name (get-, try-, -hq, -app, -studio…) and checks which ones are available as a domain (.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.nomok]
url = "https://nomok.app/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"nomok": {
"type": "http",
"url": "https://nomok.app/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: nomok
Remote MCP URL: https://nomok.app/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"nomok": {
"url": "https://nomok.app/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"nomok": {
"type": "http",
"url": "https://nomok.app/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "nomok",
"transport": "streamable-http",
"url": "https://nomok.app/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.