# Fccdb MCP server

Agent View of the PolicyLayer registry record for Fccdb: identity, probed posture, risk grade, and all 4 tools classified. HTML page: https://policylayer.com/tools/com-fccdb-api

## Facts

- Server id: `https://fccdb.com/mcp`
- Homepage: https://github.com/benlemasurier/fccdb
- Registry record: grade C, identity unverified
- Lifecycle: active
- Auth posture: open
- Rate-limited: no
- Tools: 4 (4 with introspected schema)
- Tool categories present: Read
- Context-window cost: 374 tokens per request — https://policylayer.com/token-cost/com-fccdb-api
- Tags: com fccdb api
- Record last modified: 2026-08-17T19:20:48.256Z

## Tools (4)

| Tool | Category | Risk | Record |
| --- | --- | --- | --- |
| `license_detail` | Read | Low | https://policylayer.com/tools/com-fccdb-api/license-detail.md |
| `path_profile` | Read | Low | https://policylayer.com/tools/com-fccdb-api/path-profile.md |
| `search` | Read | Low | https://policylayer.com/tools/com-fccdb-api/search.md |
| `tower_detail` | Read | Low | https://policylayer.com/tools/com-fccdb-api/tower-detail.md |

## Tool descriptions

- `license_detail` — Full data for a single FCC license by call sign — licensee, locations with coordinates, antennas, paths, frequencies. Returns Markdown.
- `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 Markdow…
- `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_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.

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=com-fccdb-api · API: https://policylayer.com/registry/api · Recommended policies for every tool: https://policylayer.com/policies/com-fccdb-api