Just Publish
REMOTE · MCP.JUSTPUBLISH.AI · SCANNED AUG 3
Publish the website you built with AI to a live public URL — straight from chat, no setup.
Available components
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 →
Endpoint Security77
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- 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
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability86
- 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 983 tokens (~122/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 Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
- Supports UI / widget rendering.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · mcp.justpublish.ai
claude mcp add --transport http ai-justpublish-just-publish https://mcp.justpublish.ai/
[mcp_servers.ai-justpublish-just-publish] url = "https://mcp.justpublish.ai/"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ai-justpublish-just-publish": {
"type": "remote",
"url": "https://mcp.justpublish.ai/",
"enabled": true
}
}
} openclaw mcp add ai-justpublish-just-publish --url https://mcp.justpublish.ai/ --transport streamable-http
mcp_servers:
ai-justpublish-just-publish:
url: "https://mcp.justpublish.ai/" {
"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.
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.
- 3 Aug 26 +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.
- 31 Jul 26 +3
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 29 Jul 26 +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.
- 28 Jul 26 +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.
- 27 Jul 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
- 26 Jul 26 71
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 3 Aug 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 | 14 Jun 2026 | 12 Sept 2026 | ECDSA 256 | ECDSA-SHA256 | 184cd8656b2e642113fcc7cf7b32e6dd |
| 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 |
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 |
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/ |
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.
deploy ~275
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 to associate with the site. Captured unverified at first deploy; verification only required later for custom domains and recovery. | |
| 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. New sites are always false. |
| 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.