Client Compass

com.numbru/client-compass

Behavioral intelligence for client-facing professionals. Know who you're walking into.

healthy

status

tools exposed

1935ms

connect latency

f8520620fdd2

schema fingerprint

Tools (11)

health_check

Check the health status of the numbrU API

list_people

Retrieve all people (clients) for the authenticated user. Optionally search by name.

get_person

Retrieve a single person (client) by their ID, including their Client Compass data.

create_person

Create a new person (client). Generates their Client Compass automatically. Requires the user to have a profession set.

batch_create_persons

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

get_chat_messages

Retrieve chat message history for a specific person (client). Returns messages in reverse chronological order.

send_chat_message

Send a chat message about a specific person (client). The AI will respond with tailored advice based on the client's Compass profile.

get_me

Retrieve the authenticated user's profile information.

complete_profile

Complete the user's profile (one-time signup). Sets name, profession, and generates a User Compass. Required before creating clients.

update_profile

Update the user's profile settings. Can change name, profession, phone, DOB, or custom prompt.

generate_compass

Generate a numbrU Compass profile for a person using the Compass engine. Returns personality insights, communication style, and relationship strategies.

Endpoint

https://numbru-mcp-server.numbru.workers.dev
Category: Communication · Last checked: 2026-08-15T09:11:01Z

Monitor your own MCP server

Get alerted the moment yours goes down, a tool schema drifts, or an upstream silently breaks.

Get early access

How we measure →

What this means. This server responded to the MCP handshake and listed its tools without authentication. The schema fingerprint lets us flag if tool signatures silently change (schema drift) between checks.