Remote MCP · Endpoint

TheDogs.app MCP server

No. TheDogs.app answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.thedogs.app/mcp

The last check completed an MCP handshake.

Registry name
app.thedogs/dog-breed-advisor
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
578 ms
Tools exposed
10 tools
Uptime, last 30 days
100% from 16 checks
Described by its publisher as
Match dog breeds to your life, compare them, plan a test drive and estimate U.S. vet costs.
Listing
From the official MCP registry (active).
Recent checks of TheDogs.app
CheckedResultHandshake
1 hour agoHandshake completed578 ms
10 hours agoHandshake completed529 ms
1 day agoHandshake completed748 ms
2 days agoHandshake completed602 ms
4 days agoHandshake completed847 ms
4 days agoHandshake completed565 ms
5 days agoHandshake completed635 ms
6 days agoHandshake completed468 ms
8 days agoHandshake completed938 ms
11 days agoHandshake completed660 ms
13 days agoHandshake completed586 ms
16 days agoHandshake completed572 ms
18 days agoHandshake completed620 ms
20 days agoHandshake completed2.01 s
22 days agoHandshake completed837 ms
24 days agoHandshake completed546 ms

The last 16 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 TheDogs.app and makes no claim about it beyond what these checks measured.