io.github.reinlainer/postmd-mcp-server
REMOTE · POSTMD.TURINK.COM · 2 COMPONENTS
Publish Markdown as a shareable web page, with document graphs
Available components
Last scanned (14 hours ago)
Scores higher than 65% of remote servers
Reachable. Last reached 6 Nov 2026.
Category Documents and Files
Recent critical change
Authorization (22 Sept 2026). See the changelog before you install this server.
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 check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (postmd_update_document). See how to fix → View diagnostics → Fail
- 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 (good).Pass
- Context-footprint check failed: tool/resource definitions use about 973 tokens (~194/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 Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage93
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 80% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- 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
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
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 →
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.
- 6 Nov 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
- 20 Oct 26 0
- Stability: 0.97 → pass security
- 19 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 67. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
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 6 Nov 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 | 19 Oct 2026 | 17 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 59699d60ad44b3c33b2b6a3bf88b699e79a |
| 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. | DS published | 19718 | 13 | Verified |
| turink.com. | 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 |
| 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 ~312
Publish Markdown as a PostMD web page. No API key required — anyone can publish. Returns docCode and data.shareUrl; hand shareUrl to people. Documents have a 30-day retention period (data.retainedUntil) that extends on each read. Documents without a password can be updated or deleted by anyone; password-protected documents require the password or the owner's API key. With an API key the document belongs to that member; groupId files it into that group (key with documents:write). The returned docCode can be kept at the top of the source file in a `postmd:document` comment (format at /docs/api) so a later session finds the document.
| 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). May include graph data in an HTML comment, which the viewer draws; the format is at /docs/graph. |
| password | string | – | Readers must supply this password to see the content. |
| 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 ~67
Delete a document. Password-protected documents require the password or the owner's API key; documents without a password can be deleted by anyone.
| Name | Type | Req | Description |
|---|---|---|---|
| docCode | string | yes | – |
| password | string | – | Document password if the document has one and you are not authenticated as its owner. |
No output schema declared.
No examples provided.
postmd_get_document ~74
Get document metadata by docCode: title, fileName, hasPassword, 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 ~59
Get the stored Markdown source of a document. Public — no API key needed. Password-protected documents need `password`.
| 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 ~315
Update a document. Password-protected documents require the password or the owner's API key; documents without a password can be updated by anyone. Include `markdown` to replace the stored content; any metadata field replaces that field. clearPassword removes the password. Replacing the content requires notesOnReplace.
| Name | Type | Req | Description |
|---|---|---|---|
| clearPassword | boolean | – | true removes the password. |
| currentPassword | string | – | Current password to authenticate if the document is password-protected. |
| 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. Adding or revising a graph means sending the whole body with the graph comment in it; the format is at /docs/graph. |
| 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. |
| 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.
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'
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 as a shareable web page, with document graphs. 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 76 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 827 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 6 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 io.github.reinlainer/postmd-mcp-server server?
VerifyMCP ran 13 checks on io.github.reinlainer/postmd-mcp-server, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. 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.