Search / com.nalpeiron.docs/mcp
Search and browse Nalpeiron product documentation (Zentitle2, ZenGain, ZenMeter, EUP) via GitBook.
v1.0.0 · active · descriptor JSON · versions
protogrid{
"mcpServers": {
"docs": {
"type": "http",
"url": "https://docs.nalpeiron.com/~gitbook/mcp"
}
}
}claude mcp add --transport http docs https://docs.nalpeiron.com/~gitbook/mcp[mcp_servers.docs]
url = "https://docs.nalpeiron.com/~gitbook/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"docs": {
"type": "remote",
"url": "https://docs.nalpeiron.com/~gitbook/mcp",
"enabled": true
}
}
}{
"mcpServers": {
"docs": {
"type": "http",
"url": "https://docs.nalpeiron.com/~gitbook/mcp"
}
},
"deeplink": "cursor://anysphere.cursor-deeplink/mcp/install?name=docs&config=eyJ0eXBlIjoiaHR0cCIsInVybCI6Imh0dHBzOi8vZG9jcy5uYWxwZWlyb24uY29tL35naXRib29rL21jcCJ9"
}{
"servers": {
"docs": {
"type": "http",
"url": "https://docs.nalpeiron.com/~gitbook/mcp"
}
}
}{
"mcpServers": {
"docs": {
"httpUrl": "https://docs.nalpeiron.com/~gitbook/mcp"
}
}
}extensions:
"docs":
enabled: true
name: "docs"
type: streamable_http
uri: "https://docs.nalpeiron.com/~gitbook/mcp"
timeout: 300
protocol.modern, protocol.stateless, protocol.transport, protocol.list_ttlno remote answered a protocol handshake (not probed yet, unreachable, or local-only)auth.prm, auth.as_metadata, auth.cimdno remote uses OAuthauth.secret_in_urlno templated URLtools.descriptionsevery tool has a descriptiontools.description_lengthdescriptions are concisetools.schemasevery tool has an object input schematools.annotations4 of 4 tools declare readOnlyHint or destructiveHinttools.directory_hintsevery tool declares readOnlyHint, destructiveHint, idempotentHint and openWorldHinttools.token_costabout 1,056 tokens to load every tooltools.api_dumptools are not a one-to-one API dumpstability.changes, stability.rug_pulltool history not recorded yetdeps.known_vulns, deps.mcp_sdk_version, deps.resolvableno npm or PyPI packageNo tool definition changes recorded. A server's first observation is its baseline; later probes record what changes.
Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed. How it is computed.
+dns-namespace +reachable +uptime-96% ~updated-41d-ago -no-repository
Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed. How it is computed.
| remote | auth | reachable | uptime 30d | p50 | protocol | last ok |
|---|---|---|---|---|---|---|
https://docs.nalpeiron.com/~gitbook/mcp streamable-http | unknown | yes | 96% | 171 ms | – | 2026-10-19 |
askQuestionread-only | 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. |
getPageread-only | 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. |
searchDocumentationread-only | 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. |
sendFeedback | 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. |
Schemas: list_tools.
{
"name": "com.nalpeiron.docs/mcp",
"title": "Nalpeiron Docs",
"$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
"remotes": [
{
"url": "https://docs.nalpeiron.com/~gitbook/mcp",
"type": "streamable-http"
}
],
"version": "1.0.0",
"description": "Search and browse Nalpeiron product documentation (Zentitle2, ZenGain, ZenMeter, EUP) via GitBook."
}