# publish.my (npm · publish-my)

Publish a folder as a live website at https://<id>.publish.my. Free, no account needed.

- Trust score: 65/100 (medium)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `api.publish.my`: 31/100, [markdown](https://verifymcp.io/servers/my-publish-publish-my/api.md), [page](https://verifymcp.io/servers/my-publish-publish-my/api)
- npm · `publish-my`: 65/100 (this document), [markdown](https://verifymcp.io/servers/my-publish-publish-my/publish-my.md), [page](https://verifymcp.io/servers/my-publish-publish-my/publish-my)

## Channel facts

- Registry: `npm`
- Package: `publish-my`
- Version: `0.1.0`
- Transport: `stdio`

## Trust breakdown

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

Scored 2026-11-05.

- **Supply Chain Security**: 81/100
  - No malware found by supply-chain analysis.
  - CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available.
  - No install/post-install scripts declared.
  - 32 of 105 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 13 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 77/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - 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**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 5 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: 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.

## Install

### 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.

### Claude

```bash
claude mcp add my-publish-publish-my -- npx -y publish-my
```

### Cursor

```json
{
  "mcpServers": {
    "my-publish-publish-my": {
      "command": "npx",
      "args": [
        "-y",
        "publish-my"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "my-publish-publish-my": {
      "command": "npx",
      "args": [
        "-y",
        "publish-my"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add my-publish-publish-my -- npx -y publish-my
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "my-publish-publish-my": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "publish-my"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add my-publish-publish-my --command npx --arg -y --arg publish-my
```

### Hermes

```yaml
mcp_servers:
  my-publish-publish-my:
    command: "npx"
    args: ["-y", "publish-my"]
```

### Netclaw

```json
{
  "McpServers": {
    "my-publish-publish-my": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "publish-my"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add my-publish-publish-my -t stdio -c npx -a -y publish-my
```

### Other

```json
{
  "mcpServers": {
    "my-publish-publish-my": {
      "command": "npx",
      "args": [
        "-y",
        "publish-my"
      ]
    }
  }
}
```

## 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-10-24 (score 65, +10)

- [security regression] CVE-2023-54404 affects this package: high
- [security regression] Known CVEs: pass → fail
- [security improvement] Malware scan: unverified → pass

### 2026-10-23 (score 55)

First indexed and scored.

## MCP tools (4)

### `publish_site` (~257 tokens)

Publish a folder as a website

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).

Input parameters:

- `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, required): 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.

### `check_activation` (~66 tokens)

Check site activation

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.

Input parameters:

- `project_id` (string): Site to check; omit to check every site waiting for activation.

### `list_sites` (~25 tokens)

List my sites

List the user's publish.my sites with their URLs, status and 30-day views.

### `reconnect_site` (~95 tokens)

Reconnect a live site

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.

Input parameters:

- `path` (string): Or: a published folder; its .publish-my.json gives the id.
- `project_id` (string): The site id (the part before .publish.my).

## Diagnostics

Captured diagnostic sections: Provenance, Vulnerabilities, Dependencies. The full working is on the page: https://verifymcp.io/servers/my-publish-publish-my/publish-my#diagnostics

## Score history

- 2026-11-05: 65
- 2026-11-04: 65
- 2026-11-03: 65
- 2026-11-02: 65
- 2026-11-01: 65
- 2026-10-31: 65
- 2026-10-30: 65
- 2026-10-29: 65
- 2026-10-28: 65
- 2026-10-27: 65
- 2026-10-26: 65
- 2026-10-25: 65
- 2026-10-24: 65
- 2026-10-23: 55

## Common questions

### 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.

## Links

- npm package: https://www.npmjs.com/package/publish-my
- Socket report: https://socket.dev/npm/package/publish-my
- Repository: https://github.com/aizuikmal/publish-my-mcp
- Website: https://publish.my/agents/
- Changelog RSS feed: https://verifymcp.io/servers/my-publish-publish-my/publish-my.xml
- Changelog JSON feed: https://verifymcp.io/servers/my-publish-publish-my/publish-my.json
- HTML version of this page: https://verifymcp.io/servers/my-publish-publish-my/publish-my