Remote MCP · Endpoint

Tulimoa MCP server

No. Tulimoa answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.tulimoa.com/mcp

The last check completed an MCP handshake.

Registry name
com.tulimoa/platform
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
213 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Find curated AI and MCP tools in the Tulimoa directory; submit yours free with a badge or for $5.
Listing
From the official MCP registry (active).
Recent checks of Tulimoa
CheckedResultHandshake
1 hour agoHandshake completed213 ms
2 days agoHandshake completed66 ms
4 days agoHandshake completed203 ms
5 days agoHandshake completed406 ms
7 days agoHandshake completed239 ms
8 days agoHandshake completed275 ms
9 days agoHandshake completed245 ms
12 days agoHandshake completed223 ms
13 days agoHandshake completed74 ms
15 days agoHandshake completed248 ms
16 days agoHandshake completed275 ms
17 days agoHandshake completed215 ms
18 days agoHandshake completed220 ms
19 days agoHandshake completed217 ms
20 days agoHandshake completed259 ms
21 days agoHandshake completed245 ms
22 days agoHandshake completed321 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 Tulimoa and makes no claim about it beyond what these checks measured.