Skip to content

demo.st MCP server

st.demo/demostdemo.ststreamable-httpv1.1.0Scanned

Reserve a subdomain, upload .zip via MCP, get a link. Optional document API at api.demo.st.

13 tools: 3 can delete or cancel things, 7 change things and 3 only read.

Tools: 3 delete, 0 irreversible, 7 write, 3 read.
  • Reads private data · 2
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

Sign-in required, no OAuth metadata. Remote posture

Anlyon alternative

10 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

What the demo.st MCP server can do

The demo.st MCP server is published by demo.st, a domain the MCP Registry verified. It has 13 tools. It can delete or cancel things (3 tools: clear_site, delete_collection and delete_record) and create or change data (7 tools: check_subdomain_availability, reserve_subdomain, upload_site, release_subdomain and 3 more). 3 tools only read.

2 tools read private data (list_collections and list_records).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Last scanned Nov 4, 2026, version 1.1.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

13 tools

Deletes or cancels 3Claude Code: deny
  • clear_siteRemove deployed site content from your subdomain.No findings

    Why it is in this group

    • The description's first verb is "remove": a word for removing or ending something.
    Description, as the server wrote it
    Remove deployed site content from your subdomain. Subdomain remains reserved.
  • delete_collectionDelete a document collection and all of its records.No findings

    Why it is in this group

    • The name "delete_collection" says "delete": a word for removing or ending something.
    Description, as the server wrote it
    Delete a document collection and all of its records.
  • delete_recordDelete a record from a document collection.No findings

    Why it is in this group

    • The name "delete_record" says "delete": a word for removing or ending something.
    Description, as the server wrote it
    Delete a record from a document collection.
Changes things 7Claude Code: ask
  • check_subdomain_availabilityCheck if a subdomain name is available on demo.st (e.g.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Check if a subdomain name is available on demo.st (e.g. "my-site" → my-site.demo.st).
  • create_collectionCreate a document collection (lowercase letter start; letters, numbers, underscores; max 63 chars).No findings

    Why it is in this group

    • The name "create_collection" says "create": a word for a change.
    Description, as the server wrote it
    Create a document collection (lowercase letter start; letters, numbers, underscores; max 63 chars). Max 20 collections per site.
  • release_subdomainRelease your reserved subdomain.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Release your reserved subdomain. Deletes the reservation, any deployed site, and all document DB data for that site.
  • reserve_subdomainReserve a subdomain for the logged-in account.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Reserve a subdomain for the logged-in account. One subdomain per account.
  • rotate_site_api_keyRotate the public site API key.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Rotate the public site API key. The old key stops working immediately; update your site with the new key.
  • upload_siteUpload a .zip as site content for your reserved subdomain.No findings

    Why it is in this group

    • The name "upload_site" says "upload": a word for a change.
    Description, as the server wrote it
    Upload a .zip as site content for your reserved subdomain. Easiest for agents: zip_base64 (base64-encoded zip). Or file_url (public URL to zip). Or file_path (local path, when MCP runs locally).
  • upsert_recordCreate or update a JSON record in a collection.No findings

    Why it is in this group

    • The name "upsert_record" says "upsert": a word for a change.
    Description, as the server wrote it
    Create or update a JSON record in a collection. Pass data as an object. Optional id to upsert a specific record.
Only reads 3Show 3 read-only tools
  • get_site_api_keyGet (or create) the public site API key for your reserved subdomain.No findings

    Why it is in this group

    • The name "get_site_api_key" says "get": a word for reading.
    Description, as the server wrote it
    Get (or create) the public site API key for your reserved subdomain. Embed this key in your static site and call https://api.demo.st/v1 with Authorization: Bearer <key>. Tenant is scoped by the key — never share another site's key.
  • list_collectionsList document collections for your site (api.demo.st document store).Reads private dataNo findings

    Why it is in this group

    • The name "list_collections" says "list": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "list" and "document": it reads documents.
    Description, as the server wrote it
    List document collections for your site (api.demo.st document store).
  • list_recordsList records in a document collection.Reads private dataNo findings

    Why it is in this group

    • The name "list_records" says "list": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "list" and "document": it reads documents.
    Description, as the server wrote it
    List records in a document collection.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged untrusted-input or outbound.

Reads private data2
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Sign-in required, no OAuth metadata

Looked at Nov 20, 2026, 19:19 UTC, unchanged since Nov 20, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
526
tools/list served without credentials
no
Tools that change things, listed without credentials
0
Protocol version
not observed
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed

The probe stopped: initialize answered HTTP 526.

Posture changes

  1. Nov 20, 2026
    • HTTP status of an anonymous initialize: 200 to 526
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 10 to 0
    • Protocol version: 2025-06-18 to none

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. HTTP status of an anonymous initialize: 200 -> 526; tools/list served without credentials: yes -> no; Tools that change things, listed without credentials: 10 -> 0 (and 1 more).View diff
    • HTTP status of an anonymous initialize: 200 to 526
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 10 to 0
    • Protocol version: 2025-06-18 to none

Install

Pinned to version 1.1.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http demost https://demo.st/mcp --header 'Authorization: <your-authorization>'
claude mcp add --transport http demost https://demo.st/mcp --header 'Authorization: <your-authorization>'

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__demost__get_site_api_key",
      "mcp__demost__list_collections",
      "mcp__demost__list_records"
    ],
    "ask": [
      "mcp__demost__check_subdomain_availability",
      "mcp__demost__reserve_subdomain",
      "mcp__demost__upload_site",
      "mcp__demost__release_subdomain",
      "mcp__demost__rotate_site_api_key",
      "mcp__demost__create_collection",
      "mcp__demost__upsert_record"
    ],
    "deny": [
      "mcp__demost__clear_site",
      "mcp__demost__delete_collection",
      "mcp__demost__delete_record"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as demost. Review it before you use it.

Capability tags behind 2 rules
  • mcp__demost__list_collections private-data
  • mcp__demost__list_records private-data

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/st.demo/demost/verify?hash=0aa90f4dc8f7fe3c6a23a69dd9304475d55f67603967f802d720e29038613066" | jq -e '.changed == false'

Pinned hash 0aa90f4dc8f7, from Nov 4, 2026, 15:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/st.demo/demost/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for st.demo/demost
[![Anlyon Radar](https://radar.anlyon.com/badge/st.demo/demost.svg)](https://radar.anlyon.com/servers/st.demo/demost)

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:55 UTC.

demo.st MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the demo.st MCP server safe?

No scan can promise that. What its definitions show: 13 tools, 10 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the demo.st MCP server delete data?

Yes. 3 tools can delete, cancel or revoke something: clear_site, delete_collection and delete_record.

Can the demo.st MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the demo.st MCP server have?

13 tools: 3 destructive, 7 write, 3 read. clear_site, delete_collection, delete_record, check_subdomain_availability, reserve_subdomain, upload_site, release_subdomain, rotate_site_api_key and 5 more.

Does the demo.st MCP server need sign-in or OAuth?

Its remote endpoint did not answer the last anonymous look.

Does the demo.st MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the demo.st MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 4, 2026.