mcp-registry/com.numbru/client-compass · v1.0.0
Also listed as glama/marcus160365/client-compass, mcp-registry/io.github.marcus160365/client-compass · primary listing: mcp-registry/io.github.marcus160365/client-compass
As of 2026-10-26 19:00 UTC, the Numbru Client Compass MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Behavioral intelligence for client-facing professionals. Know who you're walking into.
Point your MCP client at this streamable-http endpoint: https://numbru-mcp-server.numbru.workers.dev
11 of 11 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 →
4 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 →
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
In the last 30 days: 0 tool(s) removed and 2 schema change(s).
Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.numbru%2Fclient-compass/fixes
{
"name": "batch_create_persons",
"description": "Create up to 10 people (clients) in parallel and generate a Client Compass for each. Use this for re-engaging dormant leads — a name is enough. IMPORTANT: Return the full Start Here coaching for each person (ask_them, know_this, avoid_this) — do not summarize or create tables. Present each person's compass_summary_text and all three Start Here items in full.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"contacts"
],
"properties": {
"contacts": {
"type": "array",
"items": {
"type": "object",
"required": [
"first_name",
"last_name"
],
"properties": {
"dob": {
"type": "string",
"description": "Date of birth in YYYY-MM-DD format (optional)"
},
"vertical": {
"enum": [
"real_estate",
"sales",
"civic",
"insurance"
],
"type": "string"
},
"last_name": {
"type": "string",
"maxLength": 200,
"minLength": 1
},
"first_name": {
"type": "string",
"maxLength": 200,
"minLength": 1
},
"middle_name": {
"type": "string",
"maxLength": 200
}
}
},
"maxItems": 10,
"minItems": 1,
"description": "Array of 1–10 contacts to profile. First and last name required for each."
}
}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
},
"title": "Batch Create Persons"
}{
"name": "create_person",
"description": "Save a new person (client) to the user's people list. Only call this when the user asks to save or add someone. Never call it to get a Lowdown, a card, or to go deeper: use generate_compass for every read. Requires the user to have a profession set.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"first_name",
"last_name"
],
"properties": {
"dob": {
"type": "string",
"description": "Date of birth in YYYY-MM-DD format (optional, improves compass accuracy). Do not ask the user for this before calling — proceed with name only and let the engine handle it."
},
"vertical": {
"enum": [
"real_estate",
"sales",
"civic",
"insurance"
],
"type": "string",
"description": "Industry vertical override. Defaults to the user's profession if omitted."
},
"last_name": {
"type": "string",
"maxLength": 200,
"minLength": 1,
"description": "Last name (required)"
},
"first_name": {
"type": "string",
"maxLength": 200,
"minLength": 1,
"description": "First name (required)"
},
"key_parties": {
"type": "array",
"items": {
"type": "object",
"required": [
"id"
],
"properties": {
"id": {
"enum": [
"spouse_partner",
"parent",
"colleague",
"friend",
"investor"
],
"type": "string"
},
"name": {
"type": "string"
}
}
},
"description": "Key parties involved (e.g. spouse, parent, colleague)"
},
"middle_name": {
"type": "string",
"maxLength": 200,
"description": "Middle name (optional)"
},
"must_haves_avoids": {
"type": "string",
"maxLength": 2000,
"description": "Notes on must-haves or things to avoid"
},
"is_first_interaction": {
"type": "boolean",
"description": "Is this the first interaction with this client? Default: true"
}
}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
},
"title": "Create Person"
}{
"name": "get_chat_messages",
"description": "Retrieve chat message history for a specific person (client). Returns messages in reverse chronological order.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"person_id"
],
"properties": {
"limit": {
"type": "integer",
"maximum": 100,
"minimum": 1,
"description": "Max messages to return (default: 50)"
},
"cursor": {
"type": "string",
"description": "Pagination cursor from a previous response"
},
"person_id": {
"type": "string",
"description": "The UUID of the person"
}
}
},
"annotations": {
"readOnlyHint": true
},
"title": "Get Chat Messages"
}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.numbru/client-compass"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/com.numbru/client-compass"}) over MCP.
create_person ~444 tokensgenerate_compass ~385 tokensbatch_create_persons ~303 tokenscomplete_profile ~289 tokensupdate_profile ~234 tokensStatic 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:
[](https://glimind.com/server/mcp-registry%2Fcom.numbru%2Fclient-compass?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fcom.numbru%2Fclient-compass?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.numbru%2Fclient-compass.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.numbru%2Fclient-compass.svg :target: https://glimind.com/server/mcp-registry%2Fcom.numbru%2Fclient-compass?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:012a10c2e0b16f51…, first seen 2026-10-22, included at leaf 48196 of 74,898. Version history · verify what your client received.
Compare: most reliable data servers · most reliable productivity servers · most reliable ml servers · most reliable communication servers · most reliable devops servers
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.
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"
}
}
}
As of 2026-10-26 19:00 UTC, the Numbru Client Compass MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Numbru Client Compass MCP server advertises 11 tools, including batch_create_persons, complete_profile, create_person, generate_compass, get_chat_messages.
Point your MCP client at this streamable-http endpoint: https://numbru-mcp-server.numbru.workers.dev
Glimind scanned all 11 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.
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.