Remote MCP · Endpoint

Petnecto MCP server

No. Petnecto answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://petnecto.com/mcp

The last check completed an MCP handshake.

Registry name
com.petnecto/pets
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
91 ms
Tools exposed
11 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Paw to paw. Shelter pets, one question away: adoptable pets near you, and how to reach the rescue.
Website
https://petnecto.com/
Listing
From the official MCP registry (active).
Recent checks of Petnecto
CheckedResultHandshake
1 hour agoHandshake completed91 ms
7 hours agoHandshake completed99 ms
2 days agoHandshake completed307 ms
4 days agoHandshake completed132 ms
6 days agoHandshake completed168 ms
9 days agoHandshake completed840 ms
11 days agoHandshake completed176 ms
13 days agoHandshake completed85 ms
15 days agoHandshake completed232 ms
17 days agoHandshake completed86 ms
19 days agoHandshake completed436 ms
21 days agoHandshake completed341 ms
23 days agoHandshake completed366 ms
24 days agoHandshake completed413 ms

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

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