← All servers

Markdown Page

warningsverified owner

markdown.page

Publish Markdown to a public URL. Browsers receive HTML; command-line tools and agents receive plain text. No account or API key required.

https://markdown.page/mcpNo authMCP 2024-11-05v0.1.0last checked 21 Oct 2026spoke MCP on 100% of 85 checks (30 days)initialize in 2655 ms

Last checked 21 Oct 2026

✓Answered the MCP handshake (MCP 2024-11-05)
✓Auth detected: No auth
✓Lists 4 tools
!1 warning
✓Spoke MCP on 85 of 85 checks (30 days)

Will my client connect?

Decided from what the probe found at the endpoint, and from what each client's own documentation says it can complete. Every row carries the day that documentation was read.

✓Claude CodeConnects

The endpoint answers an anonymous handshake, so no credential is needed.

claude mcp add --transport http markdown-page https://markdown.page/mcp

Claude Code docs · read on 2026-08-30

✓Claude (claude.ai & Desktop)Connects

The endpoint answers an anonymous handshake, so no credential is needed.

Settings → Connectors → Add custom connector, then paste https://markdown.page/mcp.

Claude (claude.ai & Desktop) docs · read on 2026-08-30

✓ChatGPTConnects

The endpoint answers an anonymous handshake, so no credential is needed.

Settings → Apps → Advanced settings → Developer mode, then create a connector pointing at https://markdown.page/mcp.

ChatGPT docs · read on 2026-08-30

✓CursorConnects

The endpoint answers an anonymous handshake, so no credential is needed.

{
  "mcpServers": {
    "markdown-page": {
      "url": "https://markdown.page/mcp"
    }
  }
}

Cursor docs · read on 2026-08-30

✓VS Code (Copilot)Connects

The endpoint answers an anonymous handshake, so no credential is needed.

{
  "servers": {
    "markdown-page": {
      "type": "http",
      "url": "https://markdown.page/mcp"
    }
  }
}

VS Code (Copilot) docs · read on 2026-08-30

How to authenticate

Checked against the endpoint by our probe on 21 Oct 2026. These are the capabilities the server advertises, not a prediction about any particular client.

Scheme	No auth
Protected-resource metadata	✕Not found Without it a client has to guess where the authorization server lives.
Anonymous access	Handshake succeeds; 4 tools listable
Credentials demanded in prose	✕publish_markdown These tools are listed anonymously and their own descriptions ask for an account or key, but no challenge is issued — so a client has nothing to act on and the refusal arrives as a tool error.

What the probe found

warningTools needing credentials are listed without a challenge

1 of the 4 tools listed anonymously say in their own descriptions that they need an account or a key (publish_markdown), but the endpoint issued no WWW-Authenticate challenge. The requirement is stated only in prose, so a call reaches the tool and comes back as a tool error instead of an authorization step.

No CORS headers for browser-based clients

A cross-origin preflight came back without Access-Control-Allow-Origin, so the endpoint is reachable from native clients only — code running in a web page is stopped by the browser before a request is ever sent.

Tools

get_featured_pricingget_featured_purchase_statuspublish_markdownvalidate_featured_purchase

Contract history

16 Sep 2026v0.1.0first recorded contract

Watch this server

Save its public contract as a baseline and manage breaking-change email alerts.

Status badge

Status for a README, from the last probe — cached an hour, so up to seven hours behind the endpoint. Links back to this page.

[![MCP status](https://mcpi.app/servers/markdown-page/badge.svg)](https://mcpi.app/servers/markdown-page)