Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

cn.com.showdoc/showdoc

REMOTE · WWW.SHOWDOC.COM.CN

ShowDoc MCP: manage docs and API docs remotely. 60+ tools, per-user token auth.

34 Trust /100

Last scanned (15 hours ago)

Scores higher than 17% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Documents and Files

Trust breakdown (7 categories)

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 Security57
Transport & Reachability100
Schema Quality & AI Usability0
  • Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
  • Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities20
  • Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail

Unverified: 4 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.

What we tested

Checks we ran (6)

  • TLS certificate
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • MCP protocol

Checks we could not complete (5)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to connect, but we couldn't read the whole tool list to see what that exposes.
  • Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
  • Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
  • Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 21 Nov 26 0
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 20 Nov 26 0
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 19 Nov 26 0
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 18 Nov 26 0
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 17 Nov 26 34

    First indexed and scored.

Diagnostics

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 21 Nov 2026 · Probed https://www.showdoc.com.cn/mcp.php

TLS valid

Negotiated TLS 1.2 with TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.showdoc.com.cn CN=YR2,O=Let's Encrypt,C=US 11 Nov 2026 9 Feb 2027 RSA 2048 SHA256-RSA 5f8edd5c746a47e8d1b19d7b92652ec91fb
SANs: *.showdoc.com.cn, showdoc.com.cn
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of www.showdoc.com.cn. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
cn. DS published 33094 8 Verified
com.cn. DS published 40552 8 Verified
showdoc.com.cn. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://www.showdoc.com.cn/mcp.php Verified 200
http (plaintext) http://www.showdoc.com.cn/mcp.php HTTPS enforced 301 https://www.showdoc.com.cn/mcp.php
MCP tools

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 →

No tool schema has been captured from this endpoint yet.

Install

How do I install the cn.com.showdoc/showdoc MCP server?

cn.com.showdoc/showdoc is a hosted endpoint at https://www.showdoc.com.cn/mcp.php, 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 · www.showdoc.com.cn

# add to Claude Code
claude mcp add --transport http cn-com-showdoc-showdoc 'https://www.showdoc.com.cn/mcp.php'
Common questions

What is the cn.com.showdoc/showdoc MCP server?

cn.com.showdoc/showdoc is an MCP server listed in the public MCP registry as cn.com.showdoc/showdoc. ShowDoc MCP: manage docs and API docs remotely. 60+ tools, per-user token auth. This page covers its hosted endpoint (https://www.showdoc.com.cn/mcp.php).

Is the cn.com.showdoc/showdoc MCP server safe to use?

cn.com.showdoc/showdoc scores 34 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.

Does the cn.com.showdoc/showdoc MCP server require authentication?

No. We connected to cn.com.showdoc/showdoc without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the cn.com.showdoc/showdoc MCP server still maintained?

cn.com.showdoc/showdoc is still listed as active in the MCP registry. We last reached this channel on 21 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 cn.com.showdoc/showdoc MCP server?

VerifyMCP ran 6 checks on cn.com.showdoc/showdoc, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 2 more. 5 items could not be completed, a gap on our side rather than a finding about cn.com.showdoc/showdoc: Authorization, Schema quality, Stability, Tool coverage and 1 more. 4 categories score 0 for that reason, because we only credit what we can confirm. 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.