Is the FirmOps MCP server down?

mcp-registry/io.firmops/firmops · v1.0.0

One MCP connection for every live tool. Your agent finds the right tool and calls it through Glimind, and skips servers that are down. Free, no signup.Add to CursorVS CodeAdd to Claude Code copies a terminal command claude mcp add --transport http glimind https://glimind.com/mcp?ref=install-server. Other clients
healthy
Last checked 2026-11-22 12:35 UTC · handshake 91ms

As of 2026-11-22 12:35 UTC, the FirmOps MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

uptime (30d checks)
100%
checks observed
836
outages (90d)
0
tools
93

Managed firm-brain MCP for law firms: Clio matters, intake, calendar, and calls over OAuth.

Point your MCP client at this streamable-http endpoint: https://mcp.firmops.io/mcp

Agent-readiness: B (80/100)

B (80/100): 0 error(s), 3 warning(s) across 93 tool(s); ~20,936 tokens of tool definitions.
Scores higher than 24% of 27,585 MCP servers Glimind has audited.
Its tool list costs an agent ~20,936 tokens per session — more than 95% of servers.
80 → 80 since 2026-11-16
no tool-poisoning patterns
Descriptions89
Safety hints100
Schemas100
Protocol100
Stability20
Token cost35
Reliability100
Client compatibility70

What to fix (5)

93 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 →

4 parameter(s) across 1 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: create_intake_link

Loading this server's tool list costs an agent ~20,936 tokens before any work — more than 95% 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 →

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 55 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 →

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

Agents: watch_tool({"toolId": "mcp-registry/io.firmops/firmops"}) 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.

Badge for your README

Shows whether the server is live and its agent-readiness score; it updates within the hour.

MCP server status

Markdown
[![MCP server status](https://glimind.com/badge/mcp-registry%2Fio.firmops%2Ffirmops.svg)](https://glimind.com/server/mcp-registry%2Fio.firmops%2Ffirmops?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fio.firmops%2Ffirmops?ref=badge"><img src="https://glimind.com/badge/mcp-registry%2Fio.firmops%2Ffirmops.svg" alt="MCP server status"></a>

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:12939f604c71a7f8…, first seen 2026-11-19, included at leaf 353100 of 383,757. Version history · verify what your client received.

Tools (93)

Compare: most reliable productivity servers · most reliable payments servers · most reliable calendar servers · most reliable files servers · most reliable communication 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?ref=install-server

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp?ref=install-server"
    }
  }
}

FAQ

Is the FirmOps MCP server down right now?

As of 2026-11-22 12:35 UTC, the FirmOps MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

How many tools does FirmOps MCP server provide?

FirmOps MCP server advertises 93 tools, including add_portal_packet, cancel_intake_link, create_calendar_event, create_dropbox_file_request, create_dropbox_folder.

How do I install FirmOps MCP server?

Point your MCP client at this streamable-http endpoint: https://mcp.firmops.io/mcp

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

Glimind scanned all 93 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 FirmOps 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