Is the Grip Arbiter MCP server down?

mcp-registry/fyi.grip/arbiter · v1.0.2

healthy
Last checked 2026-10-23 04:43 UTC · handshake 984ms

As of 2026-10-23 04:43 UTC, the Grip Arbiter MCP server is up with a Glimind reliability score of 63/100 (grade C). Over the last 30 days it answered 97.1% of Glimind's liveness checks. It had 105 outages in 90 days, with a median recovery of 7 minutes.

uptime (30d checks)
97.1%
checks observed
4,155
outages (90d)
105
tools
2

Decision arbitration, action routing, workflow control, deployment remediation, persistent memory.

Install Grip Arbiter MCP server

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http grip-arbiter-mcp-server https://api.grip.fyi/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "grip-arbiter-mcp-server": {
      "type": "http",
      "url": "https://api.grip.fyi/mcp"
    }
  }
}

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

Agent-readiness: B (81/100)

B (81/100): 0 error(s), 3 warning(s) across 2 tool(s); ~556 tokens of tool definitions.
Scores higher than 35% of 15,585 MCP servers Glimind has audited.
Its tool list costs an agent ~556 tokens per session — lighter than 90% of servers.
79 → 81 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions100
Safety hints30
Token cost100
Client compatibility70
Protocol100
Reliability60
Stability100

What to fix (4)

2 of 2 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: arbiter_compare, arbiter_embed

Reachable 97.1% of the time over the last 30 days; median recovery 7 min.

Agents fail over to an alternative the first time a call fails. Add health checks and restart-on-failure, and avoid cold starts on serverless hosts.

Handshake + tools/list takes ~1,907 ms.

Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.

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. All of them as JSON: /v1/readiness/mcp-registry%2Ffyi.grip%2Farbiter/fixes

arbiter_compare 1 change
{
  "name": "arbiter_compare",
  "description": "Paid ARBITER finite-candidate measurement for contextual choice. Use when a caller already has an explicit candidate field and needs it ordered against a query, current state, intent, context, question, or perspective. query is the situation to measure. candidates is the finite caller-supplied field to order. top_k optionally limits returned results. Returns MCP text content containing the JSON result from POST /v1/compare with the supplied candidates ordered by measured coherence. Does not gene",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "query",
      "candidates"
    ],
    "properties": {
      "query": {
        "type": "string",
        "description": "Current state, context, intent, question, or perspective to measure against the candidate field."
      },
      "top_k": {
        "type": "integer",
        "maximum": 9007199254740991,
        "minimum": 1,
        "description": "Optional maximum number of highest-ranked candidates to return."
      },
      "candidates": {
        "type": "array",
        "items": {
          "type": "string"
        },
        "minItems": 1,
        "description": "Finite caller-supplied candidate field to order. ARBITER measures these candidates and does not generate them."
      }
    }
  },
  "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/fyi.grip/arbiter"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/fyi.grip/arbiter"}) 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%2Ffyi.grip%2Farbiter.svg)](https://glimind.com/server/mcp-registry%2Ffyi.grip%2Farbiter?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Ffyi.grip%2Farbiter?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Ffyi.grip%2Farbiter.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Ffyi.grip%2Farbiter.svg
   :target: https://glimind.com/server/mcp-registry%2Ffyi.grip%2Farbiter?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:dd85bd858c0700a8…, first seen 2026-10-17, included at leaf 5097 of 50,054. Version history · verify what your client received.

Tools (2)

Compare: most reliable ml 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 Grip Arbiter MCP server down right now?

As of 2026-10-23 04:43 UTC, the Grip Arbiter MCP server is up with a Glimind reliability score of 63/100 (grade C). Over the last 30 days it answered 97.1% of Glimind's liveness checks. It had 105 outages in 90 days, with a median recovery of 7 minutes.

How many tools does Grip Arbiter MCP server provide?

Grip Arbiter MCP server advertises 2 tools, including arbiter_compare, arbiter_embed.

How do I install Grip Arbiter MCP server?

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

Is the Grip Arbiter MCP server safe to connect to an AI agent?

Glimind scanned all 2 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 Grip Arbiter 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