Frontera Signal

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

Should I use this

Quality & Safety

A
Description quality
100%
Schema completeness
83%
Naming quality
95%
Poisoning risk
100%
Permission match
100%
Protocol compliance
100%

Based on automated analysis of tool definitions and protocol compliance.

Context Cost

~854Tokens (tool definitions)
~1.1 KBTypical response size
Moderate attention impact (0.67% of 128k context)

This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.

Install

One-Click Install

Add this to your `claude_desktop_config.json` file:

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

Remote endpoints

https://fronterasignal.com/mcpstreamable-http

What it can do

Tool inventory

Tools (4)

🟢 Read-only🟡 Write🔴 Delete⚪ Unknown
🟢list_endpoints

List every paid Frontera Signal endpoint before you spend anything. Covers Rio Grande Valley, Texas construction data: permits, building-input prices, housing supply, labor, commercial projects filed with the state, company track records, filed cost per square foot, material shelf prices and the weekly briefing. 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

{
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
🟢get_sample(endpoint)

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 Schema

{
  "type": "object",
  "properties": {
    "endpoint": {
      "type": "string",
      "enum": [
        "snapshot",
        "projects",
        "companies",
        "nearby",
        "parcel",
        "cost-per-sqft",
        "materials",
        "series-permits-weekly",
        "series-permits-monthly",
        "series-cost-basket-weekly",
        "series-absorption",
        "series-labor-ranges",
        "series-calls",
        "issue"
      ],
      "description": "Endpoint key from list_endpoints, e.g. snapshot or series-permits-weekly."
    }
  },
  "required": [
    "endpoint"
  ],
  "additionalProperties": false
}
🟢how_to_pay(endpoint, params)

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 Schema

{
  "type": "object",
  "properties": {
    "endpoint": {
      "type": "string",
      "enum": [
        "snapshot",
        "projects",
        "companies",
        "nearby",
        "parcel",
        "cost-per-sqft",
        "materials",
        "series-permits-weekly",
        "series-permits-monthly",
        "series-cost-basket-weekly",
        "series-absorption",
        "series-labor-ranges",
        "series-calls",
        "issue"
      ],
      "description": "Endpoint key from list_endpoints, e.g. snapshot or series-permits-weekly."
    },
    "params": {
      "type": "object",
      "additionalProperties": {
        "type": "string"
      },
      "description": "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."
    }
  },
  "required": [
    "endpoint"
  ],
  "additionalProperties": false
}
🟢get_free_series(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 Schema

{
  "type": "object",
  "properties": {
    "series": {
      "type": "string",
      "enum": [
        "permits-weekly",
        "cost-basket-weekly",
        "absorption",
        "labor-ranges",
        "calls"
      ],
      "description": "permits-weekly, cost-basket-weekly, absorption, labor-ranges or calls."
    }
  },
  "required": [
    "series"
  ],
  "additionalProperties": false
}

Community

Rate this Server

Evidence

Recent observations

verifiedversion not recorded4 tools