PubSpace
REMOTE · PUBSPACE.AI
Publish HTML or markdown from your agent as a shareable link, with password or work-email walls.
Available components
Last scanned (11 hours ago)
Scores higher than 52% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Documents and Files
Recent critical change
Authorization (27 Oct 2026). See the changelog before you install this server.
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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (update_page). See how to fix → View diagnostics → Fail
- 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 check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability68
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1886 tokens (~235/item across 8 items; 8 tools + 0 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 Management30
- Stability observed for 9 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 1477 → 1886 ▼ functional
- Server version: 0.24.3 → 0.25.1 functional
- New tool “create_account” functional
- New tool “verify_email” functional
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 27 Oct 26 +28
- Authorization: Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (update_page). critical
- Transport: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- MCP protocol: unverified → fail ▼ functional
- Tool coverage: unverified → 100 ▲ functional
- First check of Schema quality: fail functional
- First check of Schema quality: excellent functional
- First check of Schema quality: fail functional
- First check of Destructive annotations: 100 functional
- First check of Tool coverage: 100 functional
- 26 Oct 26 33
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 5 Nov 2026 · Probed https://pubspace.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=pubspace.ai | CN=YE1,O=Let's Encrypt,C=US | 7 Sept 2026 | 6 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 6762e4f7d3b03b34e5c83000ebbb0241db7 |
| SANs: pubspace.ai | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of pubspace.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | DS published | 1814, 3799 | 8, 8 | Verified |
| pubspace.ai. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
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://pubspace.ai/mcp | Verified | 200 | |
| http (plaintext) | http://pubspace.ai/mcp | HTTPS enforced | 301 | https://pubspace.ai/mcp |
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 →
create_account Create a PubSpace account for your human ~263
Sign your human up for a free PubSpace space (no card) without leaving this session. Callable without an API key. Only call it after the human has told you their email and chosen a space name; never invent or guess either. Their pages will live at <subdomain>.pubspace.ai, so treat the name as permanent (renames are limited). A 6-digit verification code is emailed to them: ask them to read it to you, then call verify_email. Once verified, publish_page works in this same session. Returns { subdomain, email, apiKey, verificationRequired, connectHint }; persist the key with the connectHint command so future sessions start connected. Fails with email_taken (they already have an account: have them sign in and copy their key from Settings → Connect your agent), subdomain_taken, invalid_subdomain, invalid_email or rate_limited. If this session is already connected with a key, it fails with already_connected.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | The human's real email address, as they gave it to you. The verification code goes here. | |
| subdomain | string | yes | The space name the human chose: lowercase letters, numbers and hyphens. Becomes <subdomain>.pubspace.ai. |
No output schema declared.
No examples provided.
delete_page Delete a page ~144
Delete a page: its URL stops working at once. The maker gets only a brief undo in the dashboard, then it is purged for good (there is no restore tool). Only use it when the human asked for deletion; to hide a page reversibly, use unpublish_page instead. Returns { ok, id, deleted }; fails with page_not_found if the id is not in this space or is already deleted.
| Name | Type | Req | Description |
|---|---|---|---|
| page_id | string | yes | The page id: the `id` field from publish_page or list_pages (also the last path segment of the page URL, …/docs/<page_id>). Only pages in the connected maker's space are visible. |
No output schema declared.
No examples provided.
get_page Get one page ~199
Fetch one page by id: metadata always ({ id, title, url, project, views, live, workEmailGated, hasDraft, createdAt, updatedAt, visibility }), plus the stored HTML when include_html is true. Read-only. Use it to read a page before editing it with update_page; use list_pages to find ids or browse. Fails with page_not_found if the id is not in this space or the page was deleted.
| Name | Type | Req | Description |
|---|---|---|---|
| include_html | boolean | – | Default false. true adds `html`: the document exactly as stored (the source you or the maker published, before serve-time injections). Can be large; only ask for it when you need the content. |
| page_id | string | yes | The page id: the `id` field from publish_page or list_pages (also the last path segment of the page URL, …/docs/<page_id>). Only pages in the connected maker's space are visible. |
No output schema declared.
No examples provided.
list_pages List pages ~148
List every page in the maker's space, newest first, with no paging: { total, pages: [{ id, title, url, project, views, live, workEmailGated, hasDraft, createdAt, updatedAt }] }. Read-only. Use it to find a page_id before update_page / get_page / unpublish_page / delete_page, or to reuse an existing project name. Offline pages are included (live: false); deleted pages are not. Pass q to search instead of scanning the full list; use get_page when you need one page's HTML.
| Name | Type | Req | Description |
|---|---|---|---|
| q | string | – | Optional case-insensitive search over page titles and content. Omit to list everything. |
No output schema declared.
No examples provided.
publish_page Publish a new page ~285
Publish a new HTML (or Markdown) page to the maker's PubSpace space and get back a live, shareable URL to hand to the human. Pages are unlisted by default — indexed by search engines only if the maker turns that on later (Pro); anyone with the link can view. Use this only for a brand-new page; to change a page that already exists, call update_page so its URL stays the same (find the id with list_pages). Each call creates a page that counts toward the plan's live-page cap; at the cap the call fails with doc_limit_reached and, on the free plan, an upgrade link to relay to the human. Returns { url, id, mode, visibility, dashboardUrl }.
| Name | Type | Req | Description |
|---|---|---|---|
| html | string | yes | Full HTML document (or Markdown when source_type is "markdown"). Served byte-faithful apart from documented meta/bar injections. |
| project | string | – | Optional: which body of work this page belongs to (e.g. "Q3 board pack"). Groups pages in the maker's library — reuse their existing project names from list_pages when one fits. (Renamed from `produc… |
| source_type | string | – | Default "html". |
| title | string | – | Optional title (used in the dashboard and social cards). |
No output schema declared.
No examples provided.
unpublish_page Take a page offline or back online ~169
Take a page offline without deleting it: its URL shows an "offline" notice to viewers, and the content, id, URL and view count are kept. Pass restore: true to put it back online at the same URL. Prefer this over delete_page when the human wants a page hidden or paused. Calling it twice is harmless. Returns { ok, id, live }; fails with page_not_found if the id is not in this space.
| Name | Type | Req | Description |
|---|---|---|---|
| page_id | string | yes | The page id: the `id` field from publish_page or list_pages (also the last path segment of the page URL, …/docs/<page_id>). Only pages in the connected maker's space are visible. |
| restore | boolean | – | Default false (take offline). true = put the page back online. |
No output schema declared.
No examples provided.
update_page Replace a page's content ~290
Replace the content of an existing page in place: the same URL serves the new content immediately, so links the human already shared keep working. Use this instead of publish_page whenever the page already exists. The previous version stays restorable from the dashboard for 7 days (Pro keeps full version history). Pass draft: true to stage the update instead: nothing changes for viewers until the maker reviews the previewUrl and presses "Sync to live"; use it when the human asked to see changes before they go out. Fails with page_not_found if the id is not a live or offline page in this space.
| Name | Type | Req | Description |
|---|---|---|---|
| draft | boolean | – | Default false (publishes live instantly). true = stage the update; relay the returned previewUrl so the human can review and press Sync. A new draft replaces any pending one. |
| html | string | yes | The complete new document (not a diff). HTML, or Markdown when source_type is "markdown". |
| page_id | string | yes | The page id: the `id` field from publish_page or list_pages (also the last path segment of the page URL, …/docs/<page_id>). Only pages in the connected maker's space are visible. |
| project | string | – | Optional; omit to keep the existing project. |
| source_type | string | – | Default "html". |
| title | string | – | Optional; omit to keep the existing title. |
No output schema declared.
No examples provided.
verify_email Verify the account email ~104
Finish account verification with the 6-digit code PubSpace emailed to the human (ask them to read it to you). Publishing unlocks on success. Works in the session where create_account ran, or with an API key for an unverified account. Returns { ok, verified, subdomain }; fails with invalid_code (and attemptsRemaining), code_expired, too_many_attempts or already_verified.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | The 6-digit code from the verification email. |
No output schema declared.
No examples provided.
How do I install the PubSpace MCP server?
PubSpace is a hosted endpoint at https://pubspace.ai/mcp, 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 · pubspace.ai
claude mcp add --transport http ai-pubspace-mcp 'https://pubspace.ai/mcp'
What is the PubSpace MCP server?
PubSpace is an MCP server listed in the public MCP registry as ai.pubspace/mcp. Publish HTML or markdown from your agent as a shareable link, with password or work-email walls. This page covers its hosted endpoint (https://pubspace.ai/mcp).
Is the PubSpace MCP server safe to use?
PubSpace scores 66 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 PubSpace MCP server expose?
PubSpace exposes 8 tools: publish_page, update_page, list_pages, get_page, unpublish_page, and 3 more. Their descriptions and schemas cost roughly 1,602 tokens of context every time the server is loaded.
Does the PubSpace MCP server require authentication?
No. We connected to PubSpace without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the PubSpace MCP server still maintained?
PubSpace 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 did VerifyMCP test on the PubSpace MCP server?
VerifyMCP ran 13 checks on PubSpace, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.