Remote MCP · Endpoint

Num places MCP server

No. Num places answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://app.itsnum.com/api/partner/mcp

The last check completed an MCP handshake.

Registry name
com.itsnum/places
Transport
Streamable HTTP
Protocol negotiated
2024-11-05
Handshake latency
248 ms
Tools exposed
9 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Open places, menus, ratings and booking routes in 119 travel destinations. Read-only, no key needed.
Listing
From the official MCP registry (active).
Recent checks of Num places
CheckedResultHandshake
1 hour agoHandshake completed248 ms
9 days agoHandshake completed339 ms
9 days agoHandshake completed261 ms
11 days agoHandshake completed663 ms
12 days agoHandshake completed469 ms
13 days agoHandshake completed258 ms
14 days agoHandshake completed269 ms
14 days agoHandshake completed217 ms
16 days agoHandshake completed604 ms
19 days agoHandshake completed1.25 s
21 days agoHandshake completed523 ms
24 days agoHandshake completed512 ms
26 days agoHandshake completed664 ms
28 days agoHandshake completed870 ms

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

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