# io.github.reinlainer/postmd-mcp-server (remote · postmd.turink.com)

Publish Markdown to PostMD and get a shareable web page

- Trust score: 61/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `postmd.turink.com`: 61/100 (this document), [markdown](https://verifymcp.io/servers/reinlainer-postmd-mcp-server/postmd.md), [page](https://verifymcp.io/servers/reinlainer-postmd-mcp-server/postmd)
- npm · `postmd-mcp-server`: 85/100, [markdown](https://verifymcp.io/servers/reinlainer-postmd-mcp-server/postmd-mcp-server.md), [page](https://verifymcp.io/servers/reinlainer-postmd-mcp-server/postmd-mcp-server)

## Channel facts

- Endpoint: `https://postmd.turink.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `2.4.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 65/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1042 tokens (~208/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 94/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 83% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "postmd_create_document" implies "publish" and declares no destructiveHint at all, which the MCP spec reads as destructive by default.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

**Unverified: 1 category.** A category scored 0 because we could not verify it: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

## Install

### How do I install the io.github.reinlainer/postmd-mcp-server server?

io.github.reinlainer/postmd-mcp-server is a hosted endpoint at https://postmd.turink.com/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.

### Claude

```bash
claude mcp add --transport http reinlainer-postmd-mcp-server 'https://postmd.turink.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "reinlainer-postmd-mcp-server": {
      "url": "https://postmd.turink.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "reinlainer-postmd-mcp-server": {
      "type": "http",
      "url": "https://postmd.turink.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.reinlainer-postmd-mcp-server]
url = "https://postmd.turink.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "reinlainer-postmd-mcp-server": {
      "type": "remote",
      "url": "https://postmd.turink.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add reinlainer-postmd-mcp-server --url 'https://postmd.turink.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  reinlainer-postmd-mcp-server:
    url: "https://postmd.turink.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "reinlainer-postmd-mcp-server": {
      "Transport": "http",
      "Url": "https://postmd.turink.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add reinlainer-postmd-mcp-server -t streamable-http -u 'https://postmd.turink.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "reinlainer-postmd-mcp-server": {
      "type": "http",
      "url": "https://postmd.turink.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-20 (score 61, +57)

- [security regression] HSTS header: unverified → fail
- [security improvement] Injection markers: unverified → pass
- [security improvement] TLS certificate: unverified → pass
- [security improvement] Transport: fail → pass
- [security] First check of Judged manipulation: pass
- [security] Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] MCP protocol: unverified → pass
- [functional] First check of Schema quality: fail
- [functional] First check of Tool coverage: 83
- [functional] First check of Schema quality: excellent
- [functional] First check of Schema quality: fail
- [functional] First check of Destructive annotations: 0

### 2026-09-15 (score 4)

First indexed and scored.

## MCP tools (5)

### `postmd_create_document` (~294 tokens)

Publish Markdown as a PostMD web page. No API key required — anyone can publish. Returns docCode and data.shareUrl; hand shareUrl to people. Without a key the document is anonymous: data.retainedUntil is when it is deleted and data.controlToken is the only way to update or delete it, shown once and never reissued — report both to the person. With an API key the document belongs to that member, has no expiry, needs no token and can collect notes; groupId files it into that group instead of the default one (key with documents:write).

Input parameters:

- `fileName` (string): Upload filename, must end in .md. Default document.md.
- `groupId` (number): File the document in this group instead of the default group (needs an API key).
- `markdown` (string, required): Full Markdown document as one UTF-8 string (the entire source, not a summary).
- `password` (string): Readers must supply this password to see the content.
- `shareEndDate` (string): yyyyMMdd. The document stops being served after this date. Omit for no end date.
- `title` (string): Shown in the viewer and link previews. Defaults to fileName without .md.
- `viewerStyle` (string): Viewer theme: readable (default), github, minimal, report, pamphlet or dark. Unknown values fall back to readable.

### `postmd_get_document` (~78 tokens)

Get document metadata by docCode: title, fileName, hasPassword, shareEndDate, viewerStyle, timestamps. Public — no API key needed. Content is not included; use postmd_get_document_raw for the Markdown source.

Input parameters:

- `docCode` (string, required): Document code, e.g. P-123-456-789.

### `postmd_get_document_raw` (~65 tokens)

Get the stored Markdown source of a document. Public — no API key needed. Password-protected documents need `password`; expired documents cannot be read.

Input parameters:

- `docCode` (string, required)
- `password` (string): Plain document password, if the document has one.

### `postmd_update_document` (~370 tokens)

Update a document. Requires an API key with documents:write for a document you own, or `controlToken` for an anonymously published one. Include `markdown` to replace the stored content; any metadata field replaces that field. clearPassword / clearShareEndDate remove the password / end date. Updating does not push back the deletion date of an anonymous document. Replacing the content requires notesOnReplace.

Input parameters:

- `clearPassword` (boolean): true removes the password.
- `clearShareEndDate` (boolean): true removes the end date, making sharing open-ended.
- `controlToken` (string): Control token from an anonymous publish answer (pmt_...). Lets you act on that one document without an API key.
- `docCode` (string, required)
- `fileName` (string): Upload filename when replacing content. Default document.md.
- `markdown` (string): Full new Markdown body as one UTF-8 string. Omit if only metadata changes.
- `notesOnReplace` (string): Required when replacing the content. Notes are located by the text they quote, so replacing the body moves or loses where they point: a note whose quote is gone loses its place in the body, and one w…
- `password` (string): Readers must supply this password to see the content.
- `shareEndDate` (string): yyyyMMdd. The document stops being served after this date. Omit for no end date.
- `title` (string)
- `viewerStyle` (string): Viewer theme: readable (default), github, minimal, report, pamphlet or dark. Unknown values fall back to readable.

### `postmd_delete_document` (~104 tokens)

Delete a document. Requires an API key with documents:write for a document you own, or `controlToken` for an anonymously published one. There is no endpoint to undo this: the document stops being served at once and its stored content is erased about a month later.

Input parameters:

- `controlToken` (string): Control token from an anonymous publish answer (pmt_...). Lets you act on that one document without an API key.
- `docCode` (string, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/reinlainer-postmd-mcp-server/postmd#diagnostics

## Score history

- 2026-09-20: 61
- 2026-09-19: 4
- 2026-09-18: 4
- 2026-09-17: 4
- 2026-09-16: 4
- 2026-09-15: 4

## Common questions

### What is the io.github.reinlainer/postmd-mcp-server server?

io.github.reinlainer/postmd-mcp-server is listed in the public MCP registry as io.github.reinlainer/postmd-mcp-server. Publish Markdown to PostMD and get a shareable web page. This page covers its hosted endpoint (https://postmd.turink.com/mcp).

### Is the io.github.reinlainer/postmd-mcp-server server safe to use?

io.github.reinlainer/postmd-mcp-server scores 61 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 io.github.reinlainer/postmd-mcp-server server expose?

io.github.reinlainer/postmd-mcp-server exposes 5 tools: postmd_create_document, postmd_get_document, postmd_get_document_raw, postmd_update_document, postmd_delete_document. Their descriptions and schemas cost roughly 911 tokens of context every time the server is loaded.

### Does the io.github.reinlainer/postmd-mcp-server server require authentication?

No. We connected to io.github.reinlainer/postmd-mcp-server without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the io.github.reinlainer/postmd-mcp-server server still maintained?

io.github.reinlainer/postmd-mcp-server is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://postmd.turink.com/mcp
- Repository: https://github.com/reinlainer/postmd-mcp-server
- Changelog RSS feed: https://verifymcp.io/servers/reinlainer-postmd-mcp-server/postmd.xml
- Changelog JSON feed: https://verifymcp.io/servers/reinlainer-postmd-mcp-server/postmd.json
- HTML version of this page: https://verifymcp.io/servers/reinlainer-postmd-mcp-server/postmd