mcpbeat

fccdb MCP Server

com.fccdb/api
answering

fccdb is answering right now. Last checked 10 min ago. It exposes 4 tools.

Explore FCC ULS licenses, ASR antenna structures, and microwave path elevation profiles.

The linked repository no longer exists on GitHub — it was deleted or made private.

Uptime history 39 hours of history
39 hours agonow
100.0%
Uptime 24h
91 of 91 checks
4
Tools
read from the server
599 ms
Response time
average over 24h
open, no key
Access
streamable-http

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 10 min ago.

run in your terminal
claude mcp add api --transport http https://fccdb.com/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "api": {
      "url": "https://fccdb.com/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.api]
url = "https://fccdb.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "api": {
      "url": "https://fccdb.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "api": {
      "url": "https://fccdb.com/mcp"
    }
  }
}

Available tools 4

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

license
license_detail
Full data for a single FCC license by call sign — licensee, locations with coordinates, antennas, paths, frequencies. Returns Markdown.
path
path_profile
Metadata for a single microwave path on a license. Identified by the ULS USI (per-license integer) and the path number within that license. The HTML page has an SVG elevation chart with terrain + line of sight + Fresnel zone; the Markdown response carries the endpoints, length, and frequency but not the chart.
search
search
Free-text search across FCC call signs and licensee entity names. Returns up to 50 hits. Use this when the user names a callsign or company but you don't know the exact identifier yet.
tower
tower_detail
Full data for an antenna structure by ASR registration number — owner, location, height, declared licensees on the tower, microwave paths terminating there, and licensees within 50 m by spatial proximity. Returns Markdown.

Endpoints

URLTransportStateLatencyChecked
https://fccdb.com/mcp streamable-http answering 576 ms 10 min ago

fccdb — questions

Answers built from our own checks of this server.

What can fccdb do?
It exposes 4 tools, read directly from the server on our last check. Among them: license_detail, path_profile, search, tower_detail. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is fccdb working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 599 ms. The bar chart above shows every period we have measured.
Is fccdb still maintained?
The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.
How do I connect fccdb?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does fccdb need an API key?
No. fccdb completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 4 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is fccdb?
It answers our handshake in 599 ms on average, which is faster than 16% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.