Remote MCP · Endpoint

Frontera Signal MCP server

No. Frontera Signal answered an MCP handshake 5 hours ago.

UpLast checked 5 hours ago

Server URL

https://fronterasignal.com/mcp

The last check completed an MCP handshake.

Registry name
com.fronterasignal/frontera-signal
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
52 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Rio Grande Valley, Texas construction data: free catalog, samples and series; paid calls via x402
Listing
From the official MCP registry (active).
Recent checks of Frontera Signal
CheckedResultHandshake
5 hours agoHandshake completed52 ms
2 days agoHandshake completed419 ms
5 days agoHandshake completed52 ms
7 days agoHandshake completed60 ms
9 days agoHandshake completed163 ms
11 days agoHandshake completed362 ms
13 days agoHandshake completed45 ms
15 days agoHandshake completed32 ms
17 days agoHandshake completed33 ms
18 days agoHandshake completed207 ms
20 days agoHandshake completed199 ms
21 days agoHandshake completed133 ms
23 days agoHandshake completed183 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 Frontera Signal and makes no claim about it beyond what these checks measured.