Frontera Signal MCP server
com.fronterasignal/frontera-signalfronterasignal.comstreamable-httpv1.0.0Scanned
Rio Grande Valley, Texas construction data: free catalog, samples and series; paid calls via x402
4 tools: 1 do something that can't be undone and 3 only read.
- Reads private data · 0
- Reads text others write · 1
- Can send data out · 2
- 1 finding
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here does something that can't be undone. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Frontera Signal MCP server can do
The Frontera Signal MCP server is published by fronterasignal.com, a domain the MCP Registry verified. It has 4 tools. It can do things that cannot be undone, such as sending, paying or publishing (how_to_pay), but cannot delete data. 3 tools only read.
1 tool brings in text other people can write (get_sample); 2 tools can send data out of your system (get_sample and how_to_pay).
The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.
Last scanned Nov 13, 2026, version 1.0.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
4 tools
Can't be undone 1Claude Code: ask
how_to_payGet the exact URL to call for a paid answer, with its price, network and asset.Can send data out1 finding
Why it is in this group
- The name "how_to_pay" says "pay": a word that usually means money moves, which cannot be taken back.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- outboundThe input takes a URL (input.endpoint): a request to a URL can carry data to whoever runs it.
Findings
- Warn
The server marks "how_to_pay" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "how_to_pay" says "pay": a word that usually means money moves, which cannot be taken back.
Description, as the server wrote it 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.
Annotations the server declares
- title: Paid URL and price
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
Only reads 3Show 3 read-only tools
get_free_seriesGet 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 sup…No findings
Why it is in this group
- The name "get_free_series" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Free weekly series
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_sampleGet 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.Reads text others writeCan send data outNo findings
Why it is in this group
- The name "get_sample" says "get": a word for reading.
What it can reach
- untrusted-inputThe input takes a URL (input.endpoint), and the tool reads it: it reads web pages, which anyone can write.
- outboundThe input takes a URL (input.endpoint): a request to a URL can carry data to whoever runs it.
Claude Code: ask, because it is tagged outbound.
Description, as the server wrote it 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.
Annotations the server declares
- title: Free sample answer
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list_endpointsList every paid Frontera Signal endpoint before you spend anything.No findings
Why it is in this group
- The name "list_endpoints" says "list": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: List paid endpoints
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write1
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out2
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:38 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 1
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 irreversible). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://fronterasignal.com/mcp: tools/list returned 4 tools to an anonymous client, including how_to_pay (irreversible)
Findings
Matches of fixed checks, with the text they matched.
- Warnhow_to_pay
The server marks "how_to_pay" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "how_to_pay" says "pay": a word that usually means money moves, which cannot be taken back.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools2 changed.~2 changedView diff
- Changed:get_sampleOnly readsinputSchema
- Changed:how_to_payCan't be undoneinputSchema
Tools3 changed.~3 changedView diff
- Changed:get_sampleOnly readsinputSchema
- Changed:how_to_payCan't be undoneinputSchema
- Changed:list_endpointsOnly readsdescription
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http frontera-signal https://fronterasignal.com/mcpclaude mcp add --transport http frontera-signal https://fronterasignal.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__frontera-signal__list_endpoints",
"mcp__frontera-signal__get_free_series"
],
"ask": [
"mcp__frontera-signal__get_sample",
"mcp__frontera-signal__how_to_pay"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as frontera-signal. Review it before you use it.
Capability tags behind 2 rules
- mcp__frontera-signal__get_sample untrusted-input, outbound
- mcp__frontera-signal__how_to_pay outbound
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.fronterasignal/frontera-signal/verify?hash=a65442f7a971a95900f30b058a08d88524de400fa418108a87e8011a18c88185" | jq -e '.changed == false'Pinned hash a65442f7a971, from Nov 13, 2026, 07:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.fronterasignal/frontera-signal/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.fronterasignal/frontera-signal)Source: MCP Registry. Synced Oct 21, 2026, 17:55 UTC.
Frontera Signal MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Frontera Signal MCP server safe?
- No scan can promise that. What its definitions show: 4 tools, 1 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Frontera Signal MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Frontera Signal MCP server do things that cannot be undone?
- Yes. 1 tool can send, pay, publish or merge: how_to_pay.
What tools does the Frontera Signal MCP server have?
- 4 tools: 1 irreversible, 3 read. how_to_pay, list_endpoints, get_sample and get_free_series.
Does the Frontera Signal MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Frontera Signal MCP server send data to outside services?
- 2 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): get_sample and how_to_pay.
Has the Frontera Signal MCP server changed its tools?
- Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 13, 2026. Every change is on this page and in its Atom feed.