Is the Benkaiser Mob Demo MCP server down?

mcp-registry/io.github.benkaiser/mob-demo · v0.1.0

healthy
Last checked 2026-10-23 19:52 UTC · handshake 1.2s

As of 2026-10-23 19:52 UTC, the Benkaiser Mob Demo MCP server is up with a Glimind reliability score of 81/100 (grade B). Over the last 30 days it answered 99.7% of Glimind's liveness checks. It had 87 outages in 90 days, with a median recovery of 4 minutes.

uptime (30d checks)
99.7%
checks observed
4,405
outages (90d)
87
tools
42

Ephemeral no-signup demo of Mob, an AI-first personal CRM you run in natural language.

Install Benkaiser Mob Demo MCP server

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http benkaiser-mob-demo-mcp-server https://demo.mobcrm.au/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "benkaiser-mob-demo-mcp-server": {
      "type": "http",
      "url": "https://demo.mobcrm.au/mcp"
    }
  }
}

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

Agent-readiness: C (76/100)

C (76/100): 0 error(s), 4 warning(s) across 42 tool(s); ~11,888 tokens of tool definitions.
Scores higher than 13% of 15,592 MCP servers Glimind has audited.
Its tool list costs an agent ~11,888 tokens per session — more than 85% of servers.
76 → 76 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions100
Safety hints3
Token cost75
Client compatibility70
Protocol100
Reliability85
Stability100

What to fix (5)

42 of 42 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: activity_list, activity_manage, activity_type_manage, address_manage, batch_create_activities and 37 more

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

9 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: batch_create_activities, batch_create_contacts, contact_create, contact_delete, contact_merge and 4 more

Handshake + tools/list takes ~1,722 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: 21 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.benkaiser%2Fmob-demo/fixes

activity_list 1 change
{
  "name": "activity_list",
  "description": "List activities, optionally filtered by contact or type. Add days_back or since for a chronological activity journal with participant names.",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "properties": {
      "page": {
        "type": "number",
        "description": "Page number (default: 1)"
      },
      "type": {
        "enum": [
          "phone_call",
          "video_call",
          "text_message",
          "in_person",
          "email",
          "activity",
          "other"
        ],
        "type": "string",
        "description": "Filter by interaction type"
      },
      "since": {
        "type": "string",
        "description": "Show activities since this ISO date (uses activity log mode with participant names)"
      },
      "per_page": {
        "type": "number",
        "description": "Results per page (default: 20)"
      },
      "days_back": {
        "type": "number",
        "maximum": 365,
        "minimum": 1,
        "description": "Look-back window in days (uses activity log mode with participant names). Ignored if since is provided."
      },
      "contact_id": {
        "type": "string",
        "description": "Filter by contact ID"
      },
      "sort_order": {
        "enum": [
          "asc",
          "desc"
        ],
        "type": "string",
        "description": "Sort direction by occurred_at (default: desc, only for activity log mode)"
      },
      "include_deleted": {
        "type": "boolean",
        "description": "Include soft-deleted activities in results (default: false)"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}
address_manage 1 change
{
  "name": "address_manage",
  "description": "Add, update, or remove an address for a contact",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "action"
    ],
    "properties": {
      "id": {
        "type": "string",
        "description": "The address ID (required for \"update\" and \"remove\")"
      },
      "city": {
        "type": "string",
        "description": "City"
      },
      "label": {
        "type": "string",
        "description": "Label (e.g. \"Home\", \"Work\")"
      },
      "action": {
        "enum": [
          "add",
          "update",
          "remove"
        ],
        "type": "string",
        "description": "Action to perform"
      },
      "country": {
        "type": "string",
        "description": "Country (ISO 3166-1 alpha-2 recommended)"
      },
      "contact_id": {
        "type": "string",
        "description": "The contact ID (required for \"add\")"
      },
      "is_primary": {
        "type": "boolean",
        "description": "Set as primary address"
      },
      "postal_code": {
        "type": "string",
        "description": "Postal/ZIP code"
      },
      "street_line_1": {
        "type": "string",
        "description": "Street address line 1"
      },
      "street_line_2": {
        "type": "string",
        "description": "Street address line 2"
      },
      "state_province": {
        "type": "string",
        "description": "State or province"
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  }
}
batch_create_activities 1 change
{
  "name": "batch_create_activities",
  "description": "Create multiple activities/interactions in one call. Max 50 items per batch. Runs atomically - if any item fails, the entire batch is rolled back.",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "activities"
    ],
    "properties": {
      "activities": {
        "type": "array",
        "items": {
          "type": "object",
          "required": [
            "type",
            "occurred_at",
            "participant_contact_ids"
          ],
          "properties": {
            "type": {
              "enum": [
                "phone_call",
                "video_call",
                "text_message",
                "in_person",
                "email",
                "activity",
                "other"
              ],
              "type": "string",
              "description": "Type of interaction"
            },
            "title": {
              "type": "string",
              "description": "Title (e.g. \"Coffee at Blue Bottle\")"
            },
            "location": {
              "type": "string",
              "description": "Where it happened"
            },
            "description": {
              "type": "string",
              "description": "Description or notes"
            },
            "occurred_at": {
              "type": "string",
              "description": "When it happened (ISO date/datetime)"
            },
            "activity_type_id": {
              "type": "string",
              "description": "Custom activity type ID"
            },
            "duration_minutes": {
              "type": "number",
              "description": "Duration in minutes"
            },
            "participant_contact_ids": {
              "type": "array",
              "items": {
                "type": "string"
              },
              "description": "Contact IDs of participants"
            }
          }
        },
        "description": "Array of activity creation inputs (max 50)"
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  }
}

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.github.benkaiser/mob-demo"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/io.github.benkaiser/mob-demo"}) 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%2Fio.github.benkaiser%2Fmob-demo.svg)](https://glimind.com/server/mcp-registry%2Fio.github.benkaiser%2Fmob-demo?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fio.github.benkaiser%2Fmob-demo?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.benkaiser%2Fmob-demo.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.benkaiser%2Fmob-demo.svg
   :target: https://glimind.com/server/mcp-registry%2Fio.github.benkaiser%2Fmob-demo?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:968f00148d45824b…, first seen 2026-10-17, included at leaf 117 of 54,206. Version history · verify what your client received.

Tools (42)

Compare: most reliable knowledge servers · most reliable communication servers · most reliable data servers · most reliable crm servers · most reliable finance 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 Benkaiser Mob Demo MCP server down right now?

As of 2026-10-23 19:52 UTC, the Benkaiser Mob Demo MCP server is up with a Glimind reliability score of 81/100 (grade B). Over the last 30 days it answered 99.7% of Glimind's liveness checks. It had 87 outages in 90 days, with a median recovery of 4 minutes.

How many tools does Benkaiser Mob Demo MCP server provide?

Benkaiser Mob Demo MCP server advertises 42 tools, including activity_list, activity_manage, activity_type_manage, address_manage, batch_create_activities.

How do I install Benkaiser Mob Demo MCP server?

Point your MCP client at this streamable-http endpoint: https://demo.mobcrm.au/mcp

Is the Benkaiser Mob Demo MCP server safe to connect to an AI agent?

Glimind scanned all 42 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 Benkaiser Mob Demo 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