Shiped
REMOTE · SHIPED.APP · SCANNED SEP 20
Deploy AI-generated HTML/CSS/JS to instant public HTTPS URLs from any MCP-compatible agent.
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 Security89
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- 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
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability74
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 169 tokens (~56/item across 3 items; 3 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management43
- Stability observed for 13 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 Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "deploy_to_shiped" implies "deploy" 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 3 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 Shiped MCP server?
Shiped is a hosted endpoint at https://shiped.app/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 · shiped.app
claude mcp add --transport http kandahk-shiped 'https://shiped.app/mcp'
{
"mcpServers": {
"kandahk-shiped": {
"url": "https://shiped.app/mcp"
}
}
} {
"servers": {
"kandahk-shiped": {
"type": "http",
"url": "https://shiped.app/mcp"
}
}
} [mcp_servers.kandahk-shiped] url = "https://shiped.app/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"kandahk-shiped": {
"type": "remote",
"url": "https://shiped.app/mcp",
"enabled": true
}
}
} openclaw mcp add kandahk-shiped --url 'https://shiped.app/mcp' --transport streamable-http
mcp_servers:
kandahk-shiped:
url: "https://shiped.app/mcp" {
"McpServers": {
"kandahk-shiped": {
"Transport": "http",
"Url": "https://shiped.app/mcp"
}
}
} assistant mcp add kandahk-shiped -t streamable-http -u 'https://shiped.app/mcp'
{
"mcpServers": {
"kandahk-shiped": {
"type": "http",
"url": "https://shiped.app/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.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 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.
- 14 Sept 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.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Sept 26 +1
- Stability: unverified → 0.03 ▲ functional
- 7 Sept 26 +39
- Transport: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Authorization: Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. security
- MCP protocol: unverified → pass ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- First check of Schema quality: fail functional
- First check of Destructive annotations: 0 functional
- First check of Schema quality: pass functional
- First check of Schema quality: good functional
- First check of Tool coverage: 100 functional
- 5 Sept 26 36
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 20 Sept 2026 · Probed https://shiped.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=shiped.app | CN=WE1,O=Google Trust Services,C=US | 11 Aug 2026 | 9 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 38726de324c92c2413632a5ec8ac3c3f |
| SANs: shiped.app | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of shiped.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| shiped.app. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer resource_metadata="https://shiped.app/.well-known/oauth-protected-resource/mcp"
Bearer resource_metadata="https://shiped.app/.well-known/oauth-protected-resource/mcp"Protected resource metadata
| Document | https://shiped.app/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://shiped.app/mcp |
| Authorisation server | https://shiped.app |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://shiped.app/mcp | Verified | 200 | |
| http (plaintext) | http://shiped.app/mcp | HTTPS enforced | 301 | https://shiped.app/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 →
delete_shiped_project ~29
Delete a deployed project from Shiped.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | Project slug to delete |
No output schema declared.
No examples provided.
deploy_to_shiped ~118
Deploy HTML/CSS/JS code to Shiped and get an instant public HTTPS URL. Use after generating code with an AI to make it live and shareable.
| Name | Type | Req | Description |
|---|---|---|---|
| files | array | – | Multiple files for multi-file projects |
| html | string | – | Complete HTML content (single file deployment) |
| name | string | yes | Project name — becomes the subdomain |
| type | string | – | Project type. Defaults to "static". "node" runs a single index.js file, "python" runs a single main.py file. |
No output schema declared.
No examples provided.
list_shiped_projects ~22
List the user's deployed projects on Shiped with their URLs.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the Shiped MCP server?
Shiped is an MCP server listed in the public MCP registry as io.github.kandahk/shiped. Deploy AI-generated HTML/CSS/JS to instant public HTTPS URLs from any MCP-compatible agent. This page covers its hosted endpoint (https://shiped.app/mcp).
Is the Shiped MCP server safe to use?
Shiped scores 81 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 Shiped MCP server expose?
Shiped exposes 3 tools: deploy_to_shiped, list_shiped_projects, delete_shiped_project. Their descriptions and schemas cost roughly 169 tokens of context every time the server is loaded.
Does the Shiped MCP server require authentication?
Yes. Shiped asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the Shiped MCP server still maintained?
Shiped is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.