Remote MCP · Endpoint

TeamShift MCP server

Yes, as of 42 minutes ago: the server returned an HTTP error.

DownLast checked 42 minutes ago

Server URL

https://api.teamshift.io/v1/claude/mcp

The last check failed: the server returned an HTTP error.

Registry name
io.teamshift/teamshift
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
Not measured yet
Uptime, last 30 days
0.0% from 13 checks
Described by its publisher as
Read your TeamShift team, tasks and memory via OAuth, or use workspace tools with an API key.
Listing
From the official MCP registry (active).
Recent checks of TeamShift
CheckedResultHandshake
42 minutes agoFailed - the server returned an HTTP error—
3 days agoFailed - the connection was refused or dropped—
13 days agoFailed - the connection was refused or dropped—
13 days agoFailed - the connection was refused or dropped—
15 days agoFailed - the connection was refused or dropped—
15 days agoFailed - the connection was refused or dropped—
17 days agoFailed - the connection was refused or dropped—
18 days agoFailed - the connection was refused or dropped—
18 days agoFailed - the connection was refused or dropped—
20 days agoFailed - the connection was refused or dropped—
22 days agoFailed - the connection was refused or dropped—
25 days agoFailed - the connection was refused or dropped—
27 days agoFailed - the connection was refused or dropped—
30 days agoFailed - the connection was refused or dropped—

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

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 TeamShift and makes no claim about it beyond what these checks measured.