Koskamo

Frontera Signal MCP

An official MCP server operated by Frontera Signal that provides read-only access to business data and news for the Rio Grande Valley, Texas. It allows AI agents to list available endpoints, retrieve free samples, learn how to pay for premium data, and access free data series covering construction, produce, freight, retail, health care, and restaurants.

Endpoint and access

No sign-in to connect and list tools. Individual tools may still need a vendor account, credentials, or permissions; check the documented prerequisites.

Frontera Signal MCP logo, by Frontera SignalVendor evidenceStreamable HTTPNo sign-inEndpoint checked 2026-11-06Operated by Frontera Signal
MCP endpoint (Streamable HTTP)
https://fronterasignal.com/mcp
Vendor documentation

What its tools do

4 tools, grouped by the hints the server advertises. Hints are self-declared, not verified behavior.

Read-only (4)

4 of 4 have a description · 4 of 4 declare behavior hints · 3 of 3 with parameters document them all

Checks and signals

Each line is separate evidence, not a trust score.

  • Passed Endpoint answered the live check ·
  • Passed Official MCP Registry namespace is tied to fronterasignal.com ·
  • Passed Endpoint is on the registry namespace domain ·
  • Availability 1 of 1 checks passed in 30 days

What you can do with it

  • List available data endpoints
  • Retrieve free data samples
  • Learn how to pay for premium data
  • Access free data series

Source and maintenance

Vendor evidenceRegistry 1.0.0
mcp-registry: com.fronterasignal/frontera-signal@1.0.0Project website

Protocol and capabilities

Server
frontera-signal 1.1.0
MCP protocol negotiated in check
2025-11-25
Tools
4 advertised
Resources
Not advertised
Resource templates
Not advertised
Prompts
Not advertised
Server-advertised capabilities
{
  "tools": {
    "listChanged": false
  }
}

Server-provided instructions

Untrusted server output shown for inspection. It is not Koskamo guidance and is excluded from knowledge search.

Frontera Signal sells market data for the Rio Grande Valley, Texas, per call over x402 (construction, border crossings and bridge waits, peso and diesel, city sales tax, new businesses, alcohol sales, home health): USDC on Base, no account or API key. These tools are free and read-only. Start with list_endpoints, read a real answer with get_sample, then use how_to_pay to check your parameters and get the exact URL and price. get_free_series returns the latest 4 weeks of each weekly series at no cost. Payment happens on the HTTP API with an x402 client, never through these tools.

Tools

4 advertised

list_endpoints — List paid endpoints
Advertised by the server during the last successful anonymous check.
Advertised read-only

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.

list_endpoints input schema
{
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
list_endpoints annotations
{
  "title": "List paid endpoints",
  "readOnlyHint": true,
  "openWorldHint": false,
  "idempotentHint": true,
  "destructiveHint": false
}
get_sample — Free sample answer
Advertised by the server during the last successful anonymous check.
Advertised read-only

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.

get_sample input schema
{
  "type": "object",
  "required": [
    "endpoint"
  ],
  "properties": {
    "endpoint": {
      "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",
        "bridge-wait",
        "bridge-hourly",
        "crossings",
        "peso",
        "diesel",
        "sales-tax",
        "new-outlets",
        "alcohol-sales",
        "home-health",
        "industry",
        "ask"
      ],
      "type": "string",
      "description": "Endpoint key from list_endpoints, e.g. snapshot or series-permits-weekly."
    }
  },
  "additionalProperties": false
}
get_sample annotations
{
  "title": "Free sample answer",
  "readOnlyHint": true,
  "openWorldHint": false,
  "idempotentHint": true,
  "destructiveHint": false
}
how_to_pay — Paid URL and price
Advertised by the server during the last successful anonymous check.
Advertised read-only

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.

how_to_pay input schema
{
  "type": "object",
  "required": [
    "endpoint"
  ],
  "properties": {
    "params": {
      "type": "object",
      "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.",
      "additionalProperties": {
        "type": "string"
      }
    },
    "endpoint": {
      "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",
        "bridge-wait",
        "bridge-hourly",
        "crossings",
        "peso",
        "diesel",
        "sales-tax",
        "new-outlets",
        "alcohol-sales",
        "home-health",
        "industry",
        "ask"
      ],
      "type": "string",
      "description": "Endpoint key from list_endpoints, e.g. snapshot or series-permits-weekly."
    }
  },
  "additionalProperties": false
}
how_to_pay annotations
{
  "title": "Paid URL and price",
  "readOnlyHint": true,
  "openWorldHint": false,
  "idempotentHint": true,
  "destructiveHint": false
}
get_free_series — Free weekly series
Advertised by the server during the last successful anonymous check.
Advertised read-only

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.

get_free_series input schema
{
  "type": "object",
  "required": [
    "series"
  ],
  "properties": {
    "series": {
      "enum": [
        "permits-weekly",
        "cost-basket-weekly",
        "absorption",
        "labor-ranges",
        "calls"
      ],
      "type": "string",
      "description": "permits-weekly, cost-basket-weekly, absorption, labor-ranges or calls."
    }
  },
  "additionalProperties": false
}
get_free_series annotations
{
  "title": "Free weekly series",
  "readOnlyHint": true,
  "openWorldHint": false,
  "idempotentHint": true,
  "destructiveHint": false
}

Prompts

Not advertised

No prompt definitions available.

Resources

Not advertised

No resource definitions available.

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks
1 of 1 (100%)
Average latency
283 ms
95th percentile latency
283 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

  • · probe · passed · 283 ms · metadata changed · 4 tool(s)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http frontera-signal-mcp https://fronterasignal.com/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add frontera-signal-mcp --url https://fronterasignal.com/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable frontera-signal-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "frontera-signal-mcp": {
      "url": "https://fronterasignal.com/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).
Cline configuration
{
  "mcpServers": {
    "frontera-signal-mcp": {
      "type": "streamableHttp",
      "url": "https://fronterasignal.com/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start frontera-signal-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "frontera-signal-mcp": {
      "type": "http",
      "url": "https://fronterasignal.com/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http frontera-signal-mcp https://fronterasignal.com/mcp

Claude Desktop

Open Claude Settings > Connectors > Add custom connector, enter this server URL and enable it for the conversation. This is a manual remote-connector handoff, not a desktop JSON configuration.
Claude Desktop configuration
https://fronterasignal.com/mcp

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "frontera-signal-mcp": {
      "serverUrl": "https://fronterasignal.com/mcp"
    }
  }
}

Let your agent find its tools

Find servers like Frontera Signal MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.

Connect Koskamo Explore workflows
See all 5,258

Do you run Frontera Signal MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing