publish.my
NPM · PUBLISH-MY · 2 COMPONENTS
Publish a folder as a live website at https://<id>.publish.my. Free, no account needed.
Available components
Last scanned (2 hours ago)
Scores higher than 32% of npm servers
Category Cloud Infrastructure
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 32 of 105 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 13 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability77
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 531 tokens (~132/item across 4 items; 4 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 Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 5 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: a data source with nothing on this package, evidence we could not reach, or a check we could not run. 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.
- 24 Oct 26 +10
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- Malware scan: unverified → pass ▲ security
- 23 Oct 26 55
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 5 Nov 2026 · Analysed npm/publish-my@0.1.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 105 packages
| Packages resolved | 105 |
|---|---|
| Stale | 32 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
check_activation Check site activation ~66
Check whether the user has activated a newly published site (entered their email and clicked the link). When they have, the site is live and the publish.my key is saved for future updates.
| Name | Type | Req | Description |
|---|---|---|---|
| project_id | string | – | Site to check; omit to check every site waiting for activation. |
No output schema declared.
No examples provided.
list_sites List my sites ~25
List the user's publish.my sites with their URLs, status and 30-day views.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
publish_site Publish a folder as a website ~257
Publish a local folder (with index.html at its top) as a public static website on publish.my and return its URL. Use for "publish", "deploy", "host", "put online", "share a link", and "publish again / update the site". The first publish of a folder gives a preview URL the user activates by entering their email on that page; after that, publishes go live immediately. Re-publishing a folder that is already live updates the same URL: ask the user first, then pass confirm_update: true. Framework apps (Next.js, Vite, Astro, SvelteKit, Nuxt) must be built/exported first; pass the output folder (out/, dist/, build/, .output/public).
| Name | Type | Req | Description |
|---|---|---|---|
| confirm_update | boolean | – | Set true only after the user confirmed replacing their live site. |
| new_site | boolean | – | Publish as a separate new site even if this folder was published before. |
| path | string | yes | Folder to publish; must contain index.html at its top. Absolute path preferred. |
| project_id | string | – | Update this existing publish.my site (e.g. "88vk3mqtxz"). Normally omitted: the folder's .publish-my.json is used. |
No output schema declared.
No examples provided.
reconnect_site Reconnect a live site ~95
Use when a site is already live but this machine lost its publish.my key (updates fail with 401/403 or "no key"). Emails the site owner a confirm link; once clicked, the key is saved and updates work again.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | – | Or: a published folder; its .publish-my.json gives the id. |
| project_id | string | – | The site id (the part before .publish.my). |
No output schema declared.
No examples provided.
How do I install the publish.my MCP server?
publish.my runs locally as an npm package, launched with npx -y publish-my. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · publish-my
claude mcp add my-publish-publish-my -- npx -y publish-my
What is the publish.my MCP server?
publish.my is an MCP server listed in the public MCP registry as my.publish/publish-my. Publish a folder as a live website at https://<id>.publish.my. Free, no account needed. This page covers its npm package (publish-my).
Is the publish.my MCP server safe to use?
publish.my scores 65 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 November 2026. It declares no install or post-install scripts. 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 publish.my MCP server expose?
publish.my exposes 4 tools: publish_site, check_activation, list_sites, reconnect_site. Their descriptions and schemas cost roughly 443 tokens of context every time the server is loaded.
Is the publish.my MCP server still maintained?
publish.my is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the publish.my MCP server under?
publish.my declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.