Shiped MCP server
io.github.kandahk/shipedkandahkstreamable-httpv0.2.1Scanned
Deploy AI-generated HTML/CSS/JS to instant public HTTPS URLs from any MCP-compatible agent.
3 tools: 1 can delete or cancel things, 1 change things and 1 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here can delete or cancel things. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Shiped MCP server can do
The Shiped MCP server is published by the GitHub account kandahk. It has 3 tools. It can delete or cancel things (1 tool: delete_shiped_project) and create or change data (1 tool: deploy_to_shiped). 1 tool only reads.
None of its tools reads private data, brings in text other people write, or sends data out.
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 20, 2026, version 0.2.1.
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.
3 tools
Deletes or cancels 1Claude Code: deny
delete_shiped_projectDelete a deployed project from Shiped.No findings
Why it is in this group
- The name "delete_shiped_project" says "delete": a word for removing or ending something.
Description, as the server wrote it Delete a deployed project from Shiped. Deletion needs approval from the user: if the response asks for it, relay the approval link to the user and retry after they approve.
Changes things 1Claude Code: ask
deploy_to_shipedDeploy HTML/CSS/JS code to Shiped and get an instant public HTTPS URL.No findings
Why it is in this group
- The name "deploy_to_shiped" says "deploy": a word for a change.
Description, as the server wrote it 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.
Only reads 1Show 1 read-only tool
list_shiped_projectsList the user's deployed projects on Shiped with their URLs.No findings
Why it is in this group
- The name "list_shiped_projects" says "list": a word for reading.
Description, as the server wrote it List the user's deployed projects on Shiped with their URLs.
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 private-data or untrusted-input or outbound.
- Reads private data0
- 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.
Looked at Nov 20, 2026, 19:06 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 2
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://shiped.app/.well-known/oauth-protected-resource/mcp
- Authorization servers
- https://shiped.app
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- yes
- Client ID metadata documents
- no
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 2 tools that change things (1 destructive, 1 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://shiped.app/mcp: tools/list returned 3 tools to an anonymous client, including delete_shiped_project (destructive), deploy_to_shiped (write)
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.
Tools1 changed.~1 changedView diff
- Changed:delete_shiped_projectDeletes or cancelsdescription
Install
Pinned to version 0.2.1. Values in angle brackets are yours to fill in.
claude mcp add --transport http shiped https://shiped.app/mcpclaude mcp add --transport http shiped https://shiped.app/mcpRun 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.
{
"permissions": {
"allow": [
"mcp__shiped__list_shiped_projects"
],
"ask": [
"mcp__shiped__deploy_to_shiped"
],
"deny": [
"mcp__shiped__delete_shiped_project"
]
}
}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 shiped. Review it before you use it.
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/io.github.kandahk/shiped/verify?hash=b6da4e49994877e999b0410878b3e08a8a8a30f97d9db52e18c520c94f7d233b" | jq -e '.changed == false'Pinned hash b6da4e499948, from Nov 20, 2026, 00:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.kandahk/shiped/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.kandahk/shiped)Source: MCP Registry · repository. Synced Oct 21, 2026, 18:37 UTC.
Shiped MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Shiped MCP server safe?
- No scan can promise that. What its definitions show: 3 tools, 2 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 Shiped MCP server delete data?
- Yes. 1 tool can delete, cancel or revoke something: delete_shiped_project.
Can the Shiped 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 Shiped MCP server have?
- 3 tools: 1 destructive, 1 write, 1 read. delete_shiped_project, deploy_to_shiped and list_shiped_projects.
Does the Shiped MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Shiped MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Shiped MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Nov 6, 2026. Every change is on this page and in its Atom feed.