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.

demo.st

REMOTE · DEMO.ST

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

Available components

−48 this week 32 Trust /100

Last scanned (16 hours ago)

Scores higher than 15% of remote servers

Unreachable for 5 days in a row. Last reached 16 Nov 2026.

Category Cloud Infrastructure

Degraded

One or more channels of this server are currently unreachable; their trust score is decaying and will reach 0 if they stay down.

Recent critical change

TLS certificate (17 Nov 2026). See the changelog before you install this server.

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 Security11
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
  • Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
  • Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified

Unverified: 5 categories

Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

What we tested

Checks we ran (4)

  • TLS certificate
  • HTTPS
  • DNSSEC
  • Transport

Checks we could not complete (7)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  • HSTS header in Endpoint SecurityHSTS not yet verified: we couldn't read the response headers to check for it.
  • Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
  • Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
  • Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
  • Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.

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 →

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.

  • 21 Nov 26 −16

    The score moved with no change recorded against any check. We would rather say so than guess.

  • 20 Nov 26 −16

    The score moved with no change recorded against any check. We would rather say so than guess.

  • 19 Nov 26 −16

    The score moved with no change recorded against any check. We would rather say so than guess.

  • 17 Nov 26 0
    • TLS certificate: pass → fail ▼ critical
    • Score status: scored → failed ▼ critical
    • Endpoint reachability: reachable → unreachable ▼ security
    • Stability: pass → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • HSTS header: pass → unverified ▼ security
    • Transport: pass → fail ▼ security
    • Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • Schema quality: Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list. functional
  • 6 Nov 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
  • 23 Oct 26 80
    • Authorization: fail → unverified ▼ security
    • Transport: unverified → pass ▲ security
    • Injection markers: unverified → pass ▲ security
    • Stability: unverified → pass ▲ security
    • HSTS header: fail → pass ▲ security
    • Endpoint reachability: behind authorisation → reachable ▲ functional
    • MCP protocol: unverified → pass ▲ functional
    • Tool coverage: unverified → 100 ▲ functional
  • 22 Oct 26 0
    • Endpoint reachability: reachable → behind authorisation ▼ security
    • Authorization: unverified → fail ▼ security
    • Stability: pass → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Transport: pass → unverified ▼ security
    • HSTS header: pass → fail ▼ security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • First check of Schema quality: unverified functional
  • 28 Sept 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
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 21 Nov 2026 · Probed https://demo.st/mcp

TLS invalid

Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .

Chain error: Certificate expired

Subject Issuer Valid from Valid until Key Signature Serial
CN=demo.st CN=YR1,O=Let's Encrypt,C=US 18 Aug 2026 16 Nov 2026 RSA 2048 SHA256-RSA 5201d447565de024a75764b5ef20df917ae
SANs: *.demo.st, demo.st
CN=YR1,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA a20253f15f2691c05dc1ce13b9bcca4e
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of demo.st. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
st. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Inconclusive

We could not reach the endpoint well enough to judge its authorisation posture.

Result Inconclusive

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://demo.st/mcp TLS failed
http (plaintext) http://demo.st/mcp HTTPS enforced 301 https://demo.st:443/mcp
MCP tools · 13 exposed · ~643 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
check_subdomain_availability ~61

Check if a subdomain name is available on demo.st (e.g. "my-site" → my-site.demo.st).

NameTypeReqDescription
namestringyesSubdomain name: letters, numbers, hyphens only; 1–63 chars.

No output schema declared.

No examples provided.

clear_site ~22

Remove deployed site content from your subdomain. Subdomain remains reserved.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

create_collection ~52

Create a document collection (lowercase letter start; letters, numbers, underscores; max 63 chars). Max 20 collections per site.

NameTypeReqDescription
namestringyesCollection name, e.g. todos or posts.

No output schema declared.

No examples provided.

delete_collection ~29

Delete a document collection and all of its records.

NameTypeReqDescription
namestringyesCollection name to delete.

No output schema declared.

No examples provided.

delete_record ~34

Delete a record from a document collection.

NameTypeReqDescription
collectionstringyesCollection name.
idstringyesRecord id.

No output schema declared.

No examples provided.

get_site_api_key ~63

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_collections ~22

List document collections for your site (api.demo.st document store).

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_records ~49

List records in a document collection.

NameTypeReqDescription
collectionstringyesCollection name.
limitinteger–Max records to return (default 100).
offsetinteger–Offset for pagination.

No output schema declared.

No examples provided.

release_subdomain ~32

Release your reserved subdomain. Deletes the reservation, any deployed site, and all document DB data for that site.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

reserve_subdomain ~51

Reserve a subdomain for the logged-in account. One subdomain per account.

NameTypeReqDescription
subdomainstringyesSubdomain to reserve (letters, numbers, hyphens; 1–63 chars).

No output schema declared.

No examples provided.

rotate_site_api_key ~32

Rotate the public site API key. The old key stops working immediately; update your site with the new key.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

upload_site ~128

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

NameTypeReqDescription
file_pathstring–Local path to a .zip file (for local/stdio MCP only).
file_urlstring–Public URL of a .zip file.
zip_base64string–Base64-encoded .zip content. Easiest for agents: create zip locally and pass here (no hosting needed).

No output schema declared.

No examples provided.

upsert_record ~68

Create or update a JSON record in a collection. Pass data as an object. Optional id to upsert a specific record.

NameTypeReqDescription
collectionstringyesCollection name.
dataobjectyesJSON object to store.
idstring–Optional record id (create or replace).

No output schema declared.

No examples provided.

Install

How do I install the demo.st MCP server?

demo.st is a hosted endpoint at https://demo.st/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 · demo.st

# add to Claude Code
claude mcp add --transport http st-demo-demost 'https://demo.st/mcp'
Common questions

What is the demo.st MCP server?

demo.st is an MCP server listed in the public MCP registry as st.demo/demost. Reserve a subdomain, upload .zip via MCP, get a link. Optional document API at api.demo.st. This page covers its hosted endpoint (https://demo.st/mcp).

What tools does the demo.st MCP server expose?

demo.st exposes 13 tools: check_subdomain_availability, reserve_subdomain, upload_site, clear_site, release_subdomain, and 8 more. Their descriptions and schemas cost roughly 643 tokens of context every time the server is loaded.

Does the demo.st MCP server require authentication?

Its publisher declares that demo.st requires credentials, so you will need to authorise it in your MCP client. We have not been able to confirm that against the live endpoint.

Is the demo.st MCP server still maintained?

demo.st is still listed in the MCP registry, but we have not been able to reach this channel for several days and its score is decaying. We last reached this channel on 16 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.