Remote MCP · Endpoint

Chip MCP MCP server

No. Chip MCP answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://chip-ai.digital/mcp/

The last check completed an MCP handshake.

Registry name
digital.chip-ai/chip
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
372 ms
Tools exposed
27 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Project memory, tasks and Telegram notifications for your coding agent. Chip account required.
Listing
From the official MCP registry (active).
Recent checks of Chip MCP
CheckedResultHandshake
1 hour agoHandshake completed372 ms
2 days agoHandshake completed397 ms
4 days agoHandshake completed336 ms
5 days agoHandshake completed340 ms
7 days agoHandshake completed348 ms
8 days agoHandshake completed335 ms
9 days agoHandshake completed337 ms
12 days agoHandshake completed343 ms
13 days agoHandshake completed340 ms
15 days agoHandshake completed365 ms
16 days agoHandshake completed346 ms
18 days agoHandshake completed340 ms
19 days agoHandshake completed338 ms
20 days agoHandshake completed341 ms
20 days agoHandshake completed369 ms
21 days agoHandshake completed373 ms
22 days agoHandshake completed403 ms

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

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