Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Just Publish

REMOTE · MCP.JUSTPUBLISH.AI · SCANNED SEP 20

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

Available components

remote · mcp.justpublish.ai 88
0 this week 88 Trust /100
Trust breakdown (7 categories)

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 Security77
Transport & Reachability100
Schema Quality & AI Usability85
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 999 tokens (~124/item across 8 items; 3 tools + 5 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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
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
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.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
  • Supports UI / widget rendering.Pass
Install

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

# add to Claude Code
claude mcp add --transport http ai-justpublish-just-publish 'https://mcp.justpublish.ai/'
// .cursor/mcp.json
{
  "mcpServers": {
    "ai-justpublish-just-publish": {
      "url": "https://mcp.justpublish.ai/"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "ai-justpublish-just-publish": {
      "type": "http",
      "url": "https://mcp.justpublish.ai/"
    }
  }
}
# ~/.codex/config.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
    }
  }
}
# add to OpenClaw
openclaw mcp add ai-justpublish-just-publish --url 'https://mcp.justpublish.ai/' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  ai-justpublish-just-publish:
    url: "https://mcp.justpublish.ai/"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "ai-justpublish-just-publish": {
      "Transport": "http",
      "Url": "https://mcp.justpublish.ai/"
    }
  }
}
# add to Vellum
assistant mcp add ai-justpublish-just-publish -t streamable-http -u 'https://mcp.justpublish.ai/'
// mcp.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 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.

  • 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
  • 24 Aug 26 +1

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

  • 13 Aug 26 0
    • Server version: 0.1.7 → 0.1.8 functional
  • 11 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
  • 10 Aug 26 0
    • Server version: 0.1.5 → 0.1.7 functional
Diagnostics

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 20 Sept 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 12 Aug 2026 10 Nov 2026 ECDSA 256 ECDSA-SHA256 8bda3b28eee5c43c0e5977b7d8152c14
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 3799 8 Verified
justpublish.ai. present 2371 13 Verified
mcp.justpublish.ai. Verified address RRset verified with the apex keys
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

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/ Verified 200
http (plaintext) http://mcp.justpublish.ai/ HTTPS enforced 301 https://mcp.justpublish.ai/
MCP tools · 3 exposed · ~710 tokens

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 →

Tool Tokens
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.

NameTypeReqDescription
edit_tokenstring–Edit token returned at create time. Required to update.
emailstringyesEmail address for the site. A link is sent to it to confirm the address; it is also used for recovery and service messages.
filesarrayyesFiles to publish. Must include an index.html at the root.
site_idstring–Existing site id to update. Omit to create a new site.
NameTypeReqDescription
createdbooleanyestrue if this call created a new site; false if it updated an existing one.
dashboard_urlstringyesDeep link to this site in the owner's dashboard.
edit_tokenstring–Returned ONLY on first create. Save it - it's the only way to update this site.
email_maskedstringyesThe owner email, masked for display (e.g. 'a***@example.com').
email_verifiedbooleanyesWhether the site's owner email is verified right now. False on a new site unless this address has been verified before.
files_uploadedintegeryesNumber of files written in this deploy.
site_idstringyesThe site's slug / id - pass back to update it later.
total_bytesintegeryesTotal size of the site in bytes after this deploy.
urlstringyesThe live URL of the published site.
verify_requiredbooleanyestrue 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.

NameTypeReqDescription
edit_tokenstringyesThe edit token returned at publish time.
pathsarray–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_idstringyesThe site id returned at publish time.
NameTypeReqDescription
filesarrayyesInlined contents of the requested text files (default: all text files, capped for size).
manifestarrayyesEvery file on the site (always complete, regardless of which contents were inlined).
site_idstringyesThe site's slug / id.
truncatedbooleanyestrue if some requested file contents were omitted for size - request specific paths to read them.
urlstringyesThe live URL of the site.
versionintegeryesThe 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.

NameTypeReqDescription
edit_tokenstringyesThe edit token returned at publish time.
expected_versioninteger–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…
filesarrayyesThe files to change. Only these are written; all other files on the site survive.
site_idstringyesThe site id returned at publish time.
NameTypeReqDescription
files_totalintegeryesTotal number of files on the site after the merge.
files_writtenarrayyesPaths of the files written in this update. All other files were left untouched.
site_idstringyesThe site's slug / id.
urlstringyesThe live URL of the site.
versionintegeryesThe site's new version after the merge.

No examples provided.

Common questions

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 the website you built with AI to a live public URL, straight from chat, no setup. This page covers its hosted endpoint (https://mcp.justpublish.ai/).

Is the Just Publish MCP server safe to use?

Just Publish scores 88 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?

No. We connected to Just Publish without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

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 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.