Remote MCP · Endpoint

Location & Demand Intelligence MCP server

No. Location & Demand Intelligence answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://api.timzinin.com/mcp/location-demand-intelligence

The last check completed an MCP handshake.

Registry name
com.timzinin.api/location-demand-intelligence
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
296 ms
Tools exposed
7 tools
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
Pay-per-call where-and-when-to-operate signals from official local statistics.
Listing
From the official MCP registry (active).
Recent checks of Location & Demand Intelligence
CheckedResultHandshake
1 hour agoHandshake completed296 ms
1 day agoHandshake completed296 ms
2 days agoHandshake completed370 ms
3 days agoHandshake completed279 ms
4 days agoHandshake completed288 ms
5 days agoHandshake completed284 ms
6 days agoHandshake completed279 ms
9 days agoHandshake completed294 ms
11 days agoHandshake completed366 ms
14 days agoHandshake completed289 ms
16 days agoHandshake completed291 ms
18 days agoHandshake completed286 ms
20 days agoHandshake completed286 ms
22 days agoHandshake completed320 ms
24 days agoHandshake completed347 ms
26 days agoHandshake completed282 ms
28 days agoHandshake completed316 ms
29 days agoHandshake completed296 ms

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

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