Is the Relmcrm Relm MCP server down?

mcp-registry/com.relmcrm/relm · v0.17.1

healthy
Last checked 2026-10-19 06:22 UTC · handshake 591ms

As of 2026-10-19 06:22 UTC, the Relmcrm Relm MCP server is up with a Glimind reliability score of 77/100 (grade B). Over the last 30 days it answered 99.7% of Glimind's liveness checks. It had 32 outages in 90 days, with a median recovery of 5 minutes.

uptime (30d checks)
99.7%
checks observed
3,802
outages (90d)
32
tools
41

API-first CRM for LLMs - contacts, companies, deals and activities over a native MCP server.

Install Relmcrm Relm MCP server

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http relmcrm-relm-mcp-server https://api.relmcrm.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "relmcrm-relm-mcp-server": {
      "type": "http",
      "url": "https://api.relmcrm.com/mcp"
    }
  }
}

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

Agent-readiness: C (77/100)

C (77/100): 0 error(s), 3 warning(s) across 41 tool(s); ~4,324 tokens of tool definitions.
Scores higher than 29% of 15,341 MCP servers Glimind has audited.
Its tool list costs an agent ~4,324 tokens per session — more than 55% of servers.
77 → 77 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions35
Safety hints100
Token cost75
Client compatibility70
Protocol100
Reliability85
Stability100

What to fix (4)

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

87 parameter(s) across 32 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: relm_batch, relm_connect_channel, relm_create, relm_create_automation, relm_create_enum_value and 27 more

Handshake + tools/list takes ~2,756 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 →

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/com.relmcrm/relm"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/com.relmcrm/relm"}) 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%2Fcom.relmcrm%2Frelm.svg)](https://glimind.com/server/mcp-registry%2Fcom.relmcrm%2Frelm?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fcom.relmcrm%2Frelm?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.relmcrm%2Frelm.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.relmcrm%2Frelm.svg
   :target: https://glimind.com/server/mcp-registry%2Fcom.relmcrm%2Frelm?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:bae0709947d22363…, first seen 2026-10-17, included at leaf 945 of 25,235. Version history · verify what your client received.

Tools (41)

Compare: most reliable knowledge servers · most reliable data servers · most reliable communication servers · most reliable automation servers · most reliable web 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 Relmcrm Relm MCP server down right now?

As of 2026-10-19 06:22 UTC, the Relmcrm Relm MCP server is up with a Glimind reliability score of 77/100 (grade B). Over the last 30 days it answered 99.7% of Glimind's liveness checks. It had 32 outages in 90 days, with a median recovery of 5 minutes.

How many tools does Relmcrm Relm MCP server provide?

Relmcrm Relm MCP server advertises 41 tools, including relm_automations_capabilities, relm_batch, relm_connect_channel, relm_create, relm_create_automation.

How do I install Relmcrm Relm MCP server?

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

Is the Relmcrm Relm MCP server safe to connect to an AI agent?

Glimind scanned all 41 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 Relmcrm Relm 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