Nymrel
REMOTE · MCP.NYMREL.COM
Four public utilities plus seven OAuth-protected Remote read tools for paired Nymrel devices.
Available components
Last scanned (10 hours ago)
Scores higher than 63% of remote servers
Reachable. Last reached 6 Nov 2026.
Category Documents and Files
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 Security83
- 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. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. 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 is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability68
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1281 tokens (~116/item across 11 items; 11 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 Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage83
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 40% of tool parameters carry a description.Partial
- Structured output schemas are declared (36% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 11 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
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 30 Oct 26 72
First indexed and scored.
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 6 Nov 2026 · Probed https://mcp.nymrel.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.nymrel.com | CN=YR2,O=Let's Encrypt,C=US | 14 Oct 2026 | 12 Jan 2027 | RSA 2048 | SHA256-RSA | 60100cbc26c3fb84119cb0041fb5e69325f |
| SANs: mcp.nymrel.com | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of mcp.nymrel.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| nymrel.com. | DS published | 2371 | 13 | Verified |
| mcp.nymrel.com. | Verified address RRset verified with the apex keys |
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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.nymrel.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.nymrel.com/mcp | HTTPS enforced | 308 | https://mcp.nymrel.com/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 →
nymrel_audit_website Audit website discoverability ~148
Audit one public website for SEO, schema, and AI discoverability. Returns the score, grade, discoverability status, detected schema types and recommendations supplied by the audit. Results may contain only an aggregate summary; additional per-check evidence may be included. Report robots.txt, sitemap.xml, llms.txt or AI-crawler checks only when their evidence is present in the result; absent checks are unreported, not proven by an aggregate score or PASS. Preserve unmeasured checks and empty recommendations without inventing findings. This is not a ranking guarantee or a security, legal-compliance or crawler-access certification.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
nymrel_find_domain Find domain names ~203
Suggest domain names and check each one against public registry records. A name is only reported available when the registry clearly says it is free. When the lookup is inconclusive `availability_checked` is false and `available` is false, so read that as "not confirmed free" rather than "already taken" - some TLDs have no registry service to ask. Confirm at a registrar before buying. `brandability_score` is an opinion about the string, not a claim about how the name will perform; `brandability_factors` reports what it was computed from so you can weigh it yourself.
| Name | Type | Req | Description |
|---|---|---|---|
| keyword_or_concept | string | yes | – |
| tlds | – | – | Up to 6 TLDs, each written with its leading dot - ".com", not "com". The upstream enforces this with a regex and rejects the request otherwise. Defaults to .com, .ai, .app and .dev. |
Structured output declared, but exposes no named fields.
No examples provided.
nymrel_golf_bag_gap Analyse golf bag gaps ~85
Analyse carry-distance gaps for a structured list of golf clubs. Every club needs a ``name`` and its measured ``carry_distance_yards``; ``loft_degrees`` is optional. Pass 1 to 14 clubs with unique names. The upstream rejects any other key, so send only these three.
| Name | Type | Req | Description |
|---|---|---|---|
| clubs | array | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
nymrel_remote_get_file_info get file info ~85
Use this when the user explicitly wants Nymrel Remote to return metadata for a file or directory. Select the target with the optional device argument.
| Name | Type | Req | Description |
|---|---|---|---|
| device | string | – | Paired device id or exact device name. Omit only when exactly one eligible device is available. |
| path | string | yes | Absolute path or path relative to the configured working directory. |
No output schema declared.
No examples provided.
nymrel_remote_get_read_result Get remote read result ~72
Retrieve the result of your pending Nymrel Remote read using its callId. If a file inspection returns pending, use this tool instead of submitting that inspection again. It never starts a new device operation. If still pending, wait briefly before checking again.
| Name | Type | Req | Description |
|---|---|---|---|
| callId | string | yes | – |
No output schema declared.
No examples provided.
nymrel_remote_list_devices List remote devices ~35
Use this when the user wants to see paired Nymrel Remote devices and current reachability before working with one.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
nymrel_remote_list_directory list directory ~93
Use this when the user explicitly wants Nymrel Remote to list a directory tree with a bounded recursion depth. Select the target with the optional device argument.
| Name | Type | Req | Description |
|---|---|---|---|
| depth | integer | – | – |
| device | string | – | Paired device id or exact device name. Omit only when exactly one eligible device is available. |
| path | string | yes | Absolute path or path relative to the configured working directory. |
No output schema declared.
No examples provided.
nymrel_remote_read_file read file ~114
Use this when the user explicitly wants Nymrel Remote to read a UTF-8 text file with optional line pagination. Select the target with the optional device argument.
| Name | Type | Req | Description |
|---|---|---|---|
| device | string | – | Paired device id or exact device name. Omit only when exactly one eligible device is available. |
| length | integer | – | – |
| offset | integer | – | 0-based start line; negative values read from the tail. |
| path | string | yes | Absolute path or path relative to the configured working directory. |
No output schema declared.
No examples provided.
nymrel_remote_search_content search content ~134
Use this when the user explicitly wants Nymrel Remote to search UTF-8 file contents below an allowed path. Select the target with the optional device argument.
| Name | Type | Req | Description |
|---|---|---|---|
| device | string | – | Paired device id or exact device name. Omit only when exactly one eligible device is available. |
| filePattern | string | – | – |
| ignoreCase | boolean | – | – |
| literalSearch | boolean | – | – |
| maxDepth | integer | – | – |
| maxResults | integer | – | – |
| path | string | yes | Absolute path or path relative to the configured working directory. |
| pattern | string | yes | – |
No output schema declared.
No examples provided.
nymrel_remote_search_files search files ~117
Use this when the user explicitly wants Nymrel Remote to search file and directory names below an allowed path. Select the target with the optional device argument.
| Name | Type | Req | Description |
|---|---|---|---|
| device | string | – | Paired device id or exact device name. Omit only when exactly one eligible device is available. |
| ignoreCase | boolean | – | – |
| maxDepth | integer | – | – |
| maxResults | integer | – | – |
| path | string | yes | Absolute path or path relative to the configured working directory. |
| pattern | string | yes | – |
No output schema declared.
No examples provided.
nymrel_social_clip_score Measure a short-video hook ~195
Measure what the opening of a short-video transcript actually does. Returns each measured signal - opening word count, whether it opens on a hook pattern, whether it addresses the viewer, curiosity signals, whether the total word count sits in the platform's range - plus `hook_score`, a 0-100 rollup of exactly those signals, and suggested edits. `target_platform` accepts `tiktok`, `instagram_reels`, `youtube_shorts`, or `x`. The `reels` and `shorts` aliases normalize to their corresponding canonical IDs, which the result echoes. Every figure describes the text the caller supplied. This does not estimate reach, views, retention or virality; those are outcomes in the world that this tool never observes. Read `signals` to see what moved the score.
| Name | Type | Req | Description |
|---|---|---|---|
| target_platform | string | – | – |
| transcript_text | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the Nymrel MCP server?
Nymrel is a hosted endpoint at https://mcp.nymrel.com/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 · mcp.nymrel.com
claude mcp add --transport http nymrel-nymrel 'https://mcp.nymrel.com/mcp'
What is the Nymrel MCP server?
Nymrel is an MCP server listed in the public MCP registry as io.github.nymrel/nymrel. Four public utilities plus seven OAuth-protected Remote read tools for paired Nymrel devices. This page covers its hosted endpoint (https://mcp.nymrel.com/mcp).
Is the Nymrel MCP server safe to use?
Nymrel scores 75 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 Nymrel MCP server expose?
Nymrel exposes 11 tools: nymrel_audit_website, nymrel_golf_bag_gap, nymrel_find_domain, nymrel_social_clip_score, nymrel_remote_list_devices, and 6 more. Their descriptions and schemas cost roughly 1,281 tokens of context every time the server is loaded.
Does the Nymrel MCP server require authentication?
No. We connected to Nymrel without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Nymrel MCP server still maintained?
Nymrel is still listed as active in the MCP registry. We last reached this channel on 6 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Nymrel MCP server?
VerifyMCP ran 13 checks on Nymrel, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.