# Nalpeiron Docs (remote · docs.nalpeiron.com)

Search and browse Nalpeiron product documentation (Zentitle2, ZenGain, ZenMeter, EUP) via GitBook.

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

## Components

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

## Channel facts

- Endpoint: `https://docs.nalpeiron.com/~gitbook/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.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-09-24.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 75/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 649 tokens (~162/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 53/100
  - Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 95/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 86% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the Nalpeiron Docs MCP server?

Nalpeiron Docs is a hosted endpoint at https://docs.nalpeiron.com/~gitbook/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 com-nalpeiron-docs-mcp 'https://docs.nalpeiron.com/~gitbook/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-nalpeiron-docs-mcp": {
      "url": "https://docs.nalpeiron.com/~gitbook/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-nalpeiron-docs-mcp": {
      "type": "http",
      "url": "https://docs.nalpeiron.com/~gitbook/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-nalpeiron-docs-mcp]
url = "https://docs.nalpeiron.com/~gitbook/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add com-nalpeiron-docs-mcp --url 'https://docs.nalpeiron.com/~gitbook/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-nalpeiron-docs-mcp:
    url: "https://docs.nalpeiron.com/~gitbook/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-nalpeiron-docs-mcp": {
      "Transport": "http",
      "Url": "https://docs.nalpeiron.com/~gitbook/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-nalpeiron-docs-mcp -t streamable-http -u 'https://docs.nalpeiron.com/~gitbook/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-nalpeiron-docs-mcp": {
      "type": "http",
      "url": "https://docs.nalpeiron.com/~gitbook/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-09-23 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-21 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-19 (score 77, +1)

- [security] The server changed its declared name: mcp-typescript server on vercel → docs.nalpeiron.com/~gitbook/mcp
- [functional] Server version: 0.1.0 → 0.27.2

### 2026-09-17 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-15 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-13 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-11 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-09 (score 72, 0)

- [functional improvement] Stability: unverified → 0.03

## MCP tools (4)

### `searchDocumentation` (~77 tokens)

Search across the documentation to find relevant information, code examples, API references, and guides. Use this tool when you need to answer questions about Nalpeiron Documentation, find specific documentation, understand how features work, or locate implementation details. The search returns contextual content with titles and direct links to the documentation pages.

Input parameters:

- `query` (string, required)

### `getPage` (~112 tokens)

Fetch the full markdown content of a specific documentation page from Nalpeiron Documentation. Use this when you have a page URL and want to read its content. Accepts full URLs (e.g. https://docs.nalpeiron.com//getting-started). Since `searchDocumentation` returns partial content, use `getPage` to retrieve the complete page when you need more details. The content includes links you can follow to navigate to related pages.

Input parameters:

- `url` (string, required): The URL of the page to fetch

### `askQuestion` (~133 tokens)

Ask a natural-language question about Nalpeiron Documentation and get a synthesized answer, with links to the source pages. Prefer this over `searchDocumentation` when you want a direct answer to a question rather than a list of matching pages; use `searchDocumentation`/`getPage` when you need to browse or read full pages yourself.

Input parameters:

- `goal` (string): The broader end goal you are ultimately trying to accomplish (as/on behalf of the user). Used to tailor the answer to be most useful for your goal. Optional.
- `question` (string, required): The natural-language question to answer about Nalpeiron Documentation.

### `sendFeedback` (~327 tokens)

Report an issue in the documentation of Nalpeiron Documentation so the team can fix it. Use it whenever, while helping a user, you come across content that is outdated, contradictory, missing information, or otherwise unhelpful. Also use it when the user themselves reports a problem with the docs, even if you could not verify it yourself. If it's your own observation, do a quick sanity check that the issue is real before reporting — no need to exhaustively re-read the page. Send one call per distinct issue and do not report the same issue twice in a conversation. Do not use this tool to confirm that a page is accurate; it is for reporting problems only.

Input parameters:

- `content` (string, required): Explain the issue in full, as if writing to a documentation maintainer who never saw this conversation. Describe what is wrong, where on the page it appears (quote the exact sentence or section title…
- `goal` (string): The broader end goal you were ultimately trying to accomplish (as/on behalf of the user) when you hit this issue. Gives the team the context you were working towards. Optional.
- `pageUrl` (string, required): The full URL of the page the issue is about (e.g. https://docs.nalpeiron.com//getting-started), so the finding is linked to the exact page.

## Diagnostics

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

## Score history

- 2026-09-24: 79
- 2026-09-23: 79
- 2026-09-22: 78
- 2026-09-21: 78
- 2026-09-20: 77
- 2026-09-19: 77
- 2026-09-18: 76
- 2026-09-17: 76
- 2026-09-16: 75
- 2026-09-15: 75
- 2026-09-14: 74
- 2026-09-13: 74
- 2026-09-12: 73
- 2026-09-11: 73
- 2026-09-10: 72
- 2026-09-09: 72
- 2026-09-08: 72

## Common questions

### What is the Nalpeiron Docs MCP server?

Nalpeiron Docs is an MCP server listed in the public MCP registry as com.nalpeiron.docs/mcp. Search and browse Nalpeiron product documentation (Zentitle2, ZenGain, ZenMeter, EUP) via GitBook. This page covers its hosted endpoint (https://docs.nalpeiron.com/~gitbook/mcp).

### Is the Nalpeiron Docs MCP server safe to use?

Nalpeiron Docs scores 79 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 Nalpeiron Docs MCP server expose?

Nalpeiron Docs exposes 4 tools: searchDocumentation, getPage, askQuestion, sendFeedback. Their descriptions and schemas cost roughly 649 tokens of context every time the server is loaded.

### Does the Nalpeiron Docs MCP server require authentication?

No. We connected to Nalpeiron Docs without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Nalpeiron Docs MCP server still maintained?

Nalpeiron Docs is still listed as active in the MCP registry. We last reached this channel on 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://docs.nalpeiron.com/~gitbook/mcp
- Changelog RSS feed: https://verifymcp.io/servers/com-nalpeiron-docs-mcp/gitbook-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-nalpeiron-docs-mcp/gitbook-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-nalpeiron-docs-mcp/gitbook-mcp