Remote MCP · Endpoint

SHIP MCP server

No. SHIP answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.letsship.ai/mcp

The last check completed an MCP handshake.

Registry name
ai.letsship/ship
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
342 ms
Tools exposed
74 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Assign Linear, Jira or GitHub issues to an AI coding agent team that plans, builds, reviews, tests.
Listing
From the official MCP registry (active).
Recent checks of SHIP
CheckedResultHandshake
1 hour agoHandshake completed342 ms
22 hours agoHandshake completed347 ms
2 days agoHandshake completed105 ms
3 days agoHandshake completed317 ms
4 days agoHandshake completed272 ms
5 days agoHandshake completed291 ms
6 days agoHandshake completed443 ms
8 days agoHandshake completed481 ms
11 days agoHandshake completed496 ms
13 days agoHandshake completed139 ms
15 days agoHandshake completed130 ms
18 days agoHandshake completed341 ms
20 days agoHandshake completed656 ms
22 days agoHandshake completed306 ms
24 days agoHandshake completed661 ms

The last 15 checks. Full history is kept for 30 days; the all-time counter stands at 15 responding of 15.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with SHIP and makes no claim about it beyond what these checks measured.