Is the Openmark MCP server down?

mcp-registry/ai.openmark/openmark · v1.0.0

healthy
Last checked 2026-10-26 18:00 UTC · handshake 500ms

As of 2026-10-26 18:00 UTC, the Openmark MCP server is up with a Glimind reliability score of 99/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

uptime (30d checks)
100%
checks observed
2,057
outages (90d)
0
tools
9

Benchmark your own prompt on 100+ LLMs with real API calls; pick the cheapest model that passes.

Point your MCP client at this streamable-http endpoint: https://openmark.ai/mcp

Agent-readiness: C (71/100)

C (71/100): 0 error(s), 3 warning(s) across 9 tool(s); ~2,413 tokens of tool definitions.
Scores higher than 5% of 15,768 MCP servers Glimind has audited.
Its tool list costs an agent ~2,413 tokens per session — more than 50% of servers.
75 → 71 since 2026-10-18
no tool-poisoning patterns
Schemas100
Descriptions67
Safety hints2
Token cost100
Client compatibility70
Protocol100
Reliability100
Stability44

What to fix (5)

9 of 9 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: estimate_cost, get_account, get_results, get_task_format, list_models and 4 more

3 parameter(s) across 3 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: estimate_cost, get_results, watch_task

2 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.

Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →

Tools: estimate_cost, run_benchmark

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 →

In the last 30 days: 0 tool(s) removed and 14 schema change(s).

Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →

Auto-fix: 7 corrected tool definitions

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

estimate_cost 1 change
{
  "name": "estimate_cost",
  "description": "Credits a run_benchmark call would use, before spending anything: the expected total, the split per model, the balance needed to start, the worst case, and the user's balance. Same inputs and run settings as run_benchmark. Use it to drop an expensive model, or to compare settings (e.g. max_tokens), before running.",
  "inputSchema": {
    "type": "object",
    "required": [
      "task_yaml",
      "models"
    ],
    "properties": {
      "models": {
        "type": "array",
        "items": {
          "type": "string"
        },
        "maxItems": 20,
        "minItems": 1
      },
      "preset": {
        "enum": [
          "standard",
          "thorough"
        ],
        "type": "string",
        "description": "Like the app's presets: standard = 2 passes + snappy timeouts (the default), thorough = 3 passes + patient timeouts. Explicit stability_runs / timeout_profile override it"
      },
      "fail_fast": {
        "type": "boolean",
        "default": true,
        "description": "Stop a model after repeated errors to save credits. Set false to let every model finish, e.g. to diagnose failures"
      },
      "task_yaml": {
        "type": "string",
        "description": "The full task YAML (a JSON object with the same fields also works)"
      },
      "max_tokens": {
        "type": "integer",
        "default": 500,
        "maximum": 16000,
        "minimum": 0,
        "description": "Output token limit per answer, 16 to 16000; 0 = no limit. Keep the default unless results show it was too low: a higher limit raises the credits needed to start. get_results flags models whose answers came back empty or near the limit; re-run those with a higher value"
      },
      "upload_uid": {
        "type": "string",
        "description": "From prepare_attachments, so image and document tokens are counted"
      },
      "custom_timeout": {
        "type": "integer",
        "maximum": 600,
        "minimum": 120,
        "description": "Seconds per answer, with timeout_profile custom"
      },
      "stability_runs": {
        "type": "integer",
        "default": 2,
        "maximum": 5,
        "minimum": 1,
        "description": "Passes per model; 2+ shows which models are consistent"
      },
      "temp_preference": {
        "enum": [
          "low",
          "high"
        ],
        "type": "string",
        "default": "low",
        "description": "With temperature_discovery: which temperature wins a tie"
      },
      "timeout_profile": {
        "enum": [
          "snappy",
          "patient",
          "custom"
        ],
        "type": "string",
        "default": "snappy",
        "description": "How long to wait per answer: snappy 45s, patient 90s, custom = custom_timeout"
      },
      "temperature_discovery": {
        "type": "boolean",
        "default": false,
        "description": "Find each model's best temperature for this task. Costs about 6x as much"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  },
  "title": "Estimate a run's cost"
}
get_account 1 change
{
  "name": "get_account",
  "description": "The user's plan, credit balance and limits, and what a credit pack, Pro or Expert would unlock. Use it before large runs, or when a run is refused for credits or limits.",
  "inputSchema": {
    "type": "object",
    "properties": {}
  },
  "annotations": {
    "readOnlyHint": true
  },
  "title": "Account, credits and plans"
}
get_results 1 change
{
  "name": "get_results",
  "description": "Status of a benchmark job, and once completed the ranked results (score, stability, cost per run, latency), the tests each model missed with its answer, a recommendation for the chosen objective and quick picks for the others.",
  "inputSchema": {
    "type": "object",
    "required": [
      "job_id"
    ],
    "properties": {
      "job_id": {
        "type": "string"
      },
      "tolerance": {
        "type": "number",
        "default": 2,
        "maximum": 50,
        "minimum": 0,
        "description": "Score points below the top score that still count as good enough"
      },
      "show_misses": {
        "type": "boolean",
        "default": true,
        "description": "List the tests each model got wrong, with the expected answer and the model's reply"
      },
      "optimize_for": {
        "enum": [
          "accuracy",
          "cost",
          "speed",
          "stability"
        ],
        "type": "string",
        "default": "accuracy",
        "description": "accuracy (same order as the app's results table): best score, then cheapest, then fastest. cost / speed / stability: cheapest / fastest / most consistent model within `tolerance` points of the top score"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  },
  "title": "Get benchmark results"
}

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/ai.openmark/openmark"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/ai.openmark/openmark"}) 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%2Fai.openmark%2Fopenmark.svg)](https://glimind.com/server/mcp-registry%2Fai.openmark%2Fopenmark?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fai.openmark%2Fopenmark?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fai.openmark%2Fopenmark.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fai.openmark%2Fopenmark.svg
   :target: https://glimind.com/server/mcp-registry%2Fai.openmark%2Fopenmark?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:d142eb42bba2993b…, first seen 2026-10-20, included at leaf 33740 of 74,589. Version history · verify what your client received.

Tools (9)

Compare: most reliable other servers · most reliable ml servers · most reliable knowledge servers · most reliable files servers · most reliable code 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 Openmark MCP server down right now?

As of 2026-10-26 18:00 UTC, the Openmark MCP server is up with a Glimind reliability score of 99/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

How many tools does Openmark MCP server provide?

Openmark MCP server advertises 9 tools, including estimate_cost, get_account, get_results, get_task_format, list_models.

How do I install Openmark MCP server?

Point your MCP client at this streamable-http endpoint: https://openmark.ai/mcp

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

Glimind scanned all 9 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 Openmark 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