Frontera Signal
REMOTE · FRONTERASIGNAL.COM
Rio Grande Valley, Texas construction data: free catalog, samples and series; paid calls via x402
Available components
Last scanned (9 hours ago)
Scores higher than 94% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Data and Analytics
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security83
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability73
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 641 tokens (~160/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "how_to_pay" implies "pay" and declares readOnlyHint instead, contradicting what its own name says it does. See how to fix → Fail
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 2 Nov 26 +1
- Stability: 0.97 → pass security
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +2
- DNSSEC: fail → pass ▲ security
- Server version: 1.0.0 → 1.1.0 functional
- 27 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “list_endpoints” rewrote its description, which is the text the model reads security
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://fronterasignal.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=fronterasignal.com | CN=WE1,O=Google Trust Services,C=US | 23 Sept 2026 | 22 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 32a07eba707384a0ef87b03e4cbaa5d |
| SANs: fronterasignal.com, www.fronterasignal.com, *.www.fronterasignal.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of fronterasignal.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| fronterasignal.com. | present | 2371 | 13 | Verified |
| fronterasignal.com. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| content-security-policy | default-src 'self'; script-src 'self' https://static.cloudflareinsights.com; style-src 'self' 'unsafe-inline'; font-src 'self'; img-src 'self' data:; connect-src 'self' https://cloudflareinsights.com; frame-ancestors 'none'; base-uri 'self'; form-action 'self' https://checkout.stripe.com; object-src 'none'; upgrade-insecure-requests |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), payment=(), usb=(), interest-cohort=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://fronterasignal.com/mcp | Verified | 200 | |
| http (plaintext) | http://fronterasignal.com/mcp | HTTPS enforced | 301 | https://fronterasignal.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_free_series Free weekly series ~123
Get the latest 4 weeks of a weekly Rio Grande Valley series for free: permits-weekly (building permits by city), cost-basket-weekly (building-input prices), absorption (housing supply), labor-ranges (labor and financing conditions) or calls (graded forecasts). Each row carries its week, as_of date and status. The full history is a paid endpoint; how_to_pay with series-<name> gives its URL and price.
| Name | Type | Req | Description |
|---|---|---|---|
| series | string | yes | permits-weekly, cost-basket-weekly, absorption, labor-ranges or calls. |
No output schema declared.
No examples provided.
get_sample Free sample answer ~86
Get a real answer from one paid endpoint for free, exactly as a paid call returns it, so you can check the fields, dates and coverage before you pay. Pass the endpoint key from list_endpoints, such as snapshot, projects or series-permits-weekly.
| Name | Type | Req | Description |
|---|---|---|---|
| endpoint | string | yes | Endpoint key from list_endpoints, e.g. snapshot or series-permits-weekly. |
No output schema declared.
No examples provided.
how_to_pay Paid URL and price ~168
Get the exact URL to call for a paid answer, with its price, network and asset. Pass the endpoint key and the query parameters you plan to send; they go through the same free check the API runs before payment, so a query that would be refused or come back empty shows up here. This tool never calls the paid endpoint and never pays. Payment is x402: no account or API key, USDC on Base.
| Name | Type | Req | Description |
|---|---|---|---|
| endpoint | string | yes | Endpoint key from list_endpoints, e.g. snapshot or series-permits-weekly. |
| params | object | – | Query parameters you plan to send, as strings, e.g. {"city": "McAllen"}. list_endpoints gives each endpoint's parameters and valid values. Omit for a call with no parameters. |
No output schema declared.
No examples provided.
list_endpoints List paid endpoints ~131
List every paid Frontera Signal endpoint before you spend anything. Covers Rio Grande Valley, Texas market data: construction (permits, building-input prices, housing supply, labor, commercial projects filed with the state, company track records, filed cost per square foot, material shelf prices, the weekly briefing), bridge wait times, border crossings, peso, diesel, city sales tax, new businesses, bar and restaurant alcohol sales and home health agencies. Each entry has the price per call in USDC, what the call returns, an example question, its parameters with valid values and a free sample URL. Free.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the Frontera Signal MCP server?
Frontera Signal is a hosted endpoint at https://fronterasignal.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · fronterasignal.com
claude mcp add --transport http com-fronterasignal-frontera-signal 'https://fronterasignal.com/mcp'
What is the Frontera Signal MCP server?
Frontera Signal is an MCP server listed in the public MCP registry as com.fronterasignal/frontera-signal. Rio Grande Valley, Texas construction data: free catalog, samples and series; paid calls via x402. This page covers its hosted endpoint (https://fronterasignal.com/mcp).
Is the Frontera Signal MCP server safe to use?
Frontera Signal scores 87 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Frontera Signal MCP server expose?
Frontera Signal exposes 4 tools: list_endpoints, get_sample, how_to_pay, get_free_series. Their descriptions and schemas cost roughly 508 tokens of context every time the server is loaded.
Does the Frontera Signal MCP server require authentication?
No. We connected to Frontera Signal without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Frontera Signal MCP server still maintained?
Frontera Signal is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.