# Nymrel (remote · mcp.nymrel.com)

Four public utilities plus seven OAuth-protected Remote read tools for paired Nymrel devices.

- Trust score: 75/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-06

## Components

- remote · `mcp.nymrel.com`: 75/100 (this document), [markdown](https://verifymcp.io/servers/nymrel-nymrel/mcp.md), [page](https://verifymcp.io/servers/nymrel-nymrel/mcp)

## Channel facts

- Endpoint: `https://mcp.nymrel.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.4.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-06.

- **Endpoint Security**: 83/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 68/100
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 83/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 40% of tool parameters carry a description.
  - Structured output schemas are declared (36% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http nymrel-nymrel 'https://mcp.nymrel.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "nymrel-nymrel": {
      "url": "https://mcp.nymrel.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "nymrel-nymrel": {
      "type": "http",
      "url": "https://mcp.nymrel.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.nymrel-nymrel]
url = "https://mcp.nymrel.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "nymrel-nymrel": {
      "type": "remote",
      "url": "https://mcp.nymrel.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add nymrel-nymrel --url 'https://mcp.nymrel.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  nymrel-nymrel:
    url: "https://mcp.nymrel.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "nymrel-nymrel": {
      "Transport": "http",
      "Url": "https://mcp.nymrel.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add nymrel-nymrel -t streamable-http -u 'https://mcp.nymrel.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "nymrel-nymrel": {
      "type": "http",
      "url": "https://mcp.nymrel.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-06 (score 75, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-11-05 (score 75, +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.

### 2026-11-03 (score 74, +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.

### 2026-10-31 (score 73, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-30 (score 72)

First indexed and scored.

## MCP tools (11)

### `nymrel_audit_website` (~148 tokens)

Audit website discoverability

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.

Input parameters:

- `url` (string, required)

### `nymrel_golf_bag_gap` (~85 tokens)

Analyse golf bag gaps

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.

Input parameters:

- `clubs` (array, required)

### `nymrel_find_domain` (~203 tokens)

Find domain names

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.

Input parameters:

- `keyword_or_concept` (string, required)
- `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.

### `nymrel_social_clip_score` (~195 tokens)

Measure a short-video hook

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.

Input parameters:

- `target_platform` (string)
- `transcript_text` (string, required)

### `nymrel_remote_list_devices` (~35 tokens)

List remote devices

Use this when the user wants to see paired Nymrel Remote devices and current reachability before working with one.

### `nymrel_remote_read_file` (~114 tokens)

read file

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.

Input parameters:

- `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, required): Absolute path or path relative to the configured working directory.

### `nymrel_remote_list_directory` (~93 tokens)

list directory

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.

Input parameters:

- `depth` (integer)
- `device` (string): Paired device id or exact device name. Omit only when exactly one eligible device is available.
- `path` (string, required): Absolute path or path relative to the configured working directory.

### `nymrel_remote_get_file_info` (~85 tokens)

get file info

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.

Input parameters:

- `device` (string): Paired device id or exact device name. Omit only when exactly one eligible device is available.
- `path` (string, required): Absolute path or path relative to the configured working directory.

### `nymrel_remote_search_files` (~117 tokens)

search files

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.

Input parameters:

- `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, required): Absolute path or path relative to the configured working directory.
- `pattern` (string, required)

### `nymrel_remote_search_content` (~134 tokens)

search content

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.

Input parameters:

- `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, required): Absolute path or path relative to the configured working directory.
- `pattern` (string, required)

### `nymrel_remote_get_read_result` (~72 tokens)

Get remote read result

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.

Input parameters:

- `callId` (string, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/nymrel-nymrel/mcp#diagnostics

## Score history

- 2026-11-06: 75
- 2026-11-05: 75
- 2026-11-04: 74
- 2026-11-03: 74
- 2026-11-02: 73
- 2026-11-01: 73
- 2026-10-31: 73
- 2026-10-30: 72

## Common questions

### 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.

## Links

- Remote endpoint: https://mcp.nymrel.com/mcp
- Repository: https://github.com/nymrel/nymrel-plugin
- Website: https://nymrel.com/
- Changelog RSS feed: https://verifymcp.io/servers/nymrel-nymrel/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/nymrel-nymrel/mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/nymrel-nymrel/mcp.json
- HTML version of this page: https://verifymcp.io/servers/nymrel-nymrel/mcp