Docsy
REMOTE · DOCSY.REMCP.SITE
Read versioned developer documentation with original source links using five public MCP tools.
Available components
Last scanned (19 hours ago)
Scores higher than 33% of remote servers
Reachable. Last reached 22 Oct 2026.
Category Code Search and Documentation
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 Security94
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- The endpoint enforces authorisation, advertised via RFC 9728 protected-resource metadata. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability0
- Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http. See how to fix → View diagnostics → Unverified
Schema Quality & AI Usability0
- Schema blocked by authentication: the endpoint requires auth we don't have to read it. See how to fix → Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Tool Safety0
- Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Capabilities0
- Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. See how to fix → Unverified
Unverified: 6 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm. Claim this server and supply a read-only token to verify it and lift the score.
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.
- 20 Oct 26 −35
- Endpoint reachability: reachable → behind authorisation ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → unverified ▼ security
- Stability: 0.17 → unverified ▼ security
- Authorization: partial → pass ▲ security
- First check of Authorization: partial security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 19 Oct 26 +1
- Tool “fetch” rewrote its description, which is the text the model reads security
- Tool “query-docs” rewrote its description, which is the text the model reads security
- Schema quality: 100 → 120 ▼ functional
- “fetch” added an optional parameter “libraryId” cosmetic
- “fetch” added an optional parameter “url” cosmetic
- “query-docs” added an optional parameter “response” cosmetic
- “query-docs” reworded the description of “limit” cosmetic
- “fetch” made “id” optional cosmetic
- 18 Oct 26 −1
- Tool “list-library-versions” rewrote its description, which is the text the model reads security
- Schema quality: 90 → 100 ▼ functional
- Tool coverage: 63% → 45% ▼ functional
- “list-library-versions” added an optional parameter “includePrerelease” cosmetic
- “list-library-versions” added an optional parameter “limit” cosmetic
- “list-library-versions” added an optional parameter “offset” cosmetic
- 17 Oct 26 +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.
- 15 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 14 Oct 26 71
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 22 Oct 2026 · Probed https://docsy.remcp.site/mcp/registry
TLS valid
Negotiated TLS 1.2 with TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=remcp.site | CN=YE2,O=Let's Encrypt,C=US | 17 Sept 2026 | 16 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 6478eb02b3dea6e625e24a47c3b89adc732 |
| SANs: *.remcp.site, remcp.site | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of docsy.remcp.site. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| site. | present | 31826 | 13 | Verified |
| remcp.site. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On connection |
| HTTP status | 401 |
WWW-Authenticate challenge Bearer realm="Docsy", resource_metadata="https://docsy.remcp.site/.well-known/oauth-protected-resource/mcp", scope="docsy:read", error="invalid_token", error_description="Connect your Docsy account to access documentation"
Bearer realm="Docsy", resource_metadata="https://docsy.remcp.site/.well-known/oauth-protected-resource/mcp", scope="docsy:read", error="invalid_token", error_description="Connect your Docsy account to access documentation"| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| content-security-policy | frame-ancestors 'self' |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
| www-authenticate | Bearer realm="Docsy", resource_metadata="https://docsy.remcp.site/.well-known/oauth-protected-resource/mcp", scope="docsy:read", error="invalid_token", error_description="Connect your Docsy account to access documentation" |
Protected resource metadata
| Document | https://docsy.remcp.site/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://docsy.remcp.site/mcp |
| Authorisation server | https://docsy.remcp.site |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://docsy.remcp.site/mcp/registry | Auth required | 401 | |
| http (plaintext) | http://docsy.remcp.site/mcp/registry | HTTPS enforced | 301 | https://docsy.remcp.site/mcp/registry |
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 →
fetch Fetch Documentation Chunk ~75
Fetch one indexed search result by stable ID, or fetch a verified publisher page via libraryId + url previously obtained from link-only query-docs. The URL must belong to the exact authorized source and version; no arbitrary web fetching.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | – | – |
| libraryId | string | – | – |
| url | string | – | – |
No output schema declared.
No examples provided.
list-library-versions List Library Versions ~85
Default: representative version preview. Supply limit/offset to paginate individual stable GitHub release tags, including patch versions absent from the preview. Indexed docs and upstream tags are distinguished. Upstream tags may have no usable documentation.
| Name | Type | Req | Description |
|---|---|---|---|
| includePrerelease | boolean | – | – |
| libraryId | string | yes | – |
| limit | integer | – | – |
| offset | integer | – | – |
No output schema declared.
No examples provided.
query-docs Query Documentation ~183
Retrieve current, version-aware documentation and code examples from one Docsy library, or request source links only (response: links) without loading or indexing document bodies. Resolve the library ID first unless the exact ID is known. Keep each query to one concept and do not call this tool more than 3 times per question.
| Name | Type | Req | Description |
|---|---|---|---|
| libraryId | string | yes | Exact Docsy library ID such as /org/project or /org/project/version. |
| limit | integer | – | Maximum results to return (snippets or links); omit to use the production default. |
| query | string | yes | Specific documentation concept to retrieve. Use one topic per query and never include secrets, credentials, PII, proprietary code, or confidential data. |
| response | string | – | Choose links to search existing publisher/version metadata without loading, parsing, embedding or saving documentation page contents. Defaults to snippets. |
No output schema declared.
No examples provided.
resolve-library-id Resolve Docsy Library ID ~131
Resolve a package or product name to a Docsy library ID. Call before query-docs unless an exact /org/project or /org/project/version ID is already known. The query is used only to rank likely libraries; do not include credentials, PII, proprietary code, or other confidential data.
| Name | Type | Req | Description |
|---|---|---|---|
| libraryName | string | yes | Official library, framework, SDK, API, CLI, or product name to resolve. |
| query | string | yes | What documentation you need so Docsy can rank matching libraries. Keep it focused and never include secrets, credentials, PII, proprietary code, or confidential data. |
No output schema declared.
No examples provided.
search Search Documentation ~27
Search all public indexed documentation and return stable IDs and absolute URLs.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | – |
No output schema declared.
No examples provided.
How do I install the Docsy MCP server?
Docsy is a hosted endpoint at https://docsy.remcp.site/mcp/registry, 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 · docsy.remcp.site
claude mcp add --transport http getremcp-docsy 'https://docsy.remcp.site/mcp/registry'
What is the Docsy MCP server?
Docsy is an MCP server listed in the public MCP registry as io.github.getremcp/docsy. Read versioned developer documentation with original source links using five public MCP tools. This page covers its hosted endpoint (https://docsy.remcp.site/mcp/registry).
Is the Docsy MCP server safe to use?
Docsy scores 38 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 Docsy MCP server expose?
Docsy exposes 5 tools: resolve-library-id, query-docs, list-library-versions, search, fetch. Their descriptions and schemas cost roughly 501 tokens of context every time the server is loaded.
Does the Docsy MCP server require authentication?
Yes. Docsy asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the Docsy MCP server still maintained?
Docsy is still listed as active in the MCP registry. We last reached this channel on 22 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.