Mob (Demo)
REMOTE · DEMO.MOBCRM.AU
Ephemeral no-signup demo of Mob, an AI-first personal CRM you run in natural language.
Available components
Last scanned (13 hours ago)
Scores higher than 10% of remote servers
Reachable. Last reached 5 Nov 2026.
Category CRM and Sales
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. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint returned HTTP 502. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Nov 26 −55
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 31 Oct 26 0
- Stability: 0.97 → pass security
- 30 Oct 26 0
- Stability: pass → 0.97 functional
- 1 Oct 26 0
- Injection markers: unverified → pass ▲ security
- Stability: unverified → pass ▲ security
- Authorization: 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. security
- Tool coverage: unverified → 100 ▲ functional
- Schema quality: unverified → 100 ▲ functional
- 30 Sept 26 0
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the whole tool list to see what that exposes. security
- Schema quality: 100 → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 2 Sept 26 0
- Stability: 0.97 → pass security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://demo.mobcrm.au/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=demo.mobcrm.au | CN=YE1,O=Let's Encrypt,C=US | 15 Sept 2026 | 14 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 6d8c6c47098d7eeb5e0b431a5703ba41d9f |
| SANs: demo.mobcrm.au | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of demo.mobcrm.au. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| au. | present | 26642 | 8 | Verified |
| mobcrm.au. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 502 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=15724800; includeSubdomains |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://demo.mobcrm.au/mcp | HTTP error | 502 | |
| http (plaintext) | http://demo.mobcrm.au/mcp | HTTPS enforced | 301 | https://demo.mobcrm.au:443/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
activity_list ~176
List activities, optionally filtered by contact or type. Add days_back or since for a chronological activity journal with participant names.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
No output schema declared.
No examples provided.
activity_manage ~296
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.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | 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") |
No output schema declared.
No examples provided.
activity_type_manage ~93
List, create, update, or delete custom activity types
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | 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") |
No output schema declared.
No examples provided.
address_manage ~175
Add, update, or remove an address for a contact
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | 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 |
No output schema declared.
No examples provided.
batch_create_activities ~58
Create multiple activities/interactions in one call. Max 50 items per batch. Runs atomically - if any item fails, the entire batch is rolled back.
| Name | Type | Req | Description |
|---|---|---|---|
| activities | array | yes | Array of activity creation inputs (max 50) |
No output schema declared.
No examples provided.
batch_create_contacts ~55
Create multiple contacts in one call. Max 50 items per batch. Runs atomically - if any item fails, the entire batch is rolled back.
| Name | Type | Req | Description |
|---|---|---|---|
| contacts | array | yes | Array of contact creation inputs (max 50) |
No output schema declared.
No examples provided.
batch_tag_contacts ~80
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.
| Name | Type | Req | Description |
|---|---|---|---|
| contact_ids | array | yes | Array of contact IDs to tag (max 50) |
| tag_name | string | yes | Tag name to apply |
No output schema declared.
No examples provided.
contact_create ~376
Create a new contact with basic info
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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 |
| middle_name | string | – | Middle name |
| 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 |
No output schema declared.
No examples provided.
contact_delete ~31
Soft-delete a contact (can be restored later)
| Name | Type | Req | Description |
|---|---|---|---|
| contact_id | string | yes | The contact ID to delete |
No output schema declared.
No examples provided.
contact_find_duplicates ~38
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
contact_get ~71
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
| Name | Type | Req | Description |
|---|---|---|---|
| contact_id | string | yes | The contact ID |
No output schema declared.
No examples provided.
contact_list ~167
List contacts with optional filters (status, favorite, company, tag, search). Returns paginated results.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
No output schema declared.
No examples provided.
contact_merge ~85
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.
| Name | Type | Req | Description |
|---|---|---|---|
| primary_contact_id | string | yes | The contact ID to keep (primary) |
| secondary_contact_id | string | yes | The contact ID to merge into the primary (will be soft-deleted) |
No output schema declared.
No examples provided.
contact_method_manage ~176
Add, update, or remove a contact method (email, phone, social handle, etc.)
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | 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") |
No output schema declared.
No examples provided.
contact_restore ~28
Restore a soft-deleted contact
| Name | Type | Req | Description |
|---|---|---|---|
| contact_id | string | yes | The contact ID to restore |
No output schema declared.
No examples provided.
contact_timeline ~79
Get the unified timeline for a contact (activities, life events, notes, etc.)
| Name | Type | Req | Description |
|---|---|---|---|
| contact_id | string | yes | The contact ID |
| entry_type | string | – | Filter by entry type |
| page | number | – | Page number (default: 1) |
| per_page | number | – | Results per page (default: 20) |
No output schema declared.
No examples provided.
contact_update ~299
Update contact fields
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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 |
| middle_name | string | – | Middle name |
| nickname | string | – | Nickname |
| pronouns | string | – | Pronouns |
| status | string | – | Contact status |
| work_notes | string | – | Work notes |
No output schema declared.
No examples provided.
contacts_needing_attention ~141
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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") |
No output schema declared.
No examples provided.
custom_field_manage ~124
Add, update, or remove a custom field on a contact
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | 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") |
No output schema declared.
No examples provided.
data_export ~38
Export all CRM data as a JSON object (contacts, relationships, notes, activities, life events, reminders, gifts, debts, tasks, tags)
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
data_statistics ~25
Get CRM statistics and overview (contact counts, activity counts, pending items, etc.)
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
debt_manage ~371
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.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | 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) |
No output schema declared.
No examples provided.
food_preferences_get ~37
Get food preferences for a contact (dietary restrictions, allergies, favorites, dislikes)
| Name | Type | Req | Description |
|---|---|---|---|
| contact_id | string | yes | The contact ID |
No output schema declared.
No examples provided.
food_preferences_upsert ~123
Set or update food preferences for a contact. Replaces all fields - pass all known preferences, not just changes.
| Name | Type | Req | Description |
|---|---|---|---|
| allergies | array | – | Food allergies (e.g. ["peanuts", "shellfish"]) |
| contact_id | string | yes | 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 |
No output schema declared.
No examples provided.
gift_list ~183
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
No output schema declared.
No examples provided.
gift_manage ~303
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.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | 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 |
No output schema declared.
No examples provided.
global_search ~106
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Search term |
No output schema declared.
No examples provided.
life_event_manage ~384
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.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | 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" |
No output schema declared.
No examples provided.
manage_push_notifications ~34
Open a page to manage push notification subscriptions in your browser. Enables/disables web push notifications for birthday reminders and other alerts.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
manage_settings ~271
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)
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | 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") |
No output schema declared.
No examples provided.
note_list ~194
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
No output schema declared.
No examples provided.
note_manage ~204
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.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | 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") |
No output schema declared.
No examples provided.
notification_create ~51
Create a custom notification
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | – | Notification body |
| contact_id | string | – | Related contact ID |
| title | string | yes | Notification title |
| type | string | yes | Notification type |
No output schema declared.
No examples provided.
notification_list ~57
List notifications (newest first)
| Name | Type | Req | Description |
|---|---|---|---|
| page | number | – | Page number (default: 1) |
| per_page | number | – | Results per page (default: 20) |
| unread_only | boolean | – | Only show unread notifications |
No output schema declared.
No examples provided.
notification_read ~59
Mark notification(s) as read. Pass id for a single notification, or all=true for all.
| Name | Type | Req | Description |
|---|---|---|---|
| all | boolean | – | Mark all notifications as read (default: false) |
| id | string | – | The notification ID (required unless all=true) |
No output schema declared.
No examples provided.
prime ~109
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
relationship_manage ~346
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.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | 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… |
No output schema declared.
No examples provided.
reminder_manage ~425
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.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | 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") |
No output schema declared.
No examples provided.
tag_manage ~200
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.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | 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) |
No output schema declared.
No examples provided.
task_manage ~354
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.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | 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") |
No output schema declared.
No examples provided.
upcoming_birthdays ~96
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
No output schema declared.
No examples provided.
upcoming_reminders ~91
Find upcoming and overdue reminders across all contacts. Returns reminders sorted by date (overdue first, then soonest upcoming).
| Name | Type | Req | Description |
|---|---|---|---|
| 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) |
No output schema declared.
No examples provided.
How do I install the Mob (Demo) MCP server?
Mob (Demo) is a hosted endpoint at https://demo.mobcrm.au/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · demo.mobcrm.au
claude mcp add --transport http benkaiser-mob-demo 'https://demo.mobcrm.au/mcp'
What is the Mob (Demo) MCP server?
Mob (Demo) is an MCP server listed in the public MCP registry as io.github.benkaiser/mob-demo. Ephemeral no-signup demo of Mob, an AI-first personal CRM you run in natural language. This page covers its hosted endpoint (https://demo.mobcrm.au/mcp).
Is the Mob (Demo) MCP server safe to use?
Mob (Demo) scores 25 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Mob (Demo) MCP server expose?
Mob (Demo) exposes 42 tools: contact_create, contact_get, contact_update, contact_delete, contact_restore, and 37 more. Their descriptions and schemas cost roughly 6,609 tokens of context every time the server is loaded.
Does the Mob (Demo) MCP server require authentication?
Its publisher declares no required credentials for Mob (Demo). We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the Mob (Demo) MCP server still maintained?
Mob (Demo) is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.