Remote MCP · Endpoint

Pinsvit MCP server

No. Pinsvit answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://pinsvit.com/api/v1/mcp

The last check completed an MCP handshake.

Registry name
com.pinsvit/api
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
391 ms
Tools exposed
32 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Find and book local businesses, or run yours with Pinsvit Business: bookings, front desk, bills.
Listing
From the official MCP registry (active).
Recent checks of Pinsvit
CheckedResultHandshake
1 hour agoHandshake completed391 ms
2 days agoHandshake completed410 ms
4 days agoHandshake completed392 ms
5 days agoHandshake completed473 ms
7 days agoHandshake completed408 ms
8 days agoHandshake completed438 ms
9 days agoHandshake completed423 ms
12 days agoHandshake completed399 ms
13 days agoHandshake completed396 ms
15 days agoHandshake completed394 ms
16 days agoHandshake completed425 ms
17 days agoHandshake completed387 ms
18 days agoHandshake completed391 ms
19 days agoHandshake completed416 ms
20 days agoHandshake completed429 ms
21 days agoHandshake completed405 ms
22 days agoHandshake completed409 ms

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

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