Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

FCC License Search

REMOTE · FCC-LICENSE-SEARCH.KRIMSKRAMS.XYZ

Search FCC radio licenses by company, call sign, or FRN; monitor status changes and snapshots.

−1 this week 73 Trust /100

Last scanned (18 hours ago)

Scores higher than 60% of remote servers

Reachable. Last reached 4 Nov 2026.

Category IoT and Hardware

Trust breakdown (7 categories)

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
Transport & Reachability100
Schema Quality & AI Usability59
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 434 tokens (~62/item across 7 items; 7 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
  • Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Changelog

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.

  • 4 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 28 Sept 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 Sept 26 0
    • Stability: 0.97 → pass security
  • 25 Sept 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
  • 29 Aug 26 0
    • Tool “fcc_company” rewrote its description, which is the text the model reads security
    • Stability: unverified → 0.03 ▲ functional
  • 28 Aug 26 0

    First indexed and scored.

Diagnostics

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 4 Nov 2026 · Probed https://fcc-license-search.krimskrams.xyz/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=fcc-license-search.krimskrams.xyz CN=YE1,O=Let's Encrypt,C=US 23 Oct 2026 21 Jan 2027 ECDSA 256 ECDSA-SHA384 6987649c98692bc430101a2122f5f0f57a2
SANs: fcc-license-search.krimskrams.xyz
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
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 fcc-license-search.krimskrams.xyz. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
xyz. present 3599, 18130 8, 8 Verified
krimskrams.xyz. 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=31536000; includeSubDomains
x-content-type-options nosniff
x-frame-options DENY

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://fcc-license-search.krimskrams.xyz/mcp Verified 200
http (plaintext) http://fcc-license-search.krimskrams.xyz/mcp HTTPS enforced 308 https://fcc-license-search.krimskrams.xyz/mcp
MCP tools · 7 exposed · ~434 tokens

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 →

Tool Tokens
fcc_changes ~87

Find FCC radio licence status changes since a date, filtered by frn, callsign, or service. Receive JSON records with usi, callsign, old_status, new_status, observed_date, and source_file. The since period is at most 31 days.

NameTypeReqDescription
callsign–––
frn–––
service–––
sincestringyes–

No output schema declared.

No examples provided.

fcc_company ~116

Company enrichment: return the radio-licence footprint for a named company. The data contains FCC radio licences only. Receive matched licensee entities, every matching licence up to the selected limit, licence dates and status, summary counts for all matches, the soonest upcoming expiry, store coverage, and FCC source provenance for every block as JSON.

NameTypeReqDescription
company_namestringyes–
include_expiredboolean––
limitinteger––
service–––
state–––
status–––

No output schema declared.

No examples provided.

fcc_coverage ~21

Read the current FCC ULS data coverage and provenance.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

fcc_search ~99

Look up FCC radio licences with q as a company or licensee name, call sign, or FRN. Optional service, status, and limit inputs filter the results. Receive up to 20 JSON records with callsign, licensee_name, frn, service, status, grant_date, expired_date, and cancellation_date.

NameTypeReqDescription
limitinteger––
qstringyes–
service–––
status–––

No output schema declared.

No examples provided.

fcc_snapshot ~72

Download one FCC radio licence snapshot by slice_id from /v1/snapshots. Receive as_of, row_count, source, licence, and all rows with company name, call sign, FRN, service, status, grant, expiry, and cancellation dates as JSON.

NameTypeReqDescription
slice_idstringyes–

No output schema declared.

No examples provided.

fcc_snapshots ~19

List the free FCC ULS snapshot catalog.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

fcc_stats ~20

Read free FCC ULS data statistics and ingest freshness.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Install

How do I install the FCC License Search MCP server?

FCC License Search is a hosted endpoint at https://fcc-license-search.krimskrams.xyz/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 · fcc-license-search.krimskrams.xyz

# add to Claude Code
claude mcp add --transport http xyz-krimskrams-fcc-license-search 'https://fcc-license-search.krimskrams.xyz/mcp'
Common questions

What is the FCC License Search MCP server?

FCC License Search is an MCP server listed in the public MCP registry as xyz.krimskrams/fcc-license-search. Search FCC radio licenses by company, call sign, or FRN; monitor status changes and snapshots. This page covers its hosted endpoint (https://fcc-license-search.krimskrams.xyz/mcp).

Is the FCC License Search MCP server safe to use?

FCC License Search scores 73 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 FCC License Search MCP server expose?

FCC License Search exposes 7 tools: fcc_search, fcc_company, fcc_changes, fcc_stats, fcc_coverage, and 2 more. Their descriptions and schemas cost roughly 434 tokens of context every time the server is loaded.

Does the FCC License Search MCP server require authentication?

No. We connected to FCC License Search without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the FCC License Search MCP server still maintained?

FCC License Search is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.