Just Publish
REMOTE · MCP.JUSTPUBLISH.AI
Publish and update the website you built with AI at a live public URL. Sign-in required.
Available components
Last scanned (7 hours ago)
Scores higher than 28% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Cloud Infrastructure
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 Security95
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- The endpoint enforces authorisation, advertised via RFC 9728 protected-resource metadata. View diagnostics → Pass
- 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 is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
- The authorisation server supports Client ID Metadata Documents, the current MCP client-registration mechanism. View diagnostics → Pass
Transport & Reachability0
- Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http. See how to fix → View diagnostics → Unverified
Schema Quality & AI Usability0
- Schema blocked by authentication: the endpoint requires auth we don't have to read it. See how to fix → Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Tool Safety0
- Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Capabilities0
- Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. See how to fix → Unverified
Unverified: 6 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. Claim this server and supply a read-only token to verify it and lift the score.
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.
- 9 Oct 26 −50
- Endpoint reachability: reachable → behind authorisation ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → unverified ▼ security
- Authorization: partial → pass ▲ security
- First check of Authorization: pass security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: 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
- 24 Sept 26 0
- Server version: 0.1.11 → 0.1.12 functional
- 13 Sept 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “deploy” rewrote its description, which is the text the model reads security
- Tool “get_site_files” rewrote its description, which is the text the model reads security
- Tool “update_site_file” rewrote its description, which is the text the model reads security
- Server version: 0.1.10 → 0.1.11 functional
- “deploy” reworded the description of “email” cosmetic
- 11 Sept 26 0
- Server version: 0.1.8 → 0.1.10 functional
- 26 Aug 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 Aug 26 0
- Stability: 0.97 → pass security
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 · Probed https://mcp.justpublish.ai/
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=justpublish.ai | CN=WE1,O=Google Trust Services,C=US | 10 Oct 2026 | 8 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 9148f1ac740f280d134cfbf6373bd8a2 |
| SANs: justpublish.ai, mcp.justpublish.ai, *.mcp.justpublish.ai | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of mcp.justpublish.ai. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 1814, 3799 | 8, 8 | Verified |
| justpublish.ai. | present | 2371 | 13 | Verified |
| mcp.justpublish.ai. | Verified address RRset verified with the apex keys |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On connection |
| HTTP status | 401 |
WWW-Authenticate challenge Bearer error="unauthorized", resource_metadata="https://mcp.justpublish.ai/.well-known/oauth-protected-resource"
Bearer error="unauthorized", resource_metadata="https://mcp.justpublish.ai/.well-known/oauth-protected-resource"| Header | Value |
|---|---|
| www-authenticate | Bearer error="unauthorized", resource_metadata="https://mcp.justpublish.ai/.well-known/oauth-protected-resource" |
Protected resource metadata
| Document | https://mcp.justpublish.ai/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://mcp.justpublish.ai |
| Authorisation server | https://sociable-method-41.authkit.app |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.justpublish.ai/ | Auth required | 401 | |
| http (plaintext) | http://mcp.justpublish.ai/ | HTTPS enforced | 301 | https://mcp.justpublish.ai/ |
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 →
deploy ~277
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.
| Name | Type | Req | Description |
|---|---|---|---|
| edit_token | string | – | Edit token returned at create time. Required to update. |
| string | yes | Email address for the site. A link is sent to it to confirm the address; it is also used for recovery and service messages. | |
| files | array | yes | 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| created | boolean | yes | true if this call created a new site; false if it updated an existing one. |
| dashboard_url | string | yes | 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 | yes | The owner email, masked for display (e.g. 'a***@example.com'). |
| email_verified | boolean | yes | Whether the site's owner email is verified right now. False on a new site unless this address has been verified before. |
| files_uploaded | integer | yes | Number of files written in this deploy. |
| site_id | string | yes | The site's slug / id - pass back to update it later. |
| total_bytes | integer | yes | Total size of the site in bytes after this deploy. |
| url | string | yes | The live URL of the published site. |
| verify_required | boolean | yes | true when the owner still needs to verify their email (keys on !email_verified). |
No examples provided.
get_site_files ~189
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.
| Name | Type | Req | Description |
|---|---|---|---|
| edit_token | string | yes | 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 | yes | The site id returned at publish time. |
| Name | Type | Req | Description |
|---|---|---|---|
| files | array | yes | Inlined contents of the requested text files (default: all text files, capped for size). |
| manifest | array | yes | Every file on the site (always complete, regardless of which contents were inlined). |
| site_id | string | yes | The site's slug / id. |
| truncated | boolean | yes | true if some requested file contents were omitted for size - request specific paths to read them. |
| url | string | yes | The live URL of the site. |
| version | integer | yes | The site's current version - pass as expected_version to update_site_file to avoid clobbering. |
No examples provided.
update_site_file ~244
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.
| Name | Type | Req | Description |
|---|---|---|---|
| edit_token | string | yes | 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 | yes | The files to change. Only these are written; all other files on the site survive. |
| site_id | string | yes | The site id returned at publish time. |
| Name | Type | Req | Description |
|---|---|---|---|
| files_total | integer | yes | Total number of files on the site after the merge. |
| files_written | array | yes | Paths of the files written in this update. All other files were left untouched. |
| site_id | string | yes | The site's slug / id. |
| url | string | yes | The live URL of the site. |
| version | integer | yes | The site's new version after the merge. |
No examples provided.
How do I install the Just Publish MCP server?
Just Publish is a hosted endpoint at https://mcp.justpublish.ai/, 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 · mcp.justpublish.ai
claude mcp add --transport http ai-justpublish-just-publish 'https://mcp.justpublish.ai/'
What is the Just Publish MCP server?
Just Publish is an MCP server listed in the public MCP registry as ai.justpublish/just-publish. Publish and update the website you built with AI at a live public URL. Sign-in required. This page covers its hosted endpoint (https://mcp.justpublish.ai/).
Is the Just Publish MCP server safe to use?
Just Publish scores 38 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 Just Publish MCP server expose?
Just Publish exposes 3 tools: deploy, get_site_files, update_site_file. Their descriptions and schemas cost roughly 710 tokens of context every time the server is loaded.
Does the Just Publish MCP server require authentication?
Yes. Just Publish asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the Just Publish MCP server still maintained?
Just Publish 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.