fccdb
REMOTE · FCCDB.COM · SCANNED SEP 22
Explore FCC ULS licenses, ASR antenna structures, and microwave path elevation profiles.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability77
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 337 tokens (~84/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage94
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 83% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the fccdb MCP server?
fccdb is a hosted endpoint at https://fccdb.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · fccdb.com
claude mcp add --transport http com-fccdb-api 'https://fccdb.com/mcp'
{
"mcpServers": {
"com-fccdb-api": {
"url": "https://fccdb.com/mcp"
}
}
} {
"servers": {
"com-fccdb-api": {
"type": "http",
"url": "https://fccdb.com/mcp"
}
}
} [mcp_servers.com-fccdb-api] url = "https://fccdb.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-fccdb-api": {
"type": "remote",
"url": "https://fccdb.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-fccdb-api --url 'https://fccdb.com/mcp' --transport streamable-http
mcp_servers:
com-fccdb-api:
url: "https://fccdb.com/mcp" {
"McpServers": {
"com-fccdb-api": {
"Transport": "http",
"Url": "https://fccdb.com/mcp"
}
}
} assistant mcp add com-fccdb-api -t streamable-http -u 'https://fccdb.com/mcp'
{
"mcpServers": {
"com-fccdb-api": {
"type": "http",
"url": "https://fccdb.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 26 Aug 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 0
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 22 Sept 2026 · Probed https://fccdb.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=fccdb.com | CN=YE2,O=Let's Encrypt,C=US | 31 Jul 2026 | 29 Oct 2026 | ECDSA 256 | ECDSA-SHA384 | 51abc90deb4f99a067848d0c0f9b469d410 |
| SANs: fccdb.com | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of fccdb.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| fccdb.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| content-security-policy | default-src 'self'; script-src 'self'; style-src 'self' 'unsafe-inline'; img-src 'self' data: blob: https://tiles.openfreemap.org; font-src 'self' data: https://tiles.openfreemap.org; connect-src 'self' https://tiles.openfreemap.org; worker-src 'self' blob:; child-src 'self' blob:; frame-ancestors 'none'; base-uri 'self'; form-action 'self'; object-src 'none' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | accelerometer=(), camera=(), geolocation=(), gyroscope=(), magnetometer=(), microphone=(), payment=(), usb=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://fccdb.com/mcp | Verified | 200 | |
| http (plaintext) | http://fccdb.com/mcp | HTTPS enforced | 308 | https://fccdb.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
license_detail ~53
Full data for a single FCC license by call sign — licensee, locations with coordinates, antennas, paths, frequencies. Returns Markdown.
| Name | Type | Req | Description |
|---|---|---|---|
| call_sign | string | yes | FCC call sign, e.g. KAC75 |
No output schema declared.
No examples provided.
path_profile ~102
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.
| Name | Type | Req | Description |
|---|---|---|---|
| path_number | integer | yes | Path number within the license |
| usi | integer | yes | ULS USI (license id) |
No output schema declared.
No examples provided.
search ~63
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| q | string | yes | Search query |
No output schema declared.
No examples provided.
tower_detail ~68
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.
| Name | Type | Req | Description |
|---|---|---|---|
| asr_number | integer | yes | 7-digit ASR registration number |
No output schema declared.
No examples provided.
What is the fccdb MCP server?
fccdb is an MCP server listed in the public MCP registry as com.fccdb/api. Explore FCC ULS licenses, ASR antenna structures, and microwave path elevation profiles. This page covers its hosted endpoint (https://fccdb.com/mcp).
Is the fccdb MCP server safe to use?
fccdb scores 81 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the fccdb MCP server expose?
fccdb exposes 4 tools: search, license_detail, tower_detail, path_profile. Their descriptions and schemas cost roughly 286 tokens of context every time the server is loaded.
Does the fccdb MCP server require authentication?
No. We connected to fccdb without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the fccdb MCP server still maintained?
fccdb is still listed as active in the MCP registry. We last reached this channel on 22 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.