_ registry / mcp http-sse · checked 13h ago

retainer

https://useretainer.com

Registry code: b8c194875d6f4938

api record

Free tools from Retainer (useretainer.com), the CRM for independent consultants and fractional executives. map_stakeholders: map and prioritize the people on a client account. calculate_consulting_rate: what to charge, hourly, daily, or as a retainer. check_capacity: whether there is room for another client. rank_client_profitability: which clients pay best per hour. find_neglected_relationships: who has gone too long without contact. Fill in what you can from the conversation, then share the returned link so the user can adjust the numbers on the site.

endpoint
https://useretainer.com/mcp/
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
223ms

last good check

priced tools
0

of 5 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ used through this hub 30 days

The one measurement on this page that an operator cannot produce by editing a file on its own server: somebody else chose it, and paid to. Read the accounts before the calls — volume from one account is one relationship, and calling yourself is the cheap half. Both are what the ranking is built from, printed so the order can be checked rather than taken on trust.

accounts
0

distinct, expensive to fake

calls served
0

successful, last 30 days

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 5 tools
5 never probed 0 of 5 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • check_capacity unknown 13h ago

    Check whether an independent consultant has room for another client: available billable hours, current utilization, and whether they are under target, over target, or overcommitted. Use when someone asks if they can take on new work or feels stretched. Returns a link that opens Retainer's free capacity calculator with these numbers.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "committed_hours_per_week"
  ],
  "properties": {
    "total_hours_per_week": {
      "type": "number",
      "default": 45,
      "maximum": 100,
      "minimum": 1,
      "description": "Total hours the consultant works per week. Default 45."
    },
    "committed_hours_per_week": {
      "type": "number",
      "maximum": 100,
      "minimum": 0,
      "description": "Client hours per week already committed across all current engagements."
    },
    "target_utilization_percent": {
      "type": "number",
      "default": 80,
      "maximum": 100,
      "minimum": 10,
      "description": "Share of billable hours they want filled, leaving a buffer for overruns. Default 80."
    },
    "non_billable_hours_per_week": {
      "type": "number",
      "default": 15,
      "maximum": 100,
      "minimum": 0,
      "description": "Weekly hours on admin, sales, and business development that nobody pays for. Default 15."
    }
  }
}
    arguments 36 lines
  • calculate_consulting_rate unknown 13h ago

    Work out what an independent consultant should charge: minimum and recommended hourly rate, day rate, monthly equivalent, and a suggested monthly retainer or project day rate. Use when someone asks what to charge, how to price a retainer, or whether their rate is too low. Ask for their income goal if you don't know it; the other inputs have sensible defaults. Returns a link that opens Retainer's free rate calculator with these numbers.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "target_income"
  ],
  "properties": {
    "expenses": {
      "type": "number",
      "default": 12000,
      "maximum": 100000000,
      "minimum": 0,
      "description": "Yearly business expenses (software, insurance, travel...). Default 12000."
    },
    "pricing_model": {
      "enum": [
        "retainer",
        "project"
      ],
      "type": "string",
      "default": "retainer",
      "description": "'retainer' for a monthly retainer price, 'project' for a fixed-project day rate."
    },
    "target_income": {
      "type": "number",
      "maximum": 100000000,
      "minimum": 0,
      "description": "Take-home income the consultant wants per year, in dollars."
    },
    "working_weeks": {
      "type": "number",
      "default": 46,
      "maximum": 52,
      "minimum": 1,
      "description": "Weeks worked per year after vacation and holidays. Default 46."
    },
    "margin_percent": {
      "type": "number",
      "default": 20,
      "maximum": 80,
      "minimum": 0,
      "description": "Profit margin on top of income and expenses, as a percent. Default 20."
    },
    "billable_hours_per_week": {
      "type": "number",
      "default": 25,
      "maximum": 80,
      "minimum": 1,
      "description": "Hours per week actually billed to clients, not total hours worked. Default 25."
    }
  }
}
    arguments 52 lines
  • find_neglected_relationships unknown 13h ago

    Check which clients, past clients, or referral sources a consultant has gone too long without talking to. Sorts contacts by days of silence into healthy (<30 days), cooling (30+), neglected (60+), and urgent (90+), with a suggested next step for each and an overall network health score. Use when someone asks who to follow up with or worries their pipeline is drying up. Returns a link that opens Retainer's free BD neglect detector with these contacts.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "contacts"
  ],
  "properties": {
    "contacts": {
      "type": "array",
      "items": {
        "type": "object",
        "required": [
          "name",
          "last_contact"
        ],
        "properties": {
          "name": {
            "type": "string",
            "maxLength": 80,
            "minLength": 1,
            "description": "Contact name, optionally with company, e.g. \"Sarah Chen (Aldgate Finance)\"."
          },
          "last_contact": {
            "type": "string",
            "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
            "description": "Date of the last real conversation, YYYY-MM-DD."
          }
        }
      },
      "maxItems": 50,
      "minItems": 1
    }
  }
}
    arguments 34 lines
  • map_stakeholders unknown never probed

    Sort stakeholders on a power/interest grid (Mendelow's matrix) into Manage Closely, Keep Satisfied, Keep Informed, and Monitor, with what to do for each group. Returns a link that opens the finished map in Retainer's free stakeholder mapping tool. Scores are relative: what matters is where people sit compared to each other, not the exact number.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "stakeholders"
  ],
  "properties": {
    "title": {
      "type": "string",
      "maxLength": 120,
      "description": "Optional map title, e.g. the client or project name."
    },
    "stakeholders": {
      "type": "array",
      "items": {
        "type": "object",
        "required": [
          "name",
          "power",
          "interest"
        ],
        "properties": {
          "name": {
            "type": "string",
            "maxLength": 80,
            "minLength": 1,
            "description": "Person's name and/or role, e.g. \"Dana Lee (CFO)\"."
          },
          "note": {
            "type": "string",
            "maxLength": 200,
            "description": "Optional short note, e.g. what they care about."
          },
          "power": {
            "type": "number",
            "maximum": 100,
            "minimum": 0,
            "description": "0-100. Ability to help or block the outcome: budget authority, veto power, organizational influence. 50 or more counts as high."
          },
          "interest": {
            "type": "number",
            "maximum": 100,
            "minimum": 0,
            "description": "0-100. How much the outcome affects them or how closely they are paying attention. 50 or more counts as high."
          }
        }
      },
      "maxItems": 30,
      "minItems": 1
    }
  }
}
    arguments 52 lines
  • rank_client_profitability unknown never probed

    Rank a consultant's clients by revenue per hour, with totals and the average, and flag which clients earn below average. Use when someone asks which clients are worth keeping, which to raise prices on, or why they're busy but not earning more. Returns a link that opens Retainer's free client profitability calculator with these clients.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "clients"
  ],
  "properties": {
    "clients": {
      "type": "array",
      "items": {
        "type": "object",
        "required": [
          "client",
          "monthly_fee",
          "hours_per_month"
        ],
        "properties": {
          "client": {
            "type": "string",
            "maxLength": 80,
            "minLength": 1,
            "description": "Client or engagement name."
          },
          "monthly_fee": {
            "type": "number",
            "maximum": 100000000,
            "minimum": 0,
            "description": "What the client pays per month, in dollars."
          },
          "hours_per_month": {
            "type": "number",
            "maximum": 10000,
            "minimum": 0,
            "description": "Hours the client actually takes per month, including calls and email."
          }
        }
      },
      "maxItems": 30,
      "minItems": 1
    }
  }
}
    arguments 42 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id b8c194875d6f4938.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/b8c194875d6f4938/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/b8c194875d6f4938/badge.svg)](https://brick.blue/agent/b8c194875d6f4938?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
90%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.