Is the Olyport Fbi Nibrs MCP server down?

mcp-registry/com.olyport/fbi-nibrs · v1.27.0

healthy
Last checked 2026-10-17 07:26 UTC · handshake 324ms

As of 2026-10-17 07:26 UTC, the Olyport Fbi Nibrs MCP server is up with a Glimind reliability score of 98/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 2 minutes.

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

National crime incident estimates from NIBRS by offense type, weapon, and location

Install Olyport Fbi Nibrs MCP server

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http olyport-fbi-nibrs-mcp-server https://mcp.olyport.com/fbi-nibrs/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "olyport-fbi-nibrs-mcp-server": {
      "type": "http",
      "url": "https://mcp.olyport.com/fbi-nibrs/mcp"
    }
  }
}

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: C (76/100)

C (76/100): 0 error(s), 2 warning(s) across 4 tool(s); ~1,016 tokens of tool definitions.
Scores higher than 14% of 15,259 MCP servers Glimind has audited.
Its tool list costs an agent ~1,016 tokens per session — more than 25% of servers.
no tool-poisoning patterns
Schemas100
Descriptions30
Safety hints30
Token cost100
Client compatibility100
Protocol100
Reliability100
Stability100

What to fix (2)

13 parameter(s) across 4 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.

Tools: get_offense_estimates, get_property_incident_estimates, get_victimization_data, get_violent_incident_estimates

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.

Tools: get_offense_estimates, get_property_incident_estimates, get_victimization_data, get_violent_incident_estimates

Auto-fix: 4 corrected tool definitions

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

get_offense_estimates 1 change
{
  "name": "get_offense_estimates",
  "description": "Get NIBRS offense-level estimates (person or property crimes).\n\n    Returns offense-level data (as opposed to incident-level). An incident\n    may involve multiple offenses, so offense counts are typically higher\n    than incident counts.\n\n    Args:\n        crime_category: 'person' for violent crimes or 'property' for\n            property crimes. Default: 'person'.\n        indicator: Filter by offense type.\n        domain: Filter by analysis domain.\n        limit: Maximum results to return (defa",
  "inputSchema": {
    "type": "object",
    "title": "get_offense_estimatesArguments",
    "properties": {
      "limit": {
        "type": "integer",
        "title": "Limit",
        "default": 50
      },
      "domain": {
        "anyOf": [
          {
            "type": "string"
          },
          {
            "type": "null"
          }
        ],
        "title": "Domain",
        "default": null
      },
      "indicator": {
        "anyOf": [
          {
            "type": "string"
          },
          {
            "type": "null"
          }
        ],
        "title": "Indicator",
        "default": null
      },
      "crime_category": {
        "type": "string",
        "title": "Crime Category",
        "default": "person"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}
get_property_incident_estimates 1 change
{
  "name": "get_property_incident_estimates",
  "description": "Get national estimates of property crime incidents from NIBRS.\n\n    Returns weighted national estimates of crimes against property\n    including burglary, larceny-theft, motor vehicle theft, arson,\n    and fraud. Data includes breakdowns by location type, time of day,\n    and clearance status.\n\n    Args:\n        indicator: Filter by offense type (e.g. 'Burglary/Breaking & Entering',\n            'Larceny/Theft Offenses', 'Motor Vehicle Theft',\n            'NIBRS crimes against property (Total)').",
  "inputSchema": {
    "type": "object",
    "title": "get_property_incident_estimatesArguments",
    "properties": {
      "limit": {
        "type": "integer",
        "title": "Limit",
        "default": 50
      },
      "domain": {
        "anyOf": [
          {
            "type": "string"
          },
          {
            "type": "null"
          }
        ],
        "title": "Domain",
        "default": null
      },
      "indicator": {
        "anyOf": [
          {
            "type": "string"
          },
          {
            "type": "null"
          }
        ],
        "title": "Indicator",
        "default": null
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}
get_victimization_data 1 change
{
  "name": "get_victimization_data",
  "description": "Get NIBRS victimization counts and percentages.\n\n    Returns victim-level data from NIBRS including demographics of\n    victims, victim-offender relationships, and injury types. Useful\n    for understanding who is affected by crime and in what ways.\n\n    Args:\n        indicator: Filter by offense type (e.g. 'Aggravated Assault',\n            'NIBRS crimes against persons (Total)').\n        domain: Filter by analysis domain (e.g. 'Victim-offender relationship',\n            'Injury', 'Age', 'Sex', ",
  "inputSchema": {
    "type": "object",
    "title": "get_victimization_dataArguments",
    "properties": {
      "limit": {
        "type": "integer",
        "title": "Limit",
        "default": 50
      },
      "domain": {
        "anyOf": [
          {
            "type": "string"
          },
          {
            "type": "null"
          }
        ],
        "title": "Domain",
        "default": null
      },
      "indicator": {
        "anyOf": [
          {
            "type": "string"
          },
          {
            "type": "null"
          }
        ],
        "title": "Indicator",
        "default": null
      }
    }
  },
  "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.olyport/fbi-nibrs"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/com.olyport/fbi-nibrs"}) 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.olyport%2Ffbi-nibrs.svg)](https://glimind.com/server/mcp-registry%2Fcom.olyport%2Ffbi-nibrs?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fcom.olyport%2Ffbi-nibrs?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.olyport%2Ffbi-nibrs.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.olyport%2Ffbi-nibrs.svg
   :target: https://glimind.com/server/mcp-registry%2Fcom.olyport%2Ffbi-nibrs?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:80655660ef04e2ea…, first seen 2026-10-17, included at leaf 12134 of 17,120. Version history · verify what your client received.

Tools (4)

Compare: most reliable data 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 Olyport Fbi Nibrs MCP server down right now?

As of 2026-10-17 07:26 UTC, the Olyport Fbi Nibrs MCP server is up with a Glimind reliability score of 98/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 2 minutes.

How many tools does Olyport Fbi Nibrs MCP server provide?

Olyport Fbi Nibrs MCP server advertises 4 tools, including get_offense_estimates, get_property_incident_estimates, get_victimization_data, get_violent_incident_estimates.

How do I install Olyport Fbi Nibrs MCP server?

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

Is the Olyport Fbi Nibrs 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 Olyport Fbi Nibrs 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.