# Just Publish (remote · mcp.justpublish.ai)

Publish the website you built with AI to a live public URL — straight from chat, no setup.

- Trust score: 77/100 (medium)
- Change this week: +6
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `mcp.justpublish.ai`: 77/100 (this document), [markdown](https://verifymcp.io/servers/ai-justpublish-just-publish/mcp.md), [page](https://verifymcp.io/servers/ai-justpublish-just-publish/mcp)

## Channel facts

- Endpoint: `https://mcp.justpublish.ai/`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.4`

## Trust breakdown

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

Scored 2026-08-03.

- **Endpoint Security**: 77/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 86/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 983 tokens (~122/item across 8 items; 3 tools + 5 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **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.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.
  - Supports UI / widget rendering.

## Install

### Claude

```bash
claude mcp add --transport http ai-justpublish-just-publish https://mcp.justpublish.ai/
```

### Codex

```toml
[mcp_servers.ai-justpublish-just-publish]
url = "https://mcp.justpublish.ai/"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ai-justpublish-just-publish": {
      "type": "remote",
      "url": "https://mcp.justpublish.ai/",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ai-justpublish-just-publish --url https://mcp.justpublish.ai/ --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ai-justpublish-just-publish:
    url: "https://mcp.justpublish.ai/"
```

### Other

```json
{
  "mcpServers": {
    "ai-justpublish-just-publish": {
      "type": "http",
      "url": "https://mcp.justpublish.ai/"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## 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-08-03 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 76, +3)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-28 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 71, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 71)

First indexed and scored.

## MCP tools (3)

### `deploy` (~275 tokens)

Put a website live at a public URL. Use this when the user wants to publish, launch, or get a page online — e.g. 'I need a website', 'put up a page for my business', 'make this live'. Takes static files (HTML, CSS, JS, images) and returns a working URL anyone can open. No build step, no config. First call: omit site_id and edit_token — you get back a url, a site_id, and an edit_token. Keep the edit_token; it's the only way to change this site later. Later calls: pass site_id + edit_token to publish over the same site. deploy REPLACES the whole site — any file you leave out is DELETED. To change just one or a few files, use update_site_file instead. To see what's currently live before editing, use get_site_files first.

Input parameters:

- `edit_token` (string): Edit token returned at create time. Required to update.
- `email` (string, required): Email to associate with the site. Captured unverified at first deploy; verification only required later for custom domains and recovery.
- `files` (array, required): Files to publish. Must include an index.html at the root.
- `site_id` (string): Existing site id to update. Omit to create a new site.

Output parameters:

- `created` (boolean): true if this call created a new site; false if it updated an existing one.
- `dashboard_url` (string): Deep link to this site in the owner's dashboard.
- `edit_token` (string): Returned ONLY on first create. Save it — it's the only way to update this site.
- `email_masked` (string): The owner email, masked for display (e.g. 'a***@example.com').
- `email_verified` (boolean): Whether the site's owner email is verified right now. New sites are always false.
- `files_uploaded` (integer): Number of files written in this deploy.
- `site_id` (string): The site's slug / id — pass back to update it later.
- `total_bytes` (integer): Total size of the site in bytes after this deploy.
- `url` (string): The live URL of the published site.
- `verify_required` (boolean): true when the owner still needs to verify their email (keys on !email_verified).

### `get_site_files` (~189 tokens)

Read the files of a site you already published, so you can make a targeted edit instead of rebuilding the whole site from memory. Returns a complete manifest (every file's path, size, content-type, sha256) plus the contents of the text files (HTML/CSS/JS/etc). Also returns the site's current `version` — pass it back to update_site_file so you don't overwrite a newer change. Pass `paths` to fetch only specific files; omit it to get all text files. Requires site_id + edit_token.

Input parameters:

- `edit_token` (string, required): The edit token returned at publish time.
- `paths` (array): Optional. Specific file paths to return contents for (e.g. ['index.html','style.css']). Omit to get all text files. The manifest always lists every file regardless.
- `site_id` (string, required): The site id returned at publish time.

Output parameters:

- `files` (array): Inlined contents of the requested text files (default: all text files, capped for size).
- `manifest` (array): Every file on the site (always complete, regardless of which contents were inlined).
- `site_id` (string): The site's slug / id.
- `truncated` (boolean): true if some requested file contents were omitted for size — request specific paths to read them.
- `url` (string): The live URL of the site.
- `version` (integer): The site's current version — pass as expected_version to update_site_file to avoid clobbering.

### `update_site_file` (~244 tokens)

Change one or a few files of an already-published site, leaving every other file untouched (a merge — unlike deploy, which replaces the whole site). Ideal for small edits: fix a typo in index.html, swap a stylesheet, add one page. Best practice: call get_site_files first, edit the returned content, then call this with the files you changed and the `expected_version` from that read — if the site changed in the meantime you get a clear conflict telling you to re-read. Requires site_id + edit_token. Cannot delete files (use deploy to drop a file) and cannot remove index.html.

Input parameters:

- `edit_token` (string, required): The edit token returned at publish time.
- `expected_version` (integer): Optional but recommended. The `version` you got from get_site_files. If the site has changed since, the update is rejected with a conflict so you can re-read and re-apply. Omit to force last-writer-w…
- `files` (array, required): The files to change. Only these are written; all other files on the site survive.
- `site_id` (string, required): The site id returned at publish time.

Output parameters:

- `files_total` (integer): Total number of files on the site after the merge.
- `files_written` (array): Paths of the files written in this update. All other files were left untouched.
- `site_id` (string): The site's slug / id.
- `url` (string): The live URL of the site.
- `version` (integer): The site's new version after the merge.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/ai-justpublish-just-publish/mcp#diagnostics

## Score history

- 2026-08-03: 77
- 2026-08-02: 76
- 2026-08-01: 76
- 2026-07-31: 76
- 2026-07-30: 73
- 2026-07-29: 73
- 2026-07-28: 72
- 2026-07-27: 71
- 2026-07-26: 71

## Links

- Remote endpoint: https://mcp.justpublish.ai/
- Repository: https://github.com/just-done/just-publish-mcp
- Website: https://justpublish.ai/
- Changelog RSS feed: https://verifymcp.io/servers/ai-justpublish-just-publish/mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/ai-justpublish-just-publish/mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/ai-justpublish-just-publish/mcp