Is the Ostorlab MCP server down?

mcp-registry/co.ostorlab/mcp · v1.29.1

healthy
Last checked 2026-10-26 22:34 UTC · handshake 198ms

As of 2026-10-26 22:34 UTC, the Ostorlab MCP server is up with a Glimind reliability score of 85/100 (grade B). Over the last 30 days it answered 100% of Glimind's liveness checks.

uptime (30d checks)
100%
checks observed
68
outages (90d)
0
tools
268

Query and act on your Ostorlab scans, vulnerabilities, tickets and assets.

Point your MCP client at this streamable-http endpoint: https://api.ostorlab.co/apis/mcp/{api_key}/

Agent-readiness: C (71/100)

C (71/100): 1 error(s), 3 warning(s) across 268 tool(s); ~84,931 tokens of tool definitions.
Scores higher than 5% of 15,781 MCP servers Glimind has audited.
Its tool list costs an agent ~84,931 tokens per session — more than 99% of servers.
no tool-poisoning patterns
Schemas100
Descriptions30
Safety hints100
Token cost0
Client compatibility100
Protocol100
Reliability100
Stability100

What to fix (4)

Loading this server's tool list costs an agent ~84,931 tokens before any work — more than 99% of MCP servers.

Split rarely-used tools into a separate server or a toolset the client can enable, or expose one "search tools" entry point. Many agents load every connected server's tools into every request. How to fix →

7 tool definition(s) exceed ~1,200 tokens each (largest: create_multi_asset_scan, ~2,302).

Move long reference material out of descriptions (link a doc or expose a resource), drop repeated examples, and collapse large enums. Trimming these to ~600 tokens saves ~7,313 tokens every session. How to fix →

Tools: create_multi_asset_scan, ai_remediation_create_ticket_rule, create_source_code_scan, create_mobile_file_scan, create_mobile_testflight_scan and 2 more · saves ~7,313 tokens/session

268 tools on one server. Tool-selection accuracy drops as the menu grows, and some clients (e.g. Cursor) cap the number of active tools.

Group tools by task into smaller servers or toolsets, and merge near-duplicates behind one tool with a mode parameter. How to fix →

1096 parameter(s) across 247 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: accept_autodiscovery_asset, acknowledge_alerts, add_tag, add_user, ai_remediation_add_agent_mcp_server and 242 more

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/co.ostorlab/mcp"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/co.ostorlab/mcp"}) 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%2Fco.ostorlab%2Fmcp.svg)](https://glimind.com/server/mcp-registry%2Fco.ostorlab%2Fmcp?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fco.ostorlab%2Fmcp?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fco.ostorlab%2Fmcp.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fco.ostorlab%2Fmcp.svg
   :target: https://glimind.com/server/mcp-registry%2Fco.ostorlab%2Fmcp?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:bdf0a4d604ccce5e…, first seen 2026-10-26, included at leaf 74544 of 75,855. Version history · verify what your client received.

Tools (268)

Compare: most reliable data servers · most reliable communication servers · most reliable other servers · most reliable security servers · most reliable devops 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 Ostorlab MCP server down right now?

As of 2026-10-26 22:34 UTC, the Ostorlab MCP server is up with a Glimind reliability score of 85/100 (grade B). Over the last 30 days it answered 100% of Glimind's liveness checks.

How many tools does Ostorlab MCP server provide?

Ostorlab MCP server advertises 268 tools, including accept_autodiscovery_asset, acknowledge_alerts, add_tag, add_user, ai_remediation_add_agent_mcp_server.

How do I install Ostorlab MCP server?

Point your MCP client at this streamable-http endpoint: https://api.ostorlab.co/apis/mcp/{api_key}/

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

Glimind scanned all 268 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 Ostorlab 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