mcpbeat Sign in

Client Compass MCP Server

answering

Client Compass is answering right now. Last checked 10 min ago. It exposes 11 tools.

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

The linked repository no longer exists on GitHub — it was deleted or made private.

Uptime history 91 days of history · worst day 91%
91 days agonow
100.0%
Uptime 24h
91 of 91 checks
11
Tools
read from the server
205 ms
Response time
average over 24h
OAuth sign-in
Access
streamable-http

What changed 15

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 15 September 2026. No other catalogue keeps this.

22 Oct 4 tool descriptions were rewritten5 times that day create_person, generate_compass, get_person and 1 more
22 Oct a tool changed the parameters it asks for generate_compass
17 Oct a tool changed the parameters it asks for list_people
23 Sep a tool description was rewritten generate_compass
15 Sep 6 tool descriptions were rewritten7 times that day batch_create_persons, complete_profile, create_person and 3 more
and 2 more, back to 15 September 2026

This one has been quiet for a while

Quiet is not dead — but it is worth knowing when it wakes up, or when someone else takes it over. We watch the repository and tell you either way.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 10 min ago.

run in your terminal
claude mcp add client-compass --transport http https://numbru-mcp-server.numbru.workers.dev
Settings → Connectors → Add custom connector, then paste this address
https://numbru-mcp-server.numbru.workers.dev
~/.codex/config.toml
[mcp_servers.client-compass]
url = "https://numbru-mcp-server.numbru.workers.dev"
.cursor/mcp.json
{
  "mcpServers": {
    "client-compass": {
      "url": "https://numbru-mcp-server.numbru.workers.dev"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "client-compass": {
      "type": "http",
      "url": "https://numbru-mcp-server.numbru.workers.dev"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Available tools 11

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

person
create_person
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.
get_person
Retrieve a single person (client) by their ID. Returns contact details only, not the Lowdown: for any read, card or "go deeper", call generate_compass.
batch
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 compass_summary_text and all three Start Here items in full.
chat
get_chat_messages
Retrieve chat message history for a specific person (client). Returns messages in reverse chronological order.
complete
complete_profile
Complete the user's profile (one-time signup). Sets name, profession, and generates a User Compass. Required before creating clients.
generate
generate_compass
Get the Lowdown on a person from the numbrU engine. Call with depth "card" first (the default): it returns a short card with KNOW, AVOID, and INSTEAD. If the user has described the moment (a listing meeting, a negotiation, a first call), pass it in context so the card fits that moment. When the user asks to go deeper, call again with the same name, dob, vertical, and context and depth "full" for the Deeper Details: how they decide, what earns their trust, the signs to watch for, and how to communicate. IMPORTANT: present the returned output verbatim, exactly as formatted, preserving every heading. Do not summarize, reword, reorder, condense into tables, or describe the sections instead of showing them. The formatting is the product. Get every read from generate_compass only: do not call create_person, list_people, or get_person to get or deepen a read, and do not save the person unless the user asks. In any note you add after the output, refer to the person by first name or "they", never he/she.
get
get_me
Retrieve the authenticated user's profile information.
health
health_check
Check the health status of the numbrU API
people
list_people
Retrieve all people (clients) for the authenticated user. Optionally search by name. Returns contact details only, not the Lowdown: for any read, card or "go deeper", call generate_compass.
profile
update_profile
Update the user's profile settings. Can change name, profession, phone, DOB, or custom prompt.
send
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.

Endpoints

URLTransportStateLatencyChecked
https://numbru-mcp-server.numbru.workers.dev streamable-http sign-in 201 ms 10 min ago

Alternatives to Client Compass

same job, measured the same way
Veris
by vighriday

Behavioral verification intelligence for AI coding agents. 17 MCP tools. Local-first. MIT.

65 installs/wk local only
Commerce Intelligence
by phoslabs

Behavioral-science tools for commerce: checkout, drop-off, pricing, churn. 5 free calls, then paid.

8 tools answering
Squad
by meetsquad

Decision intelligence for product teams. Turn scattered feedback into signal you can act on.

answering
Maxio MCP
by servosity

Open, local revenue-intelligence CLI for Maxio Advanced Billing - MRR waterfalls

local only
LotsInvoice
by lotsinvoice

Professional invoicing: exact invoices and estimates, a client portal and reminders, from any agent.

answering
Horus Flow MCP
by horustechltd

Institutional crypto & equity orderflow intelligence for AI trading agents.

98 installs/wk local only
Constellation
by shiftinbits

Code Intelligence Platform for AI Coding Agents

184 installs/wk local only
Emulo
by ohad6k

Mine your AI coding session logs into a you.md profile with dated receipts, for an agent to read.

150 installs/wk local only

Client Compass — questions

Answers built from our own checks of this server.

What can Client Compass do?
It exposes 11 tools, read directly from the server on our last check. Among them: batch_create_persons, complete_profile, create_person, generate_compass, get_chat_messages, get_me and 5 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Client Compass working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 205 ms. The bar chart above shows every period we have measured.
Is Client Compass still maintained?
The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.
How do I connect Client Compass?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.
How do you sign in to Client Compass?
No API key is involved. Client Compass answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.
How fast is Client Compass?
It answers our handshake in 205 ms on average, which is faster than 70% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.