Is the Exascale Osint MCP server down?

mcp-registry/build.exascale/osint · v1.0.0

As of 2026-10-23 14:21 UTC, the Exascale Osint MCP server is up with a Glimind reliability score of 93/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 7 outages in 90 days, with a median recovery of 7 minutes.

US ISO interconnection queues and cited energy data. 25 free queries, then $49/mo or $490/yr.

claude mcp add --transport http exascale-osint-mcp-server https://api.exascale.build/mcp

{
  "mcpServers": {
    "exascale-osint-mcp-server": {
      "type": "http",
      "url": "https://api.exascale.build/mcp"
    }
  }
}

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

Agent-readiness: B (87/100)

What to fix (2)

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/build.exascale/osint"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/build.exascale/osint"}) over MCP.

Passed

• Every tool has a well-formed, typed input schema.
• Every tool declares whether it is read-only or destructive.
• No tool-poisoning patterns (hidden characters, instruction overrides, concealment, secret access, tool shadowing).
• Tool names are unique and portable across clients.
• Speaks MCP 2025-06-18.
• 99.98% uptime over 30 days.
• No breaking contract changes in 30 days.

Largest tool definitions

• query_capability_v1 ~234 tokens
• query_ai_infrastructure_construction_v1 ~214 tokens
• query_power_interconnection_queue_pjm_cycle_v1 ~214 tokens
• query_ai_infrastructure_equipment_trade_v1 ~213 tokens
• query_natural_gas_prices_v1 ~213 tokens

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:

[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fbuild.exascale%2Fosint.svg)](https://glimind.com/server/mcp-registry%2Fbuild.exascale%2Fosint?ref=badge)

<a href="https://glimind.com/server/mcp-registry%2Fbuild.exascale%2Fosint?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fbuild.exascale%2Fosint.svg" alt="MCP agent-readiness"></a>

.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fbuild.exascale%2Fosint.svg
   :target: https://glimind.com/server/mcp-registry%2Fbuild.exascale%2Fosint?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:a310b49692bd73d7…, first seen 2026-10-17, included at leaf 1466 of 52,546. Version history · verify what your client received.

Tools (66)

• describe_ai_infrastructure_construction_v1
• describe_ai_infrastructure_equipment_trade_v1
• describe_ai_infrastructure_production_v1
• describe_ai_infrastructure_trade_v1
• describe_capability_v1
• describe_capacity_factor_v1
• describe_natural_gas_prices_v1
• describe_power_asset_ownership_v1
• describe_power_capacity_accreditation_miso_v1
• describe_power_capacity_accreditation_pjm_v1
• describe_power_capacity_market_miso_v1
• describe_power_capacity_market_pjm_v1
• describe_power_capacity_v1
• describe_power_demand_rollup_v1
• describe_power_demand_v1
• describe_power_fuel_cost_v1
• describe_power_generation_v1
• describe_power_interconnection_queue_caiso_v1
• describe_power_interconnection_queue_ercot_v1
• describe_power_interconnection_queue_isone_v1
• describe_power_interconnection_queue_nyiso_v1
• describe_power_interconnection_queue_pjm_cycle_v1
• describe_power_interconnection_queue_pjm_v1
• describe_power_interconnection_queue_spp_v1
• describe_power_interconnection_queue_v1
• describe_power_plant_costs_v1
• describe_power_price_ercot_v1
• describe_power_retail_sales_v1
• describe_robotics_adoption_v1
• describe_robotics_trade_v1
• describe_space_satellite_filings_v1
• describe_space_satellite_notices_v1
• get_source_evidence_v1
• list_capabilities_v1
• query_ai_infrastructure_construction_v1
• query_ai_infrastructure_equipment_trade_v1
• query_ai_infrastructure_production_v1
• query_ai_infrastructure_trade_v1
• query_capability_v1
• query_capacity_factor_v1
• query_natural_gas_prices_v1
• query_power_asset_ownership_v1
• query_power_capacity_accreditation_miso_v1
• query_power_capacity_accreditation_pjm_v1
• query_power_capacity_market_miso_v1
• query_power_capacity_market_pjm_v1
• query_power_capacity_v1
• query_power_demand_rollup_v1
• query_power_demand_v1
• query_power_fuel_cost_v1
• query_power_generation_v1
• query_power_interconnection_queue_caiso_v1
• query_power_interconnection_queue_ercot_v1
• query_power_interconnection_queue_isone_v1
• query_power_interconnection_queue_nyiso_v1
• query_power_interconnection_queue_pjm_cycle_v1
• query_power_interconnection_queue_pjm_v1
• query_power_interconnection_queue_spp_v1
• query_power_interconnection_queue_v1
• query_power_plant_costs_v1
• query_power_price_ercot_v1
• query_power_retail_sales_v1
• query_robotics_adoption_v1
• query_robotics_trade_v1
• query_space_satellite_filings_v1
• query_space_satellite_notices_v1

Compare: most reliable data servers · most reliable knowledge servers · most reliable search servers

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

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

FAQ

Is the Exascale Osint MCP server down right now?

As of 2026-10-23 14:21 UTC, the Exascale Osint MCP server is up with a Glimind reliability score of 93/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 7 outages in 90 days, with a median recovery of 7 minutes.

How many tools does Exascale Osint MCP server provide?

Exascale Osint MCP server advertises 66 tools, including describe_ai_infrastructure_construction_v1, describe_ai_infrastructure_equipment_trade_v1, describe_ai_infrastructure_production_v1, describe_ai_infrastructure_trade_v1, describe_capability_v1.

How do I install Exascale Osint MCP server?

Point your MCP client at this streamable-http endpoint: https://api.exascale.build/mcp

Is the Exascale Osint MCP server safe to connect to an AI agent?

Glimind scanned all 66 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 Exascale Osint 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.