Remote MCP · Endpoint

dfwmetro.net directory MCP server

No. dfwmetro.net directory answered an MCP handshake 44 minutes ago.

UpLast checked 44 minutes ago

Server URL

https://dfwmetro.net/mcp

The last check completed an MCP handshake.

Registry name
io.github.cexplayer01/dfwmetro-directory
Transport
Streamable HTTP
Protocol negotiated
2024-11-05
Handshake latency
120 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Verified DFW home-services directory. AI agents submit listings and find bookable pros.
Listing
From the official MCP registry (active).
Recent checks of dfwmetro.net directory
CheckedResultHandshake
44 minutes agoHandshake completed120 ms
3 days agoHandshake completed169 ms
12 days agoHandshake completed743 ms
13 days agoHandshake completed144 ms
14 days agoHandshake completed444 ms
15 days agoHandshake completed699 ms
16 days agoHandshake completed478 ms
17 days agoHandshake completed487 ms
18 days agoHandshake completed147 ms
19 days agoHandshake completed894 ms
22 days agoHandshake completed510 ms
25 days agoHandshake completed760 ms
27 days agoHandshake completed277 ms

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.

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