Remote MCP · Endpoint

Pathwize MCP server

No. Pathwize answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://www.gopathwize.com/api/mcp

The last check completed an MCP handshake.

Registry name
com.gopathwize/pathwize
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
169 ms
Tools exposed
10 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Run data annotation and evaluation tasks with vetted domain experts: create, publish, get results.
Website
https://www.gopathwize.com/
Listing
From the official MCP registry (active).
Recent checks of Pathwize
CheckedResultHandshake
1 hour agoHandshake completed169 ms
2 days agoHandshake completed140 ms
5 days agoHandshake completed915 ms
7 days agoHandshake completed1.04 s
9 days agoHandshake completed111 ms
11 days agoHandshake completed1.76 s
13 days agoHandshake completed1.72 s
15 days agoHandshake completed147 ms
17 days agoHandshake completed129 ms
19 days agoHandshake completed1.69 s
20 days agoHandshake completed777 ms
21 days agoHandshake completed798 ms
23 days agoHandshake completed84 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.

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