Skip to content

client-compass MCP server

com.numbru/client-compassnumbru.comstreamable-httpv1.0.0Scanned

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

11 tools: 1 do something that can't be undone, 6 change things and 4 only read.

Tools: 0 delete, 1 irreversible, 6 write, 4 read.
  • Reads private data · 1
  • Reads text others write · 1
  • Can send data out · 3
  • No findings

Sign-in required, OAuth metadata published. Remote posture

Anlyon alternative

7 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

What the client-compass MCP server can do

The client-compass MCP server is published by numbru.com, a domain the MCP Registry verified. It has 11 tools. It can do things that cannot be undone, such as sending, paying or publishing (send_chat_message) and create or change data (6 tools: health_check, create_person, batch_create_persons, complete_profile and 2 more), but cannot delete data. 4 tools only read.

1 tool reads private data (get_chat_messages); 1 tool brings in text other people can write (get_chat_messages); 3 tools can send data out of your system (send_chat_message, complete_profile and update_profile). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint asks for sign-in and publishes OAuth metadata, and its tools changed once since Anlyon Radar first saw them.

Last scanned Oct 29, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

11 tools

Can't be undone 1Claude Code: ask
  • send_chat_messageSend a chat message about a specific person (client).Can send data outNo findings

    Why it is in this group

    • The name "send_chat_message" says "send": a word for sending, and what is sent cannot be taken back.

    What it can reach

    • outboundThe name "send_chat_message" says "send": it sends or publishes something to other people.
    Description, as the server wrote it
    Send a chat message about a specific person (client). The AI will respond with tailored advice based on the client's Compass profile.
Changes things 6Claude Code: ask
  • batch_create_personsCreate up to 10 people (clients) in parallel and generate a Client Compass for each.No findings

    Why it is in this group

    • The name "batch_create_persons" says "create": a word for a change.
    Description, as the server wrote it
    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.
  • complete_profileComplete the user's profile (one-time signup).Can send data outNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    What it can reach

    • outboundThe input takes a destination (input.phone): what the tool writes goes there.
    Description, as the server wrote it
    Complete the user's profile (one-time signup). Sets name, profession, and generates a User Compass. Required before creating clients.
  • create_personSave a new person (client) to the user's people list.No findings

    Why it is in this group

    • The name "create_person" says "create": a word for a change.
    Description, as the server wrote it
    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.
  • generate_compassGet the Lowdown on a person from the numbrU engine.No findings

    Why it is in this group

    • The name "generate_compass" says "generate": a word for a change.
    Description, as the server wrote it
    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.
  • health_checkCheck the health status of the numbrU APINo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Check the health status of the numbrU API
  • update_profileUpdate the user's profile settings.Can send data outNo findings

    Why it is in this group

    • The name "update_profile" says "update": a word for a change.

    What it can reach

    • outboundThe input takes a destination (input.phone): what the tool writes goes there.
    Description, as the server wrote it
    Update the user's profile settings. Can change name, profession, phone, DOB, or custom prompt.
Only reads 4Show 4 read-only tools
  • get_chat_messagesRetrieve chat message history for a specific person (client).Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "get_chat_messages" says "get": a word for reading.

    What it can reach

    • private-dataThe name "get_chat_messages" says "get" and "chat": it reads messages.
    • private-dataThe description's first sentence says "retrieve" and "chat": it reads messages.
    • untrusted-inputThe name "get_chat_messages" says "get" and "chat": it reads messages, which other people can write.
    • untrusted-inputThe description's first sentence says "retrieve" and "chat": it reads messages, which other people can write.
    Description, as the server wrote it
    Retrieve chat message history for a specific person (client). Returns messages in reverse chronological order.
  • get_meRetrieve the authenticated user's profile information.No findings

    Why it is in this group

    • The name "get_me" says "get": a word for reading.
    Description, as the server wrote it
    Retrieve the authenticated user's profile information.
  • get_personRetrieve a single person (client) by their ID.No findings

    Why it is in this group

    • The name "get_person" says "get": a word for reading.
    Description, as the server wrote it
    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.
  • list_peopleRetrieve all people (clients) for the authenticated user.No findings

    Why it is in this group

    • The name "list_people" says "list": a word for reading.
    Description, as the server wrote it
    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.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

3 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 1 untrusted-input tool breaks every one.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out3
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
deny to break every path
{
  "permissions": {
    "deny": [
      "mcp__client-compass__get_chat_messages"
    ]
  }
}

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Sign-in required, OAuth metadata published

