Remote MCP · Endpoint

PHION Task Router MCP server

No. PHION Task Router answered an MCP handshake 44 minutes ago.

UpLast checked 44 minutes ago

Server URL

https://phion.systems/mcp/task

The last check completed an MCP handshake.

Registry name
systems.phion/evidence-engine
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
102 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Find the best eligible service for an agent task through one task-first MCP tool.
Listing
From the official MCP registry (active).
Recent checks of PHION Task Router
CheckedResultHandshake
44 minutes agoHandshake completed102 ms
3 days agoHandshake completed105 ms
12 days agoHandshake completed94 ms
13 days agoHandshake completed102 ms
14 days agoHandshake completed4.67 s
15 days agoHandshake completed90 ms
16 days agoHandshake completed116 ms
17 days agoHandshake completed227 ms
18 days agoHandshake completed92 ms
19 days agoHandshake completed106 ms
22 days agoHandshake completed94 ms
25 days agoHandshake completed98 ms
27 days agoHandshake completed91 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 PHION Task Router and makes no claim about it beyond what these checks measured.