demo.st
REMOTE · DEMO.ST · SCANNED SEP 22
Reserve a subdomain, upload .zip via MCP, get a link. Optional document API at api.demo.st.
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 → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 13 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability78
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 643 tokens (~49/item across 13 items; 13 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
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 Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "clear_site" implies "remove" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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
claude mcp add --transport http st-demo-demost 'https://demo.st/mcp'
{
"mcpServers": {
"st-demo-demost": {
"url": "https://demo.st/mcp"
}
}
} {
"servers": {
"st-demo-demost": {
"type": "http",
"url": "https://demo.st/mcp"
}
}
} [mcp_servers.st-demo-demost] url = "https://demo.st/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"st-demo-demost": {
"type": "remote",
"url": "https://demo.st/mcp",
"enabled": true
}
}
} openclaw mcp add st-demo-demost --url 'https://demo.st/mcp' --transport streamable-http
mcp_servers:
st-demo-demost:
url: "https://demo.st/mcp" {
"McpServers": {
"st-demo-demost": {
"Transport": "http",
"Url": "https://demo.st/mcp"
}
}
} assistant mcp add st-demo-demost -t streamable-http -u 'https://demo.st/mcp'
{
"mcpServers": {
"st-demo-demost": {
"type": "http",
"url": "https://demo.st/mcp"
}
}
} 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.
- 26 Aug 26 −1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 +1
- Stability: 0.97 → pass security
- 19 Aug 26 0
- HTTPS: fail → pass ▲ security
- 11 Aug 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
- 31 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
- 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 0
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 22 Sept 2026 · Probed https://demo.st/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .
| 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. | absent | 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | no-referrer |
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 | Verified | 200 | |
| http (plaintext) | http://demo.st/mcp | HTTPS enforced | 301 | https://demo.st:443/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 →
check_subdomain_availability ~61
Check if a subdomain name is available on demo.st (e.g. "my-site" → my-site.demo.st).
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Subdomain 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.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Collection 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.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Collection name to delete. |
No output schema declared.
No examples provided.
delete_record ~34
Delete a record from a document collection.
| Name | Type | Req | Description |
|---|---|---|---|
| collection | string | yes | Collection name. |
| id | string | yes | Record 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.
| Name | Type | Req | Description |
|---|---|---|---|
| collection | string | yes | Collection name. |
| limit | integer | – | Max records to return (default 100). |
| offset | integer | – | 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.
| Name | Type | Req | Description |
|---|---|---|---|
| subdomain | string | yes | Subdomain 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).
| Name | Type | Req | Description |
|---|---|---|---|
| file_path | string | – | Local path to a .zip file (for local/stdio MCP only). |
| file_url | string | – | Public URL of a .zip file. |
| zip_base64 | string | – | 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.
| Name | Type | Req | Description |
|---|---|---|---|
| collection | string | yes | Collection name. |
| data | object | yes | JSON object to store. |
| id | string | – | Optional record id (create or replace). |
No output schema declared.
No examples provided.
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).
Is the demo.st MCP server safe to use?
demo.st scores 80 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 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?
No. We connected to demo.st without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the demo.st MCP server still maintained?
demo.st is still listed as active in the MCP registry. We last reached this channel on 22 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.