Looked at Nov 20, 2026, 18:43 UTC, unchanged since Nov 6, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
401
tools/list served without credentials
no
Tools that change things, listed without credentials
0
Protocol version
not observed
WWW-Authenticate on 401
yes
resource_metadata in WWW-Authenticate
https://numbru-mcp-server.numbru.workers.dev/.well-known/oauth-protected-resource
RFC 9728 protected resource metadata
https://numbru-mcp-server.numbru.workers.dev/.well-known/oauth-protected-resource
Authorization servers
https://numbru-mcp-server.numbru.workers.dev
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
no

Posture changes

  1. Nov 6, 2026
    • HTTP status of an anonymous initialize: 200 to 401
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 7 to 0
    • Protocol version: 2025-06-18 to none
    • WWW-Authenticate on 401: not observed to yes
    • resource_metadata in WWW-Authenticate: none to https://numbru-mcp-server.numbru.workers.dev/.well-known/oauth-protected-resource
    • RFC 9728 protected resource metadata: none to https://numbru-mcp-server.numbru.workers.dev/.well-known/oauth-protected-resource
    • Authorization servers: none to https://numbru-mcp-server.numbru.workers.dev
    • Dynamic client registration: not observed to yes
    • Client ID metadata documents: not observed to no

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. HTTP status of an anonymous initialize: 200 -> 401; tools/list served without credentials: yes -> no; Tools that change things, listed without credentials: 7 -> 0 (and 7 more).View diff
    • HTTP status of an anonymous initialize: 200 to 401
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 7 to 0
    • Protocol version: 2025-06-18 to none
    • WWW-Authenticate on 401: not observed to yes
    • resource_metadata in WWW-Authenticate: none to https://numbru-mcp-server.numbru.workers.dev/.well-known/oauth-protected-resource
    • RFC 9728 protected resource metadata: none to https://numbru-mcp-server.numbru.workers.dev/.well-known/oauth-protected-resource
    • Authorization servers: none to https://numbru-mcp-server.numbru.workers.dev
    • Dynamic client registration: not observed to yes
    • Client ID metadata documents: not observed to no
  2. Tools4 changed.~4 changedView diff

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http client-compass https://numbru-mcp-server.numbru.workers.dev
claude mcp add --transport http client-compass https://numbru-mcp-server.numbru.workers.dev

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__client-compass__list_people",
      "mcp__client-compass__get_person",
      "mcp__client-compass__get_chat_messages",
      "mcp__client-compass__get_me"
    ],
    "ask": [
      "mcp__client-compass__health_check",
      "mcp__client-compass__create_person",
      "mcp__client-compass__batch_create_persons",
      "mcp__client-compass__send_chat_message",
      "mcp__client-compass__complete_profile",
      "mcp__client-compass__update_profile",
      "mcp__client-compass__generate_compass"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as client-compass. Review it before you use it.

Capability tags behind 4 rules
  • mcp__client-compass__get_chat_messages private-data, untrusted-input
  • mcp__client-compass__send_chat_message outbound
  • mcp__client-compass__complete_profile outbound
  • mcp__client-compass__update_profile outbound

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.numbru/client-compass/verify?hash=28ce0e1dc942ba73f1e79a2ba76f1308e2d396f2bac9c90f8508e89ffd96dcd6" | jq -e '.changed == false'

Pinned hash 28ce0e1dc942, from Oct 29, 2026, 12:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.numbru/client-compass/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.numbru/client-compass
[![Anlyon Radar](https://radar.anlyon.com/badge/com.numbru/client-compass.svg)](https://radar.anlyon.com/servers/com.numbru/client-compass)

Source: MCP Registry · repository. Synced Nov 18, 2026, 00:17 UTC.

client-compass MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the client-compass MCP server safe?

No scan can promise that. What its definitions show: 11 tools, 7 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the client-compass MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the client-compass MCP server do things that cannot be undone?

Yes. 1 tool can send, pay, publish or merge: send_chat_message.

What tools does the client-compass MCP server have?

11 tools: 1 irreversible, 6 write, 4 read. send_chat_message, health_check, create_person, batch_create_persons, complete_profile, update_profile, generate_compass, list_people and 3 more.

Does the client-compass MCP server need sign-in or OAuth?

Yes. Its remote endpoint answered 401 without credentials, and it publishes OAuth protected resource metadata (RFC 9728); its authorization server supports dynamic client registration.

Does the client-compass MCP server send data to outside services?

3 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): send_chat_message, complete_profile and update_profile.

Has the client-compass MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Oct 29, 2026. Every change is on this page and in its Atom feed.