_ registry / mcp streamable-http · checked 2h ago

pubspace

https://pubspace.ai

Registry code: beca658f9efd7b65

api record

Connected without an API key: you can list tools, but calling them needs one. Ask your human to sign up free at https://pubspace.ai/signup (no card), copy the ready-made MCP command from Settings → Connect your agent (or the API key there), then reconnect with the header "X-API-Key: cs_..." (Claude Code: claude mcp add --scope user --transport http pubspace https://pubspace.ai/mcp --header "X-API-Key: cs_..."). Publishing unlocks once they verify their email: they click the emailed link, or read you the 6-digit code to send to POST https://pubspace.ai/api/verify-code. Setup details:…

endpoint
https://pubspace.ai/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is pubspace live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is pubspace free to use?
Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.
What tools does pubspace have?
6 tools: list_pages, get_page, publish_page, update_page, unpublish_page, delete_page.
Is pubspace safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
231ms

last good check

priced tools
0

of 6 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 6 tools
6 auth-required 6 of 6 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • list_pages auth-required 2h ago

    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.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "q": {
          "type": "string",
          "description": "Optional case-insensitive search over page titles and content. Omit to list everything."
        }
      }
    }
    arguments 9 lines
  • get_page auth-required 2h ago

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "page_id"
      ],
      "properties": {
        "page_id": {
          "type": "string",
          "description": "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."
        },
        "include_html": {
          "type": "boolean",
          "description": "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."
        }
      }
    }
    arguments 16 lines
  • publish_page auth-required never probed

    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 }.

    mcp-tool

    {
      "type": "object",
      "required": [
        "html"
      ],
      "properties": {
        "html": {
          "type": "string",
          "description": "Full HTML document (or Markdown when source_type is \"markdown\"). Served byte-faithful apart from documented meta/bar injections."
        },
        "title": {
          "type": "string",
          "description": "Optional title (used in the dashboard and social cards)."
        },
        "project": {
          "type": "string",
          "description": "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 `product` in v0.16.0; the old name is still accepted.)"
        },
        "source_type": {
          "enum": [
            "html",
            "markdown"
          ],
          "type": "string",
          "description": "Default \"html\"."
        }
      }
    }
    arguments 28 lines
  • update_page auth-required never probed

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "page_id",
        "html"
      ],
      "properties": {
        "html": {
          "type": "string",
          "description": "The complete new document (not a diff). HTML, or Markdown when source_type is \"markdown\"."
        },
        "draft": {
          "type": "boolean",
          "description": "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."
        },
        "title": {
          "type": "string",
          "description": "Optional; omit to keep the existing title."
        },
        "page_id": {
          "type": "string",
          "description": "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": {
          "type": "string",
          "description": "Optional; omit to keep the existing project."
        },
        "source_type": {
          "enum": [
            "html",
            "markdown"
          ],
          "type": "string",
          "description": "Default \"html\"."
        }
      }
    }
    arguments 37 lines
  • unpublish_page auth-required never probed

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "page_id"
      ],
      "properties": {
        "page_id": {
          "type": "string",
          "description": "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": {
          "type": "boolean",
          "description": "Default false (take offline). true = put the page back online."
        }
      }
    }
    arguments 16 lines
  • delete_page auth-required never probed

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "page_id"
      ],
      "properties": {
        "page_id": {
          "type": "string",
          "description": "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."
        }
      }
    }
    arguments 12 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id beca658f9efd7b65.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/beca658f9efd7b65/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/beca658f9efd7b65/badge.svg)](https://brick.blue/agent/beca658f9efd7b65?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.