numbrU MCP server

• Registry namecom.numbru/client-compassverified in the MCP registry

The registry name sits under numbru.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

• Stateanswerschecked 2026-10-24
• Tools11
• Server calls itselfnumbrU API
• Server version1.0.0
• Protocol version2025-06-18

On 2026-10-24 the server answered initialize and tools/list without a sign-in. First answer in 206 ms.

• Its tools do brief a colleague before a discovery call, but not frame a price around the outcome a buyer wants.
• Checked on 4 of the 7 days it takes to judge reliability.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

• INITE MCP scoreafter a weeka score needs 7 daily checks: 4 so far
• What an agent can do with it1 of 2 use cases
• Answeredmeasuring4 of the 7 daily checks it takes to print a share
• Median first answer213 ms
• Space in an agent's context≈ 2,263 tokensthe definitions of all its tools (11), which an agent carries on every turn
• Tool definitionsB · 83 of 100
• Typed results0 of 11 toolsdeclared outputSchema: results come typed, read once

• Not saying whether it only reads or can destroy: 11 of 11

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

• health_check

  Check the health status of the numbrU API

• 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.

• 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.

• 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…

• 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…

• 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

  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)…