# Frontera Signal (remote · fronterasignal.com)

Rio Grande Valley, Texas construction data: free catalog, samples and series; paid calls via x402

- Trust score: 87/100 (high trust)
- Change this week: +2
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `fronterasignal.com`: 87/100 (this document), [markdown](https://verifymcp.io/servers/com-fronterasignal-frontera-signal/fronterasignal.md), [page](https://verifymcp.io/servers/com-fronterasignal-frontera-signal/fronterasignal)

## Channel facts

- Endpoint: `https://fronterasignal.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 83/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 73/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 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.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### 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.

### Claude

```bash
claude mcp add --transport http com-fronterasignal-frontera-signal 'https://fronterasignal.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-fronterasignal-frontera-signal": {
      "url": "https://fronterasignal.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-fronterasignal-frontera-signal": {
      "type": "http",
      "url": "https://fronterasignal.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-fronterasignal-frontera-signal]
url = "https://fronterasignal.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-fronterasignal-frontera-signal": {
      "type": "remote",
      "url": "https://fronterasignal.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-fronterasignal-frontera-signal --url 'https://fronterasignal.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-fronterasignal-frontera-signal:
    url: "https://fronterasignal.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-fronterasignal-frontera-signal": {
      "Transport": "http",
      "Url": "https://fronterasignal.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-fronterasignal-frontera-signal -t streamable-http -u 'https://fronterasignal.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-fronterasignal-frontera-signal": {
      "type": "http",
      "url": "https://fronterasignal.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-02 (score 87, +1)

- [security] Stability: 0.97 → pass

### 2026-10-31 (score 86, +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.

### 2026-10-29 (score 85, +2)

- [security improvement] DNSSEC: fail → pass
- [functional] Server version: 1.0.0 → 1.1.0

### 2026-10-27 (score 83, 0)

- [security] 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

### 2026-10-25 (score 83, +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.

### 2026-10-23 (score 82, +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.

### 2026-10-20 (score 81, +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.

### 2026-10-18 (score 80, +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.

## MCP tools (4)

### `list_endpoints` (~131 tokens)

List paid endpoints

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.

### `get_sample` (~86 tokens)

Free sample answer

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.

Input parameters:

- `endpoint` (string, required): Endpoint key from list_endpoints, e.g. snapshot or series-permits-weekly.

### `how_to_pay` (~168 tokens)

Paid URL and price

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.

Input parameters:

- `endpoint` (string, required): 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.

### `get_free_series` (~123 tokens)

Free weekly series

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.

Input parameters:

- `series` (string, required): permits-weekly, cost-basket-weekly, absorption, labor-ranges or calls.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-fronterasignal-frontera-signal/fronterasignal#diagnostics

## Score history

- 2026-11-05: 87
- 2026-11-04: 87
- 2026-11-03: 87
- 2026-11-02: 87
- 2026-11-01: 86
- 2026-10-31: 86
- 2026-10-30: 85
- 2026-10-29: 85
- 2026-10-28: 83
- 2026-10-27: 83
- 2026-10-26: 83
- 2026-10-25: 83
- 2026-10-24: 82
- 2026-10-23: 82
- 2026-10-22: 81
- 2026-10-21: 81
- 2026-10-20: 81
- 2026-10-19: 80
- 2026-10-18: 80
- 2026-10-17: 79
- 2026-10-16: 79
- 2026-10-15: 78
- 2026-10-14: 78
- 2026-10-13: 77
- 2026-10-12: 77
- 2026-10-10: 76
- 2026-10-07: 74
- 2026-10-06: 74
- 2026-10-04: 73
- 2026-10-03: 73

## Common questions

### 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.

## Links

- Remote endpoint: https://fronterasignal.com/mcp
- Website: https://fronterasignal.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-fronterasignal-frontera-signal/fronterasignal.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-fronterasignal-frontera-signal/fronterasignal.json
- HTML version of this page: https://verifymcp.io/servers/com-fronterasignal-frontera-signal/fronterasignal