Nalpeiron Docs

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

Should I use this

Quality & Safety

A
Description quality
100%
Schema completeness
95%
Naming quality
95%
Poisoning risk
80%
Permission match
100%
Protocol compliance
100%

Findings (2)

  • HIGHTool poisoning patterns detected
  • LOWTool description contains negative instruction about its own usein sendFeedback

Based on automated analysis of tool definitions and protocol compliance.

Context Cost

~971Tokens (tool definitions)
~1.4 KBTypical response size
Moderate attention impact (0.76% of 128k context)

This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.

Install

One-Click Install

Add this to your `claude_desktop_config.json` file:

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

Remote endpoints

https://docs.nalpeiron.com/~gitbook/mcpstreamable-http

What it can do

Tool inventory

Tools (4)

🟢 Read-only🟡 Write🔴 Delete⚪ Unknown
🟢searchDocumentation(query)

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 Schema

{
  "type": "object",
  "properties": {
    "query": {
      "type": "string"
    }
  },
  "required": [
    "query"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟢getPage(url)

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 Schema

{
  "type": "object",
  "properties": {
    "url": {
      "type": "string",
      "description": "The URL of the page to fetch"
    }
  },
  "required": [
    "url"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟢askQuestion(question, goal)

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 Schema

{
  "type": "object",
  "properties": {
    "question": {
      "type": "string",
      "description": "The natural-language question to answer about Nalpeiron Documentation."
    },
    "goal": {
      "type": "string",
      "description": "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."
    }
  },
  "required": [
    "question"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟡sendFeedback(content, pageUrl, goal)

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 Schema

{
  "type": "object",
  "properties": {
    "content": {
      "type": "string",
      "minLength": 1,
      "maxLength": 2048,
      "description": "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 when possible), what the user was trying to do, and, when relevant, what the correct or expected information should be. Write a few clear, specific sentences in English. Never include personal or confidential information from the conversation. Up to 2048 characters."
    },
    "pageUrl": {
      "type": "string",
      "description": "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."
    },
    "goal": {
      "type": "string",
      "maxLength": 1024,
      "description": "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."
    }
  },
  "required": [
    "content",
    "pageUrl"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

Community

Rate this Server

Evidence

Recent observations

verifiedversion not recorded4 tools
verifiedversion not recorded4 tools