General Tools

filadepuentes.com

Provides live and historical US–Mexico border crossing wait times, best crossing recommendations, and aggregated border news.

1 endpoint7 known toolsFirst detected October 20, 2026Last detected October 20, 2026

ENDPOINT 1

https://chat.filadepuentes.com/mcp

No auth detected

MCP server metadata

Name: filadepuentes
Version: 1.2.0

Capabilities

tools

Server instructions

Read-only live US–Mexico border wait times, best crossing, best time to cross, history and border news from filadepuentes.com. Always show the user the source_url returned with each result.

Known tools 7

get_wait_times

Current US–Mexico border crossing wait times (minutes) per bridge or port: the number filadepuentes.com publishes (CBP, adjusted by fresh community reports; in el-paso also cameras and manual verification).

Inferred read-only

best_crossing

Which bridge or port in a city has the shortest car line right now.

Inferred read-only

best_time_to_cross

Historical pattern, not live data: average and peak waits, best and worst day of the week, best hour, per bridge.

Inferred read-only

wait_history

Hourly standard (car) lane averages for one Juárez–El Paso bridge, newest hour first.

Inferred read-only

border_news

Latest border news stories from filadepuentes.com/noticias, aggregated from ~48 Mexican and US outlets and summarized in Spanish.

Inferred read-only

answer_wait_question

Turn a natural-language question like '¿cuánta fila hay en Santa Fe?' or 'how long is the San Ysidro line?' into a ready-to-post answer with live numbers (CBP data plus community reports, on every crossing) and a link.

Potential side effects

border_knowledge

Curated, source-cited answers about crossing the US–Mexico border: SENTRI and Ready Lane rules and costs, documents, what you can bring, bridge hours and quirks, tips per crossing.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.filadepuentes]
url = "https://chat.filadepuentes.com/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "filadepuentes": {
      "type": "http",
      "url": "https://chat.filadepuentes.com/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: filadepuentes
Remote MCP URL: https://chat.filadepuentes.com/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "filadepuentes": {
      "url": "https://chat.filadepuentes.com/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "filadepuentes": {
      "type": "http",
      "url": "https://chat.filadepuentes.com/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "filadepuentes",
  "transport": "streamable-http",
  "url": "https://chat.filadepuentes.com/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.