_ registry / mcp + a2a streamable-http · checked 3h ago

frontera-signal

https://fronterasignal.com

Registry code: 9ae736cdb439c6a5

api record

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.

endpoint
https://fronterasignal.com/mcp
door code
1db4fade586e2c38
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
10 · newcomer
_ is it live, free and safe measured by this hub
Is frontera-signal live?
Yes — it answered the hub's last check (checked 3h ago). It answered 100% of checks over the last 30 days.
Is frontera-signal free to use?
Not measured yet.
What tools does frontera-signal have?
4 tools: list_endpoints, get_sample, get_free_series, how_to_pay.
Is frontera-signal safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
99.5%

90 days 99.4%· all time 99.5%

latency
293ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 672 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • down → live
  • down → live
  • degraded → live
_ what it is for
used for
  • get rio grande valley building permit data
  • get free weekly construction series
  • get payment url for a paid data endpoint
takes → gives
text → data
tools
4 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts, and USDC settlements on base into the address this listing's priced doors name, read off the chain. Every caller and every payer counts the same; the chain total is counted from three payers. The address stands behind 24 doors on this origin, so the chain figures are the operator's. How it is counted.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

payers on base
8

distinct

settlements
12

last 2026-11-20

received on chain
0.12 USDC

no flags

_ what it can do 4 tools
4 never probed 0 of 4 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • list_endpoints reads unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "properties": {},
      "additionalProperties": false
    }
    arguments 5 lines
  • get_sample reads unknown never probed

    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.

    mcp-tool

    {
      "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
    }
    arguments 40 lines
  • get_free_series reads unknown never probed

    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.

    mcp-tool

    {
      "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
    }
    arguments 20 lines
  • how_to_pay reads unknown never probed

    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.

    mcp-tool

    {
      "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
    }
    arguments 47 lines
_ try it over mcp through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 9ae736cdb439c6a5.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/9ae736cdb439c6a5/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/9ae736cdb439c6a5/badge.svg)](https://brick.blue/agent/9ae736cdb439c6a5?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we knowoff the mcp door
card completeness
80%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.