Follow Up Boss MCP by usefulapi
io.usefulapi/follow-up-bossusefulapi.iostreamable-httpv1.44.5Scanned
Search Follow Up Boss leads, review calls and deals, and add notes, tasks and deal updates.
25 tools: 8 can delete or cancel things, 1 change things and 16 only read.
- Reads private data · 7
- Reads text others write · 2
- Can send data out · 2
- 2 findings
The remote endpoint did not answer the last look. Remote posture
Anlyon alternative
9 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 Follow Up Boss MCP by usefulapi can do
The Follow Up Boss MCP by usefulapi is published by usefulapi.io, a domain the MCP Registry verified. It has 25 tools. It can delete or cancel things (8 tools: fub_send_lead_event, fub_update_person, fub_add_note, fub_log_call and 4 more) and create or change data (1 tool: fub_check_duplicate_person). 16 tools only read.
7 tools read private data (fub_get_identity, fub_search_people, fub_get_person and 4 more); 2 tools bring in text other people can write (fub_list_events and fub_list_text_messages); 2 tools can send data out of your system (fub_check_duplicate_person and fub_send_lead_event). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.
The fixed checks matched 2 findings (credentials-mention and annotation-conflict). Each one comes with the text it matched.
Its tools changed once since Anlyon Radar first saw them.
Last scanned Oct 25, 2026, version 1.44.5.
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.
25 tools
Deletes or cancels 8Claude Code: deny
fub_add_noteAdd a note to a contact's timeline.No findings
Why it is in this group
- The name "fub_add_note" says "add": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Add a note to a contact's timeline. FUB: POST /v1/notes.
Annotations the server declares
- title: Add a note
- destructiveHint: true
fub_create_dealCreate a deal in a pipeline stage (stage ids from fub_list_pipelines).No findings
Why it is in this group
- The name "fub_create_deal" says "create": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Create a deal in a pipeline stage (stage ids from fub_list_pipelines). Include userIds — a deal with no users is invisible to agents. FUB: POST /v1/deals.
Annotations the server declares
- title: Create a deal
- destructiveHint: true
fub_create_taskCreate a task on a contact, assigned to a user (assignedUserId or assignedTo is required).No findings
Why it is in this group
- The name "fub_create_task" says "create": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Create a task on a contact, assigned to a user (assignedUserId or assignedTo is required). FUB: POST /v1/tasks.
Annotations the server declares
- title: Create a task
- destructiveHint: true
fub_log_callRecord a phone call made or received outside FUB, with its outcome.1 finding
Why it is in this group
- The name "fub_log_call" says "log": a word for reading.
- The server marks it destructive (destructiveHint: true).
Findings
- Warn
The server marks "fub_log_call" destructive (destructiveHint: true), and its name says "log", a word for reading.
What this check looks forMatched text
annotations: {"destructiveHint":true}; The name "fub_log_call" says "log": a word for reading.
Description, as the server wrote it Record a phone call made or received outside FUB, with its outcome. Does not place a call. FUB: POST /v1/calls.
Annotations the server declares
- title: Log a call
- destructiveHint: true
fub_send_lead_eventAdd a new lead or record activity on an existing one — FUB's documented way to create leads.Can send data outNo findings
Why it is in this group
- The name "fub_send_lead_event" says "send": a word for sending, and what is sent cannot be taken back.
- The server marks it destructive (destructiveHint: true).
What it can reach
- outboundThe name "fub_send_lead_event" says "send": it sends or publishes something to other people.
Description, as the server wrote it Add a new lead or record activity on an existing one — FUB's documented way to create leads. FUB de-duplicates by email/phone (or use person.id to target a contact), routes the lead per Lead Flow, notifies the agent and runs action plans for Registration / Inquiry types. A 204 means the lead flow for this source is archived and the event was ignored. FUB: POST /v1/events.
Annotations the server declares
- title: Send in a lead / lead event
- destructiveHint: true
fub_update_dealUpdate a deal — move it to another stage, change price, dates, people or agents.No findings
Why it is in this group
- The name "fub_update_deal" says "update": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Update a deal — move it to another stage, change price, dates, people or agents. peopleIds/userIds replace the full list. FUB: PUT /v1/deals/{id}.
Annotations the server declares
- title: Update a deal
- destructiveHint: true
fub_update_personUpdate a contact's fields.No findings
Why it is in this group
- The name "fub_update_person" says "update": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Update a contact's fields. CAUTION: `tags` REPLACES all tags unless mergeTags is true; `phones` and `emails` REPLACE the full list (send existing ones too). Setting contacted=true pauses action plans. source/sourceUrl cannot be changed after creation. FUB: PUT /v1/people/{id}.
Annotations the server declares
- title: Update a person
- destructiveHint: true
fub_update_taskUpdate a task — mark it complete, rename, retype or reassign it.No findings
Why it is in this group
- The name "fub_update_task" says "update": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Update a task — mark it complete, rename, retype or reassign it. FUB: PUT /v1/tasks/{id}.
Annotations the server declares
- title: Update a task
- destructiveHint: true
Changes things 1Claude Code: ask
fub_check_duplicate_personCheck if a contact with this email or phone already exists anywhere in the account (even ones this user cannot see) and who it is assigned to.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.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- outboundThe input takes a destination (input.phone): what the tool writes goes there.
Description, as the server wrote it Check if a contact with this email or phone already exists anywhere in the account (even ones this user cannot see) and who it is assigned to. Use before adding a lead. FUB: GET /v1/people/checkDuplicate.
Annotations the server declares
- title: Check whether a person exists
- readOnlyHint: true
Only reads 16Show 16 read-only tools
fub_get_identityWho the credential belongs to: the account (id, domain, owner) and the authenticated user.Reads private data1 finding
Why it is in this group
- The name "fub_get_identity" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "credential": it reads secrets.
Findings
- Info
The description mentions "credential".
What this check looks forMatched text
description: "Who the credential belongs to: the account (id, domain, ow..."
Description, as the server wrote it Who the credential belongs to: the account (id, domain, owner) and the authenticated user. A cheap way to confirm the API key works. FUB: GET /v1/identity.
Annotations the server declares
- title: Get identity
- readOnlyHint: true
fub_get_personFetch one contact by id.Reads private dataNo findings
Why it is in this group
- The name "fub_get_person" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "fetch" and "contact": it reads contacts.
Description, as the server wrote it Fetch one contact by id. Pass fields="allFields" to include custom fields and everything else. FUB: GET /v1/people/{id}.
Annotations the server declares
- title: Get one person
- readOnlyHint: true
fub_lead_source_reportCount leads from lead sources (e.g.No findings
Why it is in this group
- The description's first verb is "count": a word for reading.
Description, as the server wrote it Count leads from lead sources (e.g. Zillow) per assigned agent, how many reached the closed stage(s) (conversion rate), and leads per lender user (e.g. Zillow Home Loans loan officers). Use it to count instead of paging through fub_search_people. The numbers approximate FUB's in-app Lead Source report, which has no API, and cover only the people the API key can see (use an owner, admin or broker key for the whole account). At most 100 FUB requests per call (one per count). FUB: GET /v1/people totals, GET /v1/users.
Annotations the server declares
- title: Lead source report by agent
- readOnlyHint: true
fub_list_action_plansThe account's action plans (drip campaigns): id, name and status.No findings
Why it is in this group
- The name "fub_list_action_plans" says "list": a word for reading.
Description, as the server wrote it The account's action plans (drip campaigns): id, name and status. Gives the names for the actionPlanId values of fub_list_person_action_plans. FUB: GET /v1/actionPlans.
Annotations the server declares
- title: List action plans
- readOnlyHint: true
fub_list_appointmentsCalendar appointments with invitees, type and outcome.Reads private dataNo findings
Why it is in this group
- The name "fub_list_appointments" says "list": a word for reading.
What it can reach
- private-dataThe description's first sentence says "calendar": it reads calendars.
Description, as the server wrote it Calendar appointments with invitees, type and outcome. Filter by person, user, or a start+end window (both required together). FUB: GET /v1/appointments.
Annotations the server declares
- title: List appointments
- readOnlyHint: true
fub_list_callsLogged phone calls with outcome, direction and duration.No findings
Why it is in this group
- The name "fub_list_calls" says "list": a word for reading.
Description, as the server wrote it Logged phone calls with outcome, direction and duration. Filter by person or number. FUB: GET /v1/calls.
Annotations the server declares
- title: List calls
- readOnlyHint: true
fub_list_custom_fieldsThe account's contact custom fields: label, API name (customXxx), type and dropdown choices.Reads private dataNo findings
Why it is in this group
- The name "fub_list_custom_fields" says "list": a word for reading.
What it can reach
- private-dataThe description's first sentence says "contact": it reads contacts.
Description, as the server wrote it The account's contact custom fields: label, API name (customXxx), type and dropdown choices. Use the name as a key in customFields. FUB: GET /v1/customFields.
Annotations the server declares
- title: List custom fields
- readOnlyHint: true
fub_list_dealsDeals (transactions) with stage, price, people, agents and commission.No findings
Why it is in this group
- The name "fub_list_deals" says "list": a word for reading.
Description, as the server wrote it Deals (transactions) with stage, price, people, agents and commission. Filter by pipeline, user, person or status. The response metadata includes totalByStageId. FUB: GET /v1/deals.
Annotations the server declares
- title: List deals
- readOnlyHint: true
fub_list_eventsLead activity: registrations, inquiries, viewed/saved properties, website visits, etc.Reads text others writeNo findings
Why it is in this group
- The name "fub_list_events" says "list": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "website": it reads web pages, which anyone can write.
Description, as the server wrote it Lead activity: registrations, inquiries, viewed/saved properties, website visits, etc. Filter by person or type. Some events are only visible in the FUB app. FUB: GET /v1/events.
Annotations the server declares
- title: List lead events
- readOnlyHint: true
fub_list_person_action_plansWhich people are on which action plan, with the status of each assignment (e.g.No findings
Why it is in this group
- The name "fub_list_person_action_plans" says "list": a word for reading.
Description, as the server wrote it Which people are on which action plan, with the status of each assignment (e.g. "Running", "Paused"). Give personId for one contact's plans, or actionPlanId for everyone on one plan. For many contacts, list each active plan's people (limit 100; page with offset until _metadata.total is covered) instead of one call per contact. Shows classic action plans only; Automations 2.0 are in fub_list_person_automations when that tool is listed. FUB: GET /v1/actionPlansPeople.
Annotations the server declares
- title: List action plans applied to people
- readOnlyHint: true
fub_list_pipelinesDeal pipelines with their stages (the stage ids that fub_create_deal / fub_update_deal take).No findings
Why it is in this group
- The name "fub_list_pipelines" says "list": a word for reading.
Description, as the server wrote it Deal pipelines with their stages (the stage ids that fub_create_deal / fub_update_deal take). FUB: GET /v1/pipelines.
Annotations the server declares
- title: List deal pipelines
- readOnlyHint: true
fub_list_stagesContact lifecycle stages (Lead, Nurture, Past Client, Trash…) with people counts — the names fub_search_people and fub_update_person take as "stage".Reads private dataNo findings
Why it is in this group
- The name "fub_list_stages" says "list": a word for reading.
What it can reach
- private-dataThe description's first sentence says "contact": it reads contacts.
Description, as the server wrote it Contact lifecycle stages (Lead, Nurture, Past Client, Trash…) with people counts — the names fub_search_people and fub_update_person take as "stage". FUB: GET /v1/stages.
Annotations the server declares
- title: List contact stages
- readOnlyHint: true
fub_list_tasksTasks (follow-ups, calls, showings…).No findings
Why it is in this group
- The name "fub_list_tasks" says "list": a word for reading.
Description, as the server wrote it Tasks (follow-ups, calls, showings…). Filter by person, assignee, type, completion, or due window (due="today"|"overdue"|"upcoming"). FUB: GET /v1/tasks.
Annotations the server declares
- title: List tasks
- readOnlyHint: true
fub_list_text_messagesText messages for a person or a phone number (message bodies may be hidden by FUB for privacy).Reads private dataReads text others writeNo findings
Why it is in this group
- The name "fub_list_text_messages" says "list": a word for reading.
What it can reach
- private-dataThe name "fub_list_text_messages" says "list" and "message": it reads messages.
- private-dataThe description's first sentence says "message": it reads messages.
- untrusted-inputThe name "fub_list_text_messages" says "list" and "message": it reads messages, which other people can write.
- untrusted-inputThe description's first sentence says "message": it reads messages, which other people can write.
Description, as the server wrote it Text messages for a person or a phone number (message bodies may be hidden by FUB for privacy). FUB: GET /v1/textMessages.
Annotations the server declares
- title: List text messages
- readOnlyHint: true
fub_list_usersUsers in the account (agents, brokers, lenders) — the ids to assign people, tasks and deals to.No findings
Why it is in this group
- The name "fub_list_users" says "list": a word for reading.
Description, as the server wrote it Users in the account (agents, brokers, lenders) — the ids to assign people, tasks and deals to. FUB: GET /v1/users.
Annotations the server declares
- title: List users (agents)
- readOnlyHint: true
fub_search_peopleSearch contacts and leads.Reads private dataNo findings
Why it is in this group
- The name "fub_search_people" says "search": a word for reading.
What it can reach
- private-dataThe description's first sentence says "search" and "contact": it reads contacts.
Description, as the server wrote it Search contacts and leads. Criteria combine with AND. Name filters are partial matches. Newest first by default. People in the Trash stage are excluded unless includeTrash is true. Not every field is returned by default — pass `fields` (e.g. "allFields" or a comma list) for more. FUB: GET /v1/people.
Annotations the server declares
- title: Search people (contacts/leads)
- readOnlyHint: true
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.
28 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 2 outbound tools breaks every one.
- Reads private data7
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write2
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out2
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
{
"permissions": {
"deny": [
"mcp__follow-up-boss__fub_check_duplicate_person",
"mcp__follow-up-boss__fub_send_lead_event"
]
}
}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.
Looked at Nov 20, 2026, 19:35 UTC, unchanged since Oct 29, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- no
- HTTP status of an anonymous initialize
- not observed
- tools/list served without credentials
- no
- Tools that change things, listed without credentials
- 0
- Protocol version
- not observed
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
The probe stopped: The server redirected a POST to a different request.
Posture changes
- Oct 29, 2026
- Reachable: yes to no
- HTTP status of an anonymous initialize: 200 to none
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 9 to 0
- Protocol version: 2025-06-18 to none
- RFC 9728 protected resource metadata: https://follow-up-boss.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
- Authorization servers: https://follow-up-boss.usefulapi.io to none
- Dynamic client registration: yes to not observed
- Client ID metadata documents: no to not observed
Findings
Matches of fixed checks, with the text they matched.
- Warnfub_log_call
The server marks "fub_log_call" destructive (destructiveHint: true), and its name says "log", a word for reading.
What this check looks forMatched text
annotations: {"destructiveHint":true}; The name "fub_log_call" says "log": a word for reading.
- Infofub_get_identity
The description mentions "credential".
What this check looks forMatched text
description: "Who the credential belongs to: the account (id, domain, ow..."
History
Changes to its tool definitions and to its remote endpoint, newest first.
PostureRemote posture changed. Reachable: yes -> no; HTTP status of an anonymous initialize: 200 -> none; tools/list served without credentials: yes -> no (and 6 more).View diff
- Reachable: yes to no
- HTTP status of an anonymous initialize: 200 to none
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 9 to 0
- Protocol version: 2025-06-18 to none
- RFC 9728 protected resource metadata: https://follow-up-boss.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
- Authorization servers: https://follow-up-boss.usefulapi.io to none
- Dynamic client registration: yes to not observed
- Client ID metadata documents: no to not observed
Tools2 added.+2 addedView diff
- Added:fub_list_action_plansOnly reads
- Added:fub_list_person_action_plansOnly reads
Install
Pinned to version 1.44.5. Values in angle brackets are yours to fill in.
claude mcp add --transport http follow-up-boss https://follow-up-boss.usefulapi.io/mcpclaude mcp add --transport http follow-up-boss https://follow-up-boss.usefulapi.io/mcpRun 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.
{
"permissions": {
"allow": [
"mcp__follow-up-boss__fub_get_identity",
"mcp__follow-up-boss__fub_search_people",
"mcp__follow-up-boss__fub_get_person",
"mcp__follow-up-boss__fub_list_events",
"mcp__follow-up-boss__fub_list_calls",
"mcp__follow-up-boss__fub_list_text_messages",
"mcp__follow-up-boss__fub_list_tasks",
"mcp__follow-up-boss__fub_list_appointments",
"mcp__follow-up-boss__fub_list_deals",
"mcp__follow-up-boss__fub_list_pipelines",
"mcp__follow-up-boss__fub_list_stages",
"mcp__follow-up-boss__fub_list_users",
"mcp__follow-up-boss__fub_list_custom_fields",
"mcp__follow-up-boss__fub_list_action_plans",
"mcp__follow-up-boss__fub_list_person_action_plans",
"mcp__follow-up-boss__fub_lead_source_report"
],
"ask": [
"mcp__follow-up-boss__fub_check_duplicate_person"
],
"deny": [
"mcp__follow-up-boss__fub_send_lead_event",
"mcp__follow-up-boss__fub_update_person",
"mcp__follow-up-boss__fub_add_note",
"mcp__follow-up-boss__fub_log_call",
"mcp__follow-up-boss__fub_create_task",
"mcp__follow-up-boss__fub_update_task",
"mcp__follow-up-boss__fub_create_deal",
"mcp__follow-up-boss__fub_update_deal"
]
}
}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 follow-up-boss. Review it before you use it.
Capability tags behind 10 rules
- mcp__follow-up-boss__fub_get_identity private-data
- mcp__follow-up-boss__fub_search_people private-data
- mcp__follow-up-boss__fub_get_person private-data
- mcp__follow-up-boss__fub_check_duplicate_person outbound
- mcp__follow-up-boss__fub_list_events untrusted-input
- mcp__follow-up-boss__fub_list_text_messages private-data, untrusted-input
- mcp__follow-up-boss__fub_list_appointments private-data
- mcp__follow-up-boss__fub_list_stages private-data
- mcp__follow-up-boss__fub_list_custom_fields private-data
- mcp__follow-up-boss__fub_send_lead_event 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/io.usefulapi/follow-up-boss/verify?hash=f3abe3fc27f974f1491f8dfb601d187da8e68f5a9e9aa9086f82c5c19999af12" | jq -e '.changed == false'Pinned hash f3abe3fc27f9, from Oct 25, 2026, 23:19 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.usefulapi/follow-up-boss/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.usefulapi/follow-up-boss)Source: MCP Registry · repository. Synced Nov 20, 2026, 20:18 UTC.
Follow Up Boss MCP by usefulapi: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Follow Up Boss MCP by usefulapi safe?
- No scan can promise that. What its definitions show: 25 tools, 9 of which can change, send or delete something, and 2 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 Follow Up Boss MCP by usefulapi delete data?
- Yes. 8 tools can delete, cancel or revoke something: fub_send_lead_event, fub_update_person, fub_add_note, fub_log_call, fub_create_task, fub_update_task and 2 more.
Can the Follow Up Boss MCP by usefulapi do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Follow Up Boss MCP by usefulapi have?
- 25 tools: 8 destructive, 1 write, 16 read. 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 and 17 more.
Does the Follow Up Boss MCP by usefulapi need sign-in or OAuth?
- Its remote endpoint did not answer the last anonymous look.
Does the Follow Up Boss MCP by usefulapi send data to outside services?
- 2 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): fub_check_duplicate_person and fub_send_lead_event.
Has the Follow Up Boss MCP by usefulapi changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Oct 23, 2026. Every change is on this page and in its Atom feed.