Home / MCP registry index / io.usefulapi/follow-up-boss

Follow Up Boss MCP by usefulapi

io.usefulapi/follow-up-boss in the official MCP registry. Endpoint https://follow-up-boss.usefulapi.io/mcp. Source: github.com/m190/usefulapi-mcp.

The registry describes it as: Search Follow Up Boss leads, review calls and deals, and add notes, tasks and deal updates.

We read its 25 tools on 2026-10-31. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

Claude Code

claude mcp add --transport http follow-up-boss https://follow-up-boss.usefulapi.io/mcp

Cursor: ~/.cursor/mcp.json

{
  "mcpServers": {
    "follow-up-boss": {
      "url": "https://follow-up-boss.usefulapi.io/mcp"
    }
  }
}

VS Code

code --add-mcp '{"name":"follow-up-boss","type":"http","url":"https://follow-up-boss.usefulapi.io/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which.

Let Claude Code check servers as it adds them

With the free lazaretto-guard plugin installed, when Claude Code adds a server for you or writes one into an MCP config, the plugin reads the server's tools first and asks you if one of our rules matches. Install it, restart Claude Code, then ask it to run the command above.

Install lazaretto-guard

claude plugin marketplace add jamesdfinance-dev/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-plugins

Tools it advertises

fub_get_identity fub_search_people fub_get_person fub_check_duplicate_person fub_list_events fub_list_calls fub_list_text_messages fub_list_tasks fub_list_appointments fub_list_deals fub_list_pipelines fub_list_stages fub_list_users fub_list_custom_fields fub_list_action_plans fub_list_person_action_plans fub_lead_source_report fub_send_lead_event fub_update_person fub_add_note fub_log_call fub_create_task fub_update_task fub_create_deal fub_update_deal

Tool changes

We compare every full read of this server with the one before. No change in what its tools say has been seen since we started keeping this record on 2026-10-30.

Fingerprint of its tools at our last full read (2026-10-31): 0b2315164c284e88. A client can hash the tools it is served the same way and compare; the full value and a hash per tool are in this page as JSON.

Run this server? Show the check in your README

The badge reflects the latest weekly read:

Markdown

[![MCP tool check](https://lazaretto.dev/mcp-registry/io-usefulapi-follow-up-boss/badge.svg)](https://lazaretto.dev/mcp-registry/io-usefulapi-follow-up-boss)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.