Docs MD — Markdown Share
REMOTE · DOCS-MD.COM · SCANNED OCT 3
Share markdown as public links from your AI assistant — expiring or permanent, no API key.
Available components
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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- 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
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability82
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 210 tokens (~70/item across 3 items; 3 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "delete_share" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the Docs MD — Markdown Share MCP server?
Docs MD — Markdown Share is a hosted endpoint at https://docs-md.com/api/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.
remote · docs-md.com
claude mcp add --transport http com-docs-md-markdown-share 'https://docs-md.com/api/mcp'
{
"mcpServers": {
"com-docs-md-markdown-share": {
"url": "https://docs-md.com/api/mcp"
}
}
} {
"servers": {
"com-docs-md-markdown-share": {
"type": "http",
"url": "https://docs-md.com/api/mcp"
}
}
} [mcp_servers.com-docs-md-markdown-share] url = "https://docs-md.com/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-docs-md-markdown-share": {
"type": "remote",
"url": "https://docs-md.com/api/mcp",
"enabled": true
}
}
} openclaw mcp add com-docs-md-markdown-share --url 'https://docs-md.com/api/mcp' --transport streamable-http
mcp_servers:
com-docs-md-markdown-share:
url: "https://docs-md.com/api/mcp" {
"McpServers": {
"com-docs-md-markdown-share": {
"Transport": "http",
"Url": "https://docs-md.com/api/mcp"
}
}
} assistant mcp add com-docs-md-markdown-share -t streamable-http -u 'https://docs-md.com/api/mcp'
{
"mcpServers": {
"com-docs-md-markdown-share": {
"type": "http",
"url": "https://docs-md.com/api/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 11 Sept 26 +1
- Stability: 0.97 → pass security
- 9 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 13 Aug 26 0
- Stability: unverified → 0.03 ▲ functional
- 12 Aug 26 0
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 3 Oct 2026 · Probed https://docs-md.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.docs-md.com | CN=YR2,O=Let's Encrypt,C=US | 30 Aug 2026 | 28 Nov 2026 | RSA 2048 | SHA256-RSA | 6dc7fd9b639f9d74d4063cc1c0e65012447 |
| SANs: *.docs-md.com, docs-md.com | ||||||
| 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 docs-md.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| docs-md.com. | absent | 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' https://va.vercel-scripts.com https://*.googletagmanager.com; style-src 'self' 'unsafe-inline'; img-src 'self' data: blob: https:; font-src 'self' data:; connect-src 'self' https://vitals.vercel-insights.com https://*.vercel-insights.com https://*.google-analytics.com https://*.analytics.google.com https://*.googletagmanager.com; object-src 'none'; base-uri 'self'; frame-ancestors 'none'; form-action 'self' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://docs-md.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://docs-md.com/api/mcp | HTTPS enforced | 308 | https://docs-md.com/api/mcp |
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 →
delete_share Delete Shared Markdown ~51
Permanently delete a share using its id and edit token.
| Name | Type | Req | Description |
|---|---|---|---|
| edit_token | string | yes | Edit token returned when the share was created |
| id | string | yes | The share id (the URL path segment) |
No output schema declared.
No examples provided.
share_markdown Share Markdown ~85
Share a markdown file and get a public URL. Returns an edit token that can be used later to update or delete the share.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | The markdown content to share |
| expiry | string | – | How long the link stays live (default 30d; "never" keeps it forever) |
| filename | string | – | Optional filename for the markdown file |
No output schema declared.
No examples provided.
update_share Update Shared Markdown ~74
Replace the content of an existing share using its id and edit token.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | The new markdown content |
| edit_token | string | yes | Edit token returned when the share was created |
| filename | string | – | Optional new filename |
| id | string | yes | The share id (the URL path segment) |
No output schema declared.
No examples provided.
What is the Docs MD — Markdown Share MCP server?
Docs MD — Markdown Share is an MCP server listed in the public MCP registry as com.docs-md/markdown-share. Share markdown as public links from your AI assistant, expiring or permanent, no API key. This page covers its hosted endpoint (https://docs-md.com/api/mcp).
Is the Docs MD — Markdown Share MCP server safe to use?
Docs MD — Markdown Share 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 Docs MD — Markdown Share MCP server expose?
Docs MD — Markdown Share exposes 3 tools: share_markdown, update_share, delete_share. Their descriptions and schemas cost roughly 210 tokens of context every time the server is loaded.
Does the Docs MD — Markdown Share MCP server require authentication?
No. We connected to Docs MD — Markdown Share without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Docs MD — Markdown Share MCP server still maintained?
Docs MD — Markdown Share is still listed as active in the MCP registry. We last reached this channel on 3 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.