Remote MCP · Endpoint

CommonTape MCP server

No. CommonTape answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://commontape.com/api/mcp

The last check completed an MCP handshake.

Registry name
com.commontape/booking
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
68 ms
Tools exposed
10 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Quote, hold and book US house cleaning jobs on a customer's behalf, at each business's own prices.
Website
https://commontape.com/docs
Listing
From the official MCP registry (active).
Recent checks of CommonTape
CheckedResultHandshake
1 hour agoHandshake completed68 ms
2 days agoHandshake completed80 ms
5 days agoHandshake completed63 ms
7 days agoHandshake completed93 ms
9 days agoHandshake completed137 ms
11 days agoHandshake completed87 ms
13 days agoHandshake completed71 ms
15 days agoHandshake completed191 ms
17 days agoHandshake completed68 ms
19 days agoHandshake completed67 ms
20 days agoHandshake completed193 ms
21 days agoCredentials required—
23 days agoCredentials required—

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

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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

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