# Mob (Demo) (remote · demo.mobcrm.au)

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

- Trust score: 66/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `demo.mobcrm.au`: 66/100 (this document), [markdown](https://verifymcp.io/servers/benkaiser-mob-demo/demo.md), [page](https://verifymcp.io/servers/benkaiser-mob-demo/demo)

## Channel facts

- Endpoint: `https://demo.mobcrm.au/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 42 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 78/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 6589 tokens (~156/item across 42 items; 42 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

**Unverified: 1 category.** A category scored 0 because we could not verify it: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

## Install

### Claude

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

### Codex

```toml
[mcp_servers.benkaiser-mob-demo]
url = "https://demo.mobcrm.au/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "benkaiser-mob-demo": {
      "type": "remote",
      "url": "https://demo.mobcrm.au/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add benkaiser-mob-demo --url https://demo.mobcrm.au/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  benkaiser-mob-demo:
    url: "https://demo.mobcrm.au/mcp"
```

### Other

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

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 66)

First indexed and scored.

## MCP tools (42)

### `contact_create` (~366 tokens)

Create a new contact with basic info

Input parameters:

- `avatar_url` (string): Avatar URL
- `birthday_date` (string): Full birthday date (YYYY-MM-DD), used with birthday_mode=full_date
- `birthday_day` (number): Birthday day (1-31), used with birthday_mode=month_day
- `birthday_mode` (string): Birthday mode: full_date (YYYY-MM-DD), month_day (month + day only), or approximate_age (birth year estimate)
- `birthday_month` (number): Birthday month (1-12), used with birthday_mode=month_day
- `birthday_year_approximate` (number): Approximate birth year, used with birthday_mode=approximate_age
- `company` (string): Company or organization
- `deceased_date` (string): Date of death (YYYY-MM-DD)
- `first_name` (string, required): First name (required)
- `gender` (string): Gender
- `industry` (string): Industry
- `is_favorite` (boolean): Mark as favorite
- `job_title` (string): Job title
- `last_name` (string): Last name
- `maiden_name` (string): Maiden name
- `met_at_date` (string): Date you met this person (YYYY-MM-DD)
- `met_at_location` (string): Where you met this person
- `met_description` (string): Story of how you met
- `met_through_contact_id` (string): Contact ID of person who introduced you
- `nickname` (string): Nickname
- `pronouns` (string): Pronouns (e.g. she/her, he/him, they/them)
- `status` (string): Contact status (default: active)
- `work_notes` (string): Notes about their work

### `contact_get` (~71 tokens)

Get full contact details including all related data in one call: contact methods, addresses, food preferences, custom fields, tags, relationships, recent notes, recent activities, life events, active reminders, open tasks, recent gifts, active debts, and debt summary

Input parameters:

- `contact_id` (string, required): The contact ID

### `contact_update` (~289 tokens)

Update contact fields

Input parameters:

- `avatar_url` (string): Avatar URL
- `birthday_date` (string): Full birthday date (YYYY-MM-DD)
- `birthday_day` (number): Birthday day (1-31)
- `birthday_mode` (string): Birthday mode
- `birthday_month` (number): Birthday month (1-12)
- `birthday_year_approximate` (number): Approximate birth year
- `company` (string): Company
- `contact_id` (string, required): The contact ID to update
- `deceased_date` (string): Date of death (YYYY-MM-DD)
- `first_name` (string): First name
- `gender` (string): Gender
- `industry` (string): Industry
- `is_favorite` (boolean): Mark as favorite
- `job_title` (string): Job title
- `last_name` (string): Last name
- `maiden_name` (string): Maiden name
- `met_at_date` (string): Date you met this person
- `met_at_location` (string): Where you met this person
- `met_description` (string): How you met
- `met_through_contact_id` (string): Contact ID of person who introduced you
- `nickname` (string): Nickname
- `pronouns` (string): Pronouns
- `status` (string): Contact status
- `work_notes` (string): Work notes

### `contact_delete` (~31 tokens)

Soft-delete a contact (can be restored later)

Input parameters:

- `contact_id` (string, required): The contact ID to delete

### `contact_restore` (~28 tokens)

Restore a soft-deleted contact

Input parameters:

- `contact_id` (string, required): The contact ID to restore

### `contact_list` (~167 tokens)

List contacts with optional filters (status, favorite, company, tag, search). Returns paginated results.

Input parameters:

- `company` (string): Filter by company
- `include_deleted` (boolean): Include soft-deleted contacts in results (default: false)
- `is_favorite` (boolean): Filter by favorite
- `page` (number): Page number (default: 1)
- `per_page` (number): Results per page (default: 20)
- `search` (string): Search contacts by name, company, or job title
- `sort_by` (string): Sort field (default: name)
- `sort_order` (string): Sort order (default: asc)
- `status` (string): Filter by status
- `tag_name` (string): Filter by tag name

### `contact_merge` (~85 tokens)

Merge two contacts into one. All child records (notes, activities, tags, etc.) from the secondary contact are moved to the primary. The secondary contact is soft-deleted after merge.

Input parameters:

- `primary_contact_id` (string, required): The contact ID to keep (primary)
- `secondary_contact_id` (string, required): The contact ID to merge into the primary (will be soft-deleted)

### `contact_find_duplicates` (~38 tokens)

Scan for potential duplicate contacts using name, email, and phone matching. Returns pairs of contacts that may be duplicates with the reason for the match.

### `contact_method_manage` (~176 tokens)

Add, update, or remove a contact method (email, phone, social handle, etc.)

Input parameters:

- `action` (string, required): Action to perform
- `contact_id` (string): The contact ID (required for "add")
- `id` (string): The contact method ID (required for "update" and "remove")
- `is_primary` (boolean): Set as primary for this type
- `label` (string): Label (e.g. "Personal", "Work")
- `type` (string): Type of contact method (required for "add"). Built-ins: email, phone, whatsapp, telegram, signal, twitter, instagram, facebook, linkedin, website, other. Custom values defined in Settings are also ac…
- `value` (string): The value - email, phone number, handle (required for "add")

### `address_manage` (~175 tokens)

Add, update, or remove an address for a contact

Input parameters:

- `action` (string, required): Action to perform
- `city` (string): City
- `contact_id` (string): The contact ID (required for "add")
- `country` (string): Country (ISO 3166-1 alpha-2 recommended)
- `id` (string): The address ID (required for "update" and "remove")
- `is_primary` (boolean): Set as primary address
- `label` (string): Label (e.g. "Home", "Work")
- `postal_code` (string): Postal/ZIP code
- `state_province` (string): State or province
- `street_line_1` (string): Street address line 1
- `street_line_2` (string): Street address line 2

### `food_preferences_get` (~37 tokens)

Get food preferences for a contact (dietary restrictions, allergies, favorites, dislikes)

Input parameters:

- `contact_id` (string, required): The contact ID

### `food_preferences_upsert` (~123 tokens)

Set or update food preferences for a contact. Replaces all fields - pass all known preferences, not just changes.

Input parameters:

- `allergies` (array): Food allergies (e.g. ["peanuts", "shellfish"])
- `contact_id` (string, required): The contact ID
- `dietary_restrictions` (array): Dietary restrictions (e.g. ["vegetarian", "gluten-free"])
- `disliked_foods` (array): Disliked foods
- `favorite_foods` (array): Favorite foods
- `notes` (string): Additional notes about food preferences

### `custom_field_manage` (~124 tokens)

Add, update, or remove a custom field on a contact

Input parameters:

- `action` (string, required): Action to perform
- `contact_id` (string): The contact ID (required for "add")
- `field_group` (string): Group to organize fields, e.g. "Preferences"
- `field_name` (string): Field name, e.g. "Favorite Color" (required for "add")
- `field_value` (string): Field value (required for "add")
- `id` (string): The custom field ID (required for "update" and "remove")

### `relationship_manage` (~346 tokens)

Add, update, remove, or list relationships between contacts.
• action="add": Create a relationship between two contacts. Automatically creates the inverse relationship. Requires contact_id, related_contact_id, and relationship_type. To create relationships involving yourself, use your own contact_id from the prime tool. Relationships describe how contacts relate to each other (e.g. Bandit is Bingo's parent).
• action="update": Update a relationship. Also updates the inverse relationship. Requires id. Optionally set relationship_type and/or notes.
• action="remove": Remove a relationship and its inverse. Requires id.
• action="list": List all relationships for a contact. Requires contact_id.

Input parameters:

- `action` (string, required): Action to perform
- `contact_id` (string): The source contact ID (required for "add" and "list")
- `id` (string): The relationship ID (required for "update" and "remove")
- `notes` (string): Notes about this relationship (optional for "add" and "update")
- `related_contact_id` (string): The related contact ID (required for "add")
- `relationship_type` (string): Type of relationship (required for "add", optional for "update"). Canonical values: significant_other, spouse, date, lover, in_love_with, secret_lover, ex_boyfriend_girlfriend, ex_husband_wife, paren…

### `note_manage` (~204 tokens)

Create, update, delete, or restore a note for a contact.
• action="create": Add a new note. Requires contact_id and body. Optional title, is_pinned.
• action="update": Update an existing note. Requires id. Optional title, body, is_pinned.
• action="delete": Soft-delete a note. Requires id.
• action="restore": Restore a soft-deleted note. Requires id.

Input parameters:

- `action` (string, required): Action to perform
- `body` (string): Note body, supports markdown (required for "create", optional for "update")
- `contact_id` (string): The contact ID (required for "create")
- `id` (string): The note ID (required for "update", "delete", "restore")
- `is_pinned` (boolean): Pin/unpin note (optional for "create" and "update")
- `title` (string): Note title (optional for "create" and "update")

### `note_list` (~194 tokens)

List and search notes. When contact_id is provided alone, lists that contact's notes (pinned first). Add query, tag_name, is_pinned, or omit contact_id to search across all contacts.

Input parameters:

- `contact_id` (string): Filter by contact ID (optional - omit to search across all contacts)
- `include_deleted` (boolean): Include soft-deleted notes in results (default: false)
- `is_pinned` (boolean): Filter by pinned status
- `page` (number): Page number (default: 1)
- `per_page` (number): Results per page (default: 20)
- `query` (string): Search term matched against note title and body
- `sort_by` (string): Sort field (default: updated_at)
- `sort_order` (string): Sort direction (default: desc)
- `tag_name` (string): Filter to notes belonging to contacts with this tag

### `tag_manage` (~200 tokens)

Manage tags and contact tagging.
• action="list": List all tags for the authenticated user. No additional fields required.
• action="create": Create a new tag (or return existing if name already exists). Requires name.
• action="update": Update a tag name. Requires id and name.
• action="delete": Delete a tag. Requires id.
• action="tag_contact": Tag a contact. Creates the tag if it doesn't exist. Requires name (the tag name) and contact_id.
• action="untag_contact": Remove a tag from a contact. Requires id (the tag ID) and contact_id.

Input parameters:

- `action` (string, required): Action to perform
- `contact_id` (string): The contact ID (required for tag_contact and untag_contact)
- `id` (string): The tag ID (required for update, delete, untag_contact)
- `name` (string): Tag name (required for create and tag_contact)

### `activity_manage` (~296 tokens)

Create, get, update, delete, or restore an activity/interaction.
• action="create": Record a new activity. Requires type, occurred_at, participant_contact_ids. Optional title, description, duration_minutes, location, activity_type_id.
• action="get": Get full details of an activity. Requires id.
• action="update": Update an activity. Requires id. Optional type, title, description, occurred_at, duration_minutes, location, participant_contact_ids.
• action="delete": Soft-delete an activity. Requires id.
• action="restore": Restore a soft-deleted activity. Requires id.

Input parameters:

- `action` (string, required): Action to perform
- `activity_type_id` (string): Custom activity type ID
- `description` (string): Description or notes
- `duration_minutes` (number): Duration in minutes
- `id` (string): The activity ID (required for "get", "update", "delete", "restore")
- `location` (string): Where it happened
- `occurred_at` (string): When it happened (ISO date/datetime) (required for "create", optional for "update")
- `participant_contact_ids` (array): Contact IDs of participants (required for "create", optional for "update")
- `title` (string): Title (e.g. "Coffee at Blue Bottle")
- `type` (string): Type of interaction (required for "create", optional for "update")

### `activity_list` (~176 tokens)

List activities, optionally filtered by contact or type. Add days_back or since for a chronological activity journal with participant names.

Input parameters:

- `contact_id` (string): Filter by contact ID
- `days_back` (number): Look-back window in days (uses activity log mode with participant names). Ignored if since is provided.
- `include_deleted` (boolean): Include soft-deleted activities in results (default: false)
- `page` (number): Page number (default: 1)
- `per_page` (number): Results per page (default: 20)
- `since` (string): Show activities since this ISO date (uses activity log mode with participant names)
- `sort_order` (string): Sort direction by occurred_at (default: desc, only for activity log mode)
- `type` (string): Filter by interaction type

### `activity_type_manage` (~93 tokens)

List, create, update, or delete custom activity types

Input parameters:

- `action` (string, required): Action to perform
- `category` (string): Category (e.g. "Food & Drink", "Sports")
- `icon` (string): Icon identifier
- `id` (string): Activity type ID (required for "update" and "delete")
- `name` (string): Activity type name (required for "create")

### `life_event_manage` (~384 tokens)

Create, list, update, delete, or restore life events for a contact.
• action="create": Record a new life event. Requires contact_id, event_type, and title. Optional description, occurred_at, related_contact_ids.
• action="list": List life events for a contact. Requires contact_id. Optional page, per_page, include_deleted.
• action="update": Update a life event. Requires id. Optional event_type, title, description, occurred_at, related_contact_ids.
• action="delete": Soft-delete a life event. Requires id.
• action="restore": Restore a soft-deleted life event. Requires id.

Input parameters:

- `action` (string, required): Action to perform
- `contact_id` (string): The contact ID (required for "create" and "list")
- `description` (string): Description (optional for "create" and "update")
- `event_type` (string): Event type (e.g. "new_job", "got_married", "moved") - required for "create", optional for "update"
- `id` (string): The life event ID (required for "update", "delete", "restore")
- `include_deleted` (boolean): Include soft-deleted life events in "list" results (default: false)
- `occurred_at` (string): When it happened (ISO date, optional for "create" and "update")
- `page` (number): Page number for "list" (default: 1)
- `per_page` (number): Results per page for "list" (default: 20)
- `related_contact_ids` (array): IDs of other contacts involved (optional for "create" and "update")
- `title` (string): Title (e.g. "Started at Google", "Moved to Berlin") - required for "create", optional for "update"

### `contact_timeline` (~79 tokens)

Get the unified timeline for a contact (activities, life events, notes, etc.)

Input parameters:

- `contact_id` (string, required): The contact ID
- `entry_type` (string): Filter by entry type
- `page` (number): Page number (default: 1)
- `per_page` (number): Results per page (default: 20)

### `reminder_manage` (~425 tokens)

Create, list, update, complete, snooze, delete, or restore reminders.
• action="create": Create a reminder for a contact. Requires contact_id, title, and reminder_date. Optional description, frequency.
• action="list": List reminders, optionally filtered by contact or status. Optional contact_id, status, page, per_page, include_deleted.
• action="update": Update a reminder. Requires id. Optional title, description, reminder_date, frequency.
• action="complete": Mark a reminder as completed. For recurring reminders, advances to the next occurrence. Requires id.
• action="snooze": Snooze a reminder to a new date. Requires id and new_date.
• action="delete": Soft-delete a reminder. Requires id.
• action="restore": Restore a soft-deleted reminder. Requires id.

Input parameters:

- `action` (string, required): Action to perform
- `contact_id` (string): The contact ID (required for "create", optional filter for "list")
- `description` (string): Description (optional for "create" and "update")
- `frequency` (string): Frequency (default: one_time, optional for "create" and "update")
- `id` (string): The reminder ID (required for "update", "complete", "snooze", "delete", "restore")
- `include_deleted` (boolean): Include soft-deleted reminders in "list" results (default: false)
- `new_date` (string): New reminder date (ISO date YYYY-MM-DD) (required for "snooze")
- `page` (number): Page number for "list" (default: 1)
- `per_page` (number): Results per page for "list" (default: 20)
- `reminder_date` (string): When to remind (ISO date YYYY-MM-DD) (required for "create", optional for "update")
- `status` (string): Filter by status (for "list" only)
- `title` (string): Reminder title (required for "create", optional for "update")

### `notification_list` (~57 tokens)

List notifications (newest first)

Input parameters:

- `page` (number): Page number (default: 1)
- `per_page` (number): Results per page (default: 20)
- `unread_only` (boolean): Only show unread notifications

### `notification_create` (~51 tokens)

Create a custom notification

Input parameters:

- `body` (string): Notification body
- `contact_id` (string): Related contact ID
- `title` (string, required): Notification title
- `type` (string, required): Notification type

### `notification_read` (~59 tokens)

Mark notification(s) as read. Pass id for a single notification, or all=true for all.

Input parameters:

- `all` (boolean): Mark all notifications as read (default: false)
- `id` (string): The notification ID (required unless all=true)

### `gift_manage` (~303 tokens)

Create, update, delete, or restore a gift for a contact.
• action="create": Track a gift idea, plan, or record a given/received gift. Requires contact_id, name, and direction. Optional description, url, estimated_cost, currency, occasion, status, date.
• action="update": Update an existing gift (change status, add details, etc.). Requires id. Optional name, description, url, estimated_cost, currency, occasion, status, direction, date.
• action="delete": Soft-delete a gift. Requires id.
• action="restore": Restore a soft-deleted gift. Requires id.

Input parameters:

- `action` (string, required): Action to perform
- `contact_id` (string): The contact ID (required for "create")
- `currency` (string): Currency (default: USD)
- `date` (string): Date of giving/receiving (ISO date)
- `description` (string): Description
- `direction` (string): Giving to or receiving from this contact (required for "create")
- `estimated_cost` (number): Estimated cost
- `id` (string): The gift ID (required for "update", "delete", "restore")
- `name` (string): Gift name (required for "create")
- `occasion` (string): Occasion (e.g. "Birthday", "Christmas")
- `status` (string): Gift status (default: idea)
- `url` (string): Link to the gift

### `gift_list` (~183 tokens)

List gifts, optionally filtered by contact, status, or direction. Add occasion, sort_by, sort_order, or omit contact_id for a cross-contact gift tracker with summary stats.

Input parameters:

- `contact_id` (string): Filter by contact ID
- `direction` (string): Filter by direction
- `include_deleted` (boolean): Include soft-deleted gifts in results (default: false)
- `occasion` (string): Filter by occasion (fuzzy match, e.g. "birthday", "Christmas")
- `page` (number): Page number (default: 1)
- `per_page` (number): Results per page (default: 20)
- `sort_by` (string): Sort field (default: date for tracker mode, created_at otherwise)
- `sort_order` (string): Sort direction (default: desc)
- `status` (string): Filter by status

### `debt_manage` (~371 tokens)

Create, list, update, settle, delete, restore, or summarize debts.
• action="create": Track a new debt. Requires contact_id, amount, direction. Optional currency, reason, incurred_at.
• action="list": List debts. Optional contact_id, status, page, per_page, include_deleted.
• action="update": Update a debt. Requires id. Optional amount, currency, direction, reason, incurred_at.
• action="settle": Mark a debt as settled. Requires id.
• action="delete": Soft-delete a debt. Requires id.
• action="restore": Restore a soft-deleted debt. Requires id.
• action="summary": Get net balance summary for a contact. Requires contact_id.

Input parameters:

- `action` (string, required): Action to perform
- `amount` (number): Amount owed (required for "create", optional for "update")
- `contact_id` (string): The contact ID (required for "create" and "summary", optional filter for "list")
- `currency` (string): Currency (default: USD)
- `direction` (string): Who owes whom (required for "create", optional for "update")
- `id` (string): The debt ID (required for "update", "settle", "delete", "restore")
- `include_deleted` (boolean): Include soft-deleted debts in "list" results (default: false)
- `incurred_at` (string): When the debt was incurred (ISO date)
- `page` (number): Page number for "list" (default: 1)
- `per_page` (number): Results per page for "list" (default: 20)
- `reason` (string): Reason for the debt
- `status` (string): Filter by status (for "list" only)

### `task_manage` (~354 tokens)

Create, list, update, complete, delete, or restore tasks.
• action="create": Create a task. Requires title. Optional description, contact_id, due_date, priority.
• action="list": List tasks. Optional contact_id, status, priority, page, per_page, include_deleted.
• action="update": Update a task. Requires id. Optional title, description, contact_id, due_date, priority, status.
• action="complete": Mark a task as completed. Requires id.
• action="delete": Soft-delete a task. Requires id.
• action="restore": Restore a soft-deleted task. Requires id.

Input parameters:

- `action` (string, required): Action to perform
- `contact_id` (string): Link to a contact (optional for "create"/"update", filter for "list")
- `description` (string): Description (optional for "create" and "update")
- `due_date` (string): Due date (ISO date, optional for "create" and "update")
- `id` (string): The task ID (required for "update", "complete", "delete", "restore")
- `include_deleted` (boolean): Include soft-deleted tasks in "list" results (default: false)
- `page` (number): Page number for "list" (default: 1)
- `per_page` (number): Results per page for "list" (default: 20)
- `priority` (string): Priority (optional for "create"/"update", filter for "list")
- `status` (string): Status (optional for "update", filter for "list")
- `title` (string): Task title (required for "create", optional for "update")

### `data_export` (~38 tokens)

Export all CRM data as a JSON object (contacts, relationships, notes, activities, life events, reminders, gifts, debts, tasks, tags)

### `data_statistics` (~25 tokens)

Get CRM statistics and overview (contact counts, activity counts, pending items, etc.)

### `prime` (~109 tokens)

IMPORTANT: Call this tool FIRST before any other tool to load essential CRM context. Returns a compact overview of the user's data: the current user's identity (name, email, contact_id), all tags, the 200 most recently updated contacts (id, name, and tag IDs), and the 10 most recent notes. This primes your context so you can reference contacts by name, understand the user's tag taxonomy, and see recent activity without needing separate list calls. Always call this at the start of a conversation.

### `upcoming_birthdays` (~96 tokens)

Find contacts with birthdays coming up within a time window or in a specific month. Returns contacts sorted by soonest birthday first, with age calculations when available.

Input parameters:

- `days_ahead` (number): Look-ahead window in days from today (default: 30). Ignored if month is provided.
- `month` (number): Optional: show all birthdays in a specific month (1-12) instead of using days_ahead

### `global_search` (~106 tokens)

Search across all entity types (contacts, notes, activities, life events, gifts, tasks, reminders, debts, relationships, contact methods, addresses, custom fields) in a single query. Returns grouped results by entity type with snippets and contact context.

Input parameters:

- `entity_types` (array): Optional: filter to specific entity types (default: all types)
- `limit_per_type` (number): Max results per entity type (default: 10)
- `query` (string, required): Search term

### `contacts_needing_attention` (~141 tokens)

Find contacts you haven't interacted with recently - the "who am I neglecting?" query. Returns contacts sorted by staleness (longest since last interaction first). Contacts with zero interactions are included and sorted first.

Input parameters:

- `days_since_last_interaction` (number): Minimum days since last activity to be included (default: 30)
- `is_favorite` (boolean): Filter to favorites only
- `limit` (number): Max results to return (default: 20)
- `status` (string): Contact status filter (default: active)
- `tag_name` (string): Filter to contacts with this tag (e.g., "close friends")

### `upcoming_reminders` (~91 tokens)

Find upcoming and overdue reminders across all contacts. Returns reminders sorted by date (overdue first, then soonest upcoming).

Input parameters:

- `days_ahead` (number): Look-ahead window in days from today (default: 14)
- `include_overdue` (boolean): Include overdue reminders with reminder_date before today (default: true)
- `status` (string): Filter by reminder status (default: active)

### `batch_create_contacts` (~55 tokens)

Create multiple contacts in one call. Max 50 items per batch. Runs atomically - if any item fails, the entire batch is rolled back.

Input parameters:

- `contacts` (array, required): Array of contact creation inputs (max 50)

### `batch_tag_contacts` (~80 tokens)

Apply a tag to multiple contacts in one call. Max 50 contacts per batch. Creates the tag if it doesn't exist. Runs atomically - if any item fails, the entire batch is rolled back.

Input parameters:

- `contact_ids` (array, required): Array of contact IDs to tag (max 50)
- `tag_name` (string, required): Tag name to apply

### `batch_create_activities` (~58 tokens)

Create multiple activities/interactions in one call. Max 50 items per batch. Runs atomically - if any item fails, the entire batch is rolled back.

Input parameters:

- `activities` (array, required): Array of activity creation inputs (max 50)

### `manage_settings` (~271 tokens)

View or update your personal settings (timezone, birthday reminder preferences).
• action="get": View current settings
• action="update": Update settings. Optional fields: timezone (IANA timezone like "America/New_York"), birthday_reminder_offsets (array of day offsets like [0,7,30] where 0=day-of, 7=week-before), reminder_offsets (array of day offsets like [0,7,30] for advance notice on custom reminders), birthday_reminder_time (HH:MM 24-hour format for when to send reminders)

Input parameters:

- `action` (string, required): Action to perform
- `birthday_reminder_offsets` (array): Array of day offsets for birthday reminders (e.g. [0,7,30] = day-of, 1 week before, 1 month before)
- `birthday_reminder_time` (string): Time of day for birthday reminders in HH:MM 24-hour format (e.g. "09:00")
- `reminder_offsets` (array): Array of day offsets for custom reminder advance notice (e.g. [0,7,30] = day-of, 1 week before, 1 month before)
- `timezone` (string): IANA timezone (e.g. "America/New_York", "Europe/London")

### `manage_push_notifications` (~34 tokens)

Open a page to manage push notification subscriptions in your browser. Enables/disables web push notifications for birthday reminders and other alerts.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/benkaiser-mob-demo/demo#diagnostics

## Score history

- 2026-08-03: 66

## Links

- Remote endpoint: https://demo.mobcrm.au/mcp
- Repository: https://github.com/benkaiser/mob-mcp-crm
- Website: https://mobcrm.au/
- Changelog RSS feed: https://verifymcp.io/servers/benkaiser-mob-demo/demo/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/benkaiser-mob-demo/demo/changelog.json
- HTML version of this page: https://verifymcp.io/servers/benkaiser-mob-demo/demo