Remote MCP · Endpoint

Frontera Signal MCP server

No. Frontera Signal answered an MCP handshake 42 minutes ago.

UpLast checked 42 minutes 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
300 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
42 minutes agoHandshake completed300 ms
3 days agoHandshake completed47 ms
13 days agoHandshake completed479 ms
13 days agoHandshake completed302 ms
15 days agoHandshake completed376 ms
15 days agoHandshake completed180 ms
17 days agoHandshake completed191 ms
18 days agoHandshake completed176 ms
18 days agoHandshake completed210 ms
20 days agoHandshake completed219 ms
22 days agoHandshake completed52 ms
25 days agoHandshake completed419 ms
27 days agoHandshake completed52 ms
30 days agoHandshake completed60 ms

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

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.