Nomok
REMOTE · NOMOK.APP
Check name availability on 70+ platforms: domains, social networks, marketplaces.
Available components
Last scanned (4 hours ago)
Scores higher than 85% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Marketing and SEO
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability70
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 552 tokens (~184/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management73
- Stability observed for 22 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage94
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 83% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Oct 26 +1
- Server version: 1950c31 → 7828489 functional
- 21 Oct 26 0
- Tool “check_name” rewrote its description, which is the text the model reads security
- Schema quality: good → excellent functional
- Server version: 60acd6d → 1950c31 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://nomok.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=nomok.app | CN=YE1,O=Let's Encrypt,C=US | 13 Oct 2026 | 11 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 5a4c024926ac1e47407c884cd5d2745ad12 |
| SANs: nomok.app, www.nomok.app | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of nomok.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| nomok.app. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' https://*.google.com https://*.googlesyndication.com https://*.googletagmanager.com https://*.google-analytics.com https://*.googleadservices.com https://*.doubleclick.net https://*.gstatic.com https://*.adtrafficquality.google; style-src 'self' 'unsafe-inline'; img-src 'self' data: blob: https:; font-src 'self'; connect-src 'self' https://*.google.com https://*.googlesyndication.com https://*.googletagmanager.com https://*.google-analytics.com https://*.googleadservices.com https://*.doubleclick.net https://*.gstatic.com https://*.adtrafficquality.google; frame-src 'self' https://*.google.com https://*.googlesyndication.com https://*.googletagmanager.com https://*.google-analytics.com https://*.googleadservices.com https://*.doubleclick.net https://*.gstatic.com https://*.adtrafficquality.google; object-src 'none'; base-uri 'self'; form-action 'self'; upgrade-insecure-requests; frame-ancestors 'none' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), interest-cohort=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://nomok.app/mcp | Verified | 200 | |
| http (plaintext) | http://nomok.app/mcp | HTTPS enforced | 301 | https://nomok.app/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_domains Check domain names ~199
Checks domain name availability for up to 10 names on chosen extensions (DNS + RDAP registry lookup). Default extensions: .com, .net, .org, .io, .app, .dev, .co, .fr. Supported: .com, .fr, .net, .org, .info, .biz, .co, .de, .uk, .it, .es, .be, .ch, .nl, .eu, .ca, .us, .io, .ai, .me, .gg, .tv, .app, .dev, .tech, .studio, .design, .art, .shop, .store, .online, .xyz. Ideal to compare several name ideas quickly. Available domains come with a registration link and indicative price.
| Name | Type | Req | Description |
|---|---|---|---|
| names | array | yes | – |
| tlds | array | – | Extensions to check, without dot (default: main ones) |
No output schema declared.
No examples provided.
check_name Check a name everywhere ~205
Checks whether a name/handle is available on 70+ platforms at once: domain names (.com, .fr, .io, .app…), social networks (Instagram, TikTok, X, YouTube…), creative and dev platforms (GitHub, Behance…), e-commerce, freelance, gaming and company registries. Takes 5-15 s on first call (results cached 10 min). Statuses: available, likely_available, taken, manual (cannot be checked automatically), unknown (check failed). Never present manual/unknown results as available. Available domains come with a registration link. Each call is a full live search: to compare many name ideas, first use check_domains (up to 10 names per call), then check_name only on the shortlist.
| Name | Type | Req | Description |
|---|---|---|---|
| categories | array | – | Optional: only return these categories (all by default) |
| name | string | yes | Name or handle to check (2-50 chars: letters, digits, . - _) |
No output schema declared.
No examples provided.
suggest_names Suggest available name variants ~81
Generates common variants of a name (get-, try-, -hq, -app, -studio…) and checks which ones are available as a domain (.com by default). Use when the exact name is taken.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Base name, letters/digits/hyphens |
| tld | string | – | Extension to check, default com |
No output schema declared.
No examples provided.
How do I install the Nomok MCP server?
Nomok is a hosted endpoint at https://nomok.app/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · nomok.app
claude mcp add --transport http app-nomok-nomok 'https://nomok.app/mcp'
What is the Nomok MCP server?
Nomok is an MCP server listed in the public MCP registry as app.nomok/nomok. Check name availability on 70+ platforms: domains, social networks, marketplaces. This page covers its hosted endpoint (https://nomok.app/mcp).
Is the Nomok MCP server safe to use?
Nomok scores 82 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Nomok MCP server expose?
Nomok exposes 3 tools: check_name, check_domains, suggest_names. Their descriptions and schemas cost roughly 485 tokens of context every time the server is loaded.
Does the Nomok MCP server require authentication?
No. We connected to Nomok without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Nomok MCP server still maintained?
Nomok is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.