Back to MCP servers

ShipDapp

https://api.shipdapp.com/api/mcp/sse
● healthy

Deploy Dockerized apps to Akash devnet with ShipDapp MCP build, deploy, update, and logs tools.

Transport
sse
Auth
—
Cost
—
Protocol revision
—

MCP readiness

C · 60/100

Readiness is how fully this listing follows its protocol and how it behaved in our probes over 30 days. It is shown for reference and does not move it in search. Search order and leaderboards use the separate quality grade (here C, 53.4/100), which weighs availability, conformance, p95 speed and descriptor. How the two differ

Valid MCP handshake 7/10 initialize answered; tools/list failed.
  • tools/list did not return a tools array
Live MCP endpoint 25/25 Endpoint answers the MCP initialize handshake (1260 ms).
Protocol revision 0/10 No protocol revision reported by initialize.
Signed descriptor n/a No MCP standard defines a signed server descriptor.
Uptime (30 days) 15/15 30/30 probes succeeded over 30 days (100%).
Tool declaration 0/10 No tools listed by tools/list.
Verified identity 7/10 Namespace verified by the official MCP Registry (GitHub or DNS proof at publish time).
Freshness + modern flags 0/5 not seen in a source for over 30 days.
Auth declaration 0/5 How to authenticate is not stated.
Applicable criteria total 90 points, scaled to 100.
Responsiveness: Responsive (1260 ms; bands ≤2.5 s, ≤5 s, ≤8 s, slower; penalty only).
Measured 2026-11-11.
Nine criteria, the same as the A2A readiness score, read from our daily MCP probe (initialize + tools/list) and 30-day probe history. No MCP standard defines a signed server descriptor, so that criterion is n/a and the other 90 points are scaled to 100. Grades: A>=90, B>=75, C>=60, D>=40, F<40. Display only: search order uses the quality grade.

Compared with peers

Against 53,021 reachable MCP servers in our daily snapshot (2026-11-12 01:39 UTC). Display only; it does not change search order.

Readiness
Higher than 31% of peers
This listing 60 · peer median 81
Latency
Faster than 23% of peers
This listing 584 ms · peer median 326 ms

Where it loses the most points, and how to win them back

  • Protocol revision −10 — Support the current protocol revision.
    Now: No protocol revision reported by initialize.
  • Tool declaration −10 — Declare every tool with a description and input schema.
    Now: No tools listed by tools/list.
  • Freshness + modern flags −5 — Keep the listing current in the registry or source it comes from.
    Now: not seen in a source for over 30 days.

How many agent tools actually work · All statistics

Listed in

Directories this entry was found in.

How to connect

MCP endpoint (sse)
https://api.shipdapp.com/api/mcp/sse
JSON-RPC initialize probe
curl -X POST https://api.shipdapp.com/api/mcp/sse \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}'
Homepage
https://shipdapp.com
Source code
https://github.com/yash1ts/shipdapp