io.github.reinlainer/postmd-mcp-server
REMOTE · POSTMD.TURINK.COM · 2 COMPONENTS · SCANNED SEP 20
Publish Markdown to PostMD and get a shareable web page
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 Security57
- 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 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. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 Usability65
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage94
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 83% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 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. See how to fix → Fail
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
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.
remote · postmd.turink.com
claude mcp add --transport http reinlainer-postmd-mcp-server 'https://postmd.turink.com/mcp'
{
"mcpServers": {
"reinlainer-postmd-mcp-server": {
"url": "https://postmd.turink.com/mcp"
}
}
} {
"servers": {
"reinlainer-postmd-mcp-server": {
"type": "http",
"url": "https://postmd.turink.com/mcp"
}
}
} [mcp_servers.reinlainer-postmd-mcp-server] url = "https://postmd.turink.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"reinlainer-postmd-mcp-server": {
"type": "remote",
"url": "https://postmd.turink.com/mcp",
"enabled": true
}
}
} openclaw mcp add reinlainer-postmd-mcp-server --url 'https://postmd.turink.com/mcp' --transport streamable-http
mcp_servers:
reinlainer-postmd-mcp-server:
url: "https://postmd.turink.com/mcp" {
"McpServers": {
"reinlainer-postmd-mcp-server": {
"Transport": "http",
"Url": "https://postmd.turink.com/mcp"
}
}
} assistant mcp add reinlainer-postmd-mcp-server -t streamable-http -u 'https://postmd.turink.com/mcp'
{
"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.
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 Sept 26 +57
- HSTS header: unverified → fail ▼ security
- Injection markers: unverified → pass ▲ security
- TLS certificate: unverified → pass ▲ security
- 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. security
- Tool coverage: unverified → 100 ▲ functional
- 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 functional
- 15 Sept 26 4
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 20 Sept 2026 · Probed https://postmd.turink.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=postmd.turink.com | CN=YE2,O=Let's Encrypt,C=US | 20 Aug 2026 | 18 Nov 2026 | ECDSA 256 | ECDSA-SHA384 | 676e23d9420dddf34518a9531d254e381b3 |
| SANs: postmd.turink.com | ||||||
| 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 postmd.turink.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| turink.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 |
|---|---|
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://postmd.turink.com/mcp | Verified | 200 | |
| http (plaintext) | http://postmd.turink.com/mcp | HTTPS enforced | 301 | https://postmd.turink.com/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 →
postmd_create_document ~294
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).
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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. |
No output schema declared.
No examples provided.
postmd_delete_document ~104
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.
| Name | Type | Req | Description |
|---|---|---|---|
| controlToken | string | – | Control token from an anonymous publish answer (pmt_...). Lets you act on that one document without an API key. |
| docCode | string | yes | – |
No output schema declared.
No examples provided.
postmd_get_document ~78
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.
| Name | Type | Req | Description |
|---|---|---|---|
| docCode | string | yes | Document code, e.g. P-123-456-789. |
No output schema declared.
No examples provided.
postmd_get_document_raw ~65
Get the stored Markdown source of a document. Public — no API key needed. Password-protected documents need `password`; expired documents cannot be read.
| Name | Type | Req | Description |
|---|---|---|---|
| docCode | string | yes | – |
| password | string | – | Plain document password, if the document has one. |
No output schema declared.
No examples provided.
postmd_update_document ~370
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | – |
| 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. |
No output schema declared.
No examples provided.
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.