Is the Fccdb MCP server down?

mcp-registry/com.fccdb/api · v0.1.0

healthy
Last checked 2026-10-27 01:58 UTC · handshake 70ms

As of 2026-10-27 01:58 UTC, the Fccdb MCP server is up with a Glimind reliability score of 97/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 3 outages in 90 days, with a median recovery of 7 minutes.

uptime (30d checks)
100%
checks observed
4,966
outages (90d)
3
tools
4

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

Point your MCP client at this streamable-http endpoint: https://fccdb.com/mcp

Agent-readiness: B (80/100)

B (80/100): 0 error(s), 2 warning(s) across 4 tool(s); ~477 tokens of tool definitions.
Scores higher than 18% of 15,771 MCP servers Glimind has audited.
Its tool list costs an agent ~477 tokens per session — lighter than 95% of servers.
78 → 80 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions73
Safety hints30
Token cost100
Client compatibility70
Protocol100
Reliability100
Stability100

What to fix (3)

4 of 4 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →

Tools: license_detail, path_profile, search, tower_detail

1 parameter(s) across 1 tool(s) have no description.

Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →

Tools: search

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →

Auto-fix: 1 corrected tool definition

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 1 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.fccdb%2Fapi/fixes

search 1 change
{
  "name": "search",
  "description": "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.",
  "inputSchema": {
    "type": "object",
    "required": [
      "q"
    ],
    "properties": {
      "q": {
        "type": "string",
        "description": "Search query"
      },
      "limit": {
        "type": "integer",
        "default": 20,
        "maximum": 50,
        "minimum": 1
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/com.fccdb/api"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/com.fccdb/api"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

Markdown
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.fccdb%2Fapi.svg)](https://glimind.com/server/mcp-registry%2Fcom.fccdb%2Fapi?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fcom.fccdb%2Fapi?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.fccdb%2Fapi.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.fccdb%2Fapi.svg
   :target: https://glimind.com/server/mcp-registry%2Fcom.fccdb%2Fapi?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:b42d6eb726b67c66…, first seen 2026-10-17, included at leaf 5775 of 76,719. Version history · verify what your client received.

Tools (4)

Compare: most reliable retrieval servers · most reliable search servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

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

FAQ

Is the Fccdb MCP server down right now?

As of 2026-10-27 01:58 UTC, the Fccdb MCP server is up with a Glimind reliability score of 97/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 3 outages in 90 days, with a median recovery of 7 minutes.

How many tools does Fccdb MCP server provide?

Fccdb MCP server advertises 4 tools, including license_detail, path_profile, search, tower_detail.

How do I install Fccdb MCP server?

Point your MCP client at this streamable-http endpoint: https://fccdb.com/mcp

Is the Fccdb MCP server safe to connect to an AI agent?

Glimind scanned all 4 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Fccdb MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.

Feedback
Help us improve