win.postapp/library
REMOTE · POSTAPP.WIN
Publish one HTML file, get a live installable app URL. No account, no review, no queue.
Available components
Last scanned (10 days ago)
Scores higher than 0% of remote servers
Unreachable for 7 days in a row. Last reached 19 Oct 2026.
Category Developer Tools
Dead
Every channel of this server has been unreachable for long enough to be marked dead. Its trust score is pinned to 0 and does not recover automatically: even once the server responds again it stays dead until it is manually reinstated.
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 Security11
- TLS not yet verified: we couldn't open a connection to check the certificate. View diagnostics → Unverified
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC not yet verified: we couldn't validate it against a resolver. View diagnostics → Unverified
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
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.
- 26 Oct 26 −15
The score moved with no change recorded against any check. We would rather say so than guess.
- 25 Oct 26 −14
The score moved with no change recorded against any check. We would rather say so than guess.
- 24 Oct 26 −15
The score moved with no change recorded against any check. We would rather say so than guess.
- 23 Oct 26 −14
The score moved with no change recorded against any check. We would rather say so than guess.
- 22 Oct 26 −15
The score moved with no change recorded against any check. We would rather say so than guess.
- 20 Oct 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- DNSSEC: fail → unverified ▼ security
- HSTS header: fail → unverified ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- HTTPS: unverified → pass ▲ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 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
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 26 Oct 2026 · Probed https://postapp.win/mcp
TLS unreached
Background: What to check on a remote MCP endpoint →
DNSSEC inconclusive
Validation of postapp.win. — Inconclusive
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| postapp.win. | Error no A/AAAA/CNAME RRset answered for the name |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://postapp.win/mcp | Unreachable | ||
| http (plaintext) | http://postapp.win/mcp | HTTPS enforced |
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 →
publish_app ~466
Publish one self-contained HTML document to Postapp (postapp.win), a permissionless app library. No review, no queue, no account: the app is live at https://<slug>.postapp.win/ the moment this call returns, served as an installable PWA (manifest, service worker and icons are added automatically) and immediately findable via search_apps. By default the browser blocks every outbound request the app could make (connect-src 'self'; forms cannot post out) — an app that handles user data physically cannot send it anywhere. Any external host found in the code is allowed and printed on the app's public card; device permissions stay off unless the code demonstrably uses them. Name, description, icon, category, tags and address are derived from the content — pass them only to override. Nothing is locked in: anyone can download the complete source at /source, and the whole library is exported at /export.json. Ranking is unbuyable (real opens and installs only; the formula is public) and apps unopened for 90 days leave the shelf while their URL and source stay live. Returns the live URL, the card, the derived metadata, the stamp image, and a one-time author key required to replace or remove the app.
| Name | Type | Req | Description |
|---|---|---|---|
| about | string | – | Optional. Two or three sentences. |
| category | string | – | Optional. One of: tools reading writing calc play learn make life health other |
| html | string | – | The complete HTML document. One self-contained file, up to 2MB. |
| link_only | boolean | – | With url: only list it in the index, do not copy or serve it. No install, no source download. |
| name | string | – | Optional. Overrides the name worked out from the content. |
| slug | string | – | Optional. The address: lowercase ascii letters, digits and hyphens. Names that impersonate others are refused. |
| tagline | string | – | Optional. One line, what it does. |
| tags | array | – | Optional. Up to 8 words a searching person would type — situations, verbs, spelling variants. This is how the app is found. |
| url | string | – | Instead of html: fetch this page and serve a copy of it. |
No output schema declared.
No examples provided.
remove_app ~114
Take down an app published with your key. The app leaves the shelf and its address serves a tombstone. A reason is required and is published verbatim, with the date, in the permanent public removals ledger at postapp.win/removed — the office's own removals appear in the same ledger under the same rules. Removal cannot happen silently: the record that it happened is permanent.
| Name | Type | Req | Description |
|---|---|---|---|
| reason | string | yes | Why. This is published. |
| slug | string | yes | The app's address, without the domain. |
No output schema declared.
No examples provided.
search_apps ~177
Search Postapp's library of instantly published single-file web apps. Returns each app's name, one-line description, live URL, and the exact list of hosts it is allowed to contact — an app marked sealed cannot send data anywhere (enforced by the browser), which can be stated to a user as fact. Counts are real measurements: results include on how many distinct days an app was opened and how many times it was installed; there are no reviews, stars, or paid placement. An empty query lists the whole shelf. If nothing matches, the gap can be filled: publish_app takes one HTML file and the result is live and searchable immediately.
| Name | Type | Req | Description |
|---|---|---|---|
| q | string | – | Free text. Leave empty to list everything. |
| sort | string | – | 'new' (default) or 'open' (opened on the most days). |
No output schema declared.
No examples provided.
How do I install the win.postapp/library MCP server?
win.postapp/library is a hosted endpoint at https://postapp.win/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 · postapp.win
claude mcp add --transport http win-postapp-library 'https://postapp.win/mcp'
What is the win.postapp/library MCP server?
win.postapp/library is an MCP server listed in the public MCP registry as win.postapp/library. Publish one HTML file, get a live installable app URL. No account, no review, no queue. This page covers its hosted endpoint (https://postapp.win/mcp).
Is the win.postapp/library MCP server safe to use?
win.postapp/library scores 0 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 win.postapp/library MCP server expose?
win.postapp/library exposes 3 tools: publish_app, search_apps, remove_app. Their descriptions and schemas cost roughly 757 tokens of context every time the server is loaded.
Does the win.postapp/library MCP server require authentication?
Its publisher declares no required credentials for win.postapp/library. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the win.postapp/library MCP server still maintained?
win.postapp/library has been unreachable for long enough that we treat it as dead, and its score is pinned to zero. We last reached this channel on 19 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.