Remote MCP · Endpoint

Entyrax MCP server

No. Entyrax answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://www.entyrax.com/mcp

The last check completed an MCP handshake.

Registry name
com.entyrax/entyrax
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
316 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
PC hardware decision engine for Brazil (pt-BR): compatibility, GPU recommendations, build analysis.
Listing
From the official MCP registry (active).
Recent checks of Entyrax
CheckedResultHandshake
1 hour agoHandshake completed316 ms
2 days agoHandshake completed375 ms
4 days agoHandshake completed493 ms
5 days agoHandshake completed368 ms
7 days agoHandshake completed341 ms
8 days agoHandshake completed602 ms
9 days agoHandshake completed1.04 s
12 days agoHandshake completed337 ms
13 days agoHandshake completed497 ms
15 days agoHandshake completed436 ms
16 days agoHandshake completed416 ms
17 days agoHandshake completed347 ms
18 days agoHandshake completed406 ms
19 days agoHandshake completed302 ms
20 days agoHandshake completed433 ms
21 days agoHandshake completed365 ms
22 days agoHandshake completed355 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 Entyrax and makes no claim about it beyond what these checks measured.