follow-up-boss

Tools

22 tools: 14 read-only, 0 change data, 8 high risk (delete, pay, send or run code).

1 tool can send messages; they are listed first.

read-only

Only reads or looks things up. Safe for an agent to call on its own.

changes data

Creates, edits or sends something. Worth a person's approval the first time.

high risk

Can delete, pay, send on your behalf or run code. Hard or impossible to undo.

Connecting costs an agent about 7,066 tokens of tool definitions and a 827 ms handshake.

• high riskfub_send_lead_eventsends messagesAdd 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...
• high riskfub_update_personUpdate 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}.
• high riskfub_add_noteAdd a note to a contact's timeline. FUB: POST /v1/notes.
• high riskfub_log_callRecord a phone call made or received outside FUB, with its outcome. Does not place a call. FUB: POST /v1/calls.
• high riskfub_create_taskCreate a task on a contact, assigned to a user (assignedUserId or assignedTo is required). FUB: POST /v1/tasks.
• high riskfub_update_taskUpdate a task - mark it complete, rename, retype or reassign it. FUB: PUT /v1/tasks/{id}.
• high riskfub_create_dealCreate 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.
• high riskfub_update_dealUpdate a deal - move it to another stage, change price, dates, people or agents. peopleIds/userIds replace the full list. FUB: PUT /v1/deals/{id}.
• read-onlyfub_get_identityWho 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.
• read-onlyfub_search_peopleSearch 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/peo...
• read-onlyfub_get_personFetch one contact by id. Pass fields="allFields" to include custom fields and everything else. FUB: GET /v1/people/{id}.
• read-onlyfub_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. Use before adding a lead. FUB: GET /v1/people/checkDuplicate.
• read-onlyfub_list_eventsLead 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.
• read-onlyfub_list_callsLogged phone calls with outcome, direction and duration. Filter by person or number. FUB: GET /v1/calls.
• read-onlyfub_list_text_messagesText messages for a person or a phone number (message bodies may be hidden by FUB for privacy). FUB: GET /v1/textMessages.
• read-onlyfub_list_tasksTasks (follow-ups, calls, showings…). Filter by person, assignee, type, completion, or due window (due="today"|"overdue"|"upcoming"). FUB: GET /v1/tasks.
• read-onlyfub_list_appointmentsCalendar appointments with invitees, type and outcome. Filter by person, user, or a start+end window (both required together). FUB: GET /v1/appointments.
• read-onlyfub_list_dealsDeals (transactions) with stage, price, people, agents and commission. Filter by pipeline, user, person or status. The response metadata includes totalByStageId. FUB: GET /v1/deals.
• read-onlyfub_list_pipelinesDeal pipelines with their stages (the stage ids that fub_create_deal / fub_update_deal take). FUB: GET /v1/pipelines.
• read-onlyfub_list_stagesContact 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.
• read-onlyfub_list_usersUsers in the account (agents, brokers, lenders) - the ids to assign people, tasks and deals to. FUB: GET /v1/users.
• read-onlyfub_list_custom_fieldsThe 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.

Levels are automated estimates from each tool's public name, description and annotations, and can be wrong. Descriptions as the server publishes them.

Status

Newest check: answered with tools, from the daily check, 2026-10-04, 827 ms.

From one check a day over the last 1 day. Servers whose owner verified them are checked every 5 minutes. Sign-in and payment answers count as up.

Last 30 days

2026-09-052026-10-04

answered with toolssign-in or payment askednot answeringnot checked

Compare: the most reliable servers in CRM and sales, ranked by days answering.

Badge

Live: status, days reachable, the tokens its tool list costs an agent. For a README:

[![7Maps](https://7it.co.il/7maps/badge/follow-up-boss.usefulapi.io/mcp.svg)](https://7it.co.il/7maps/s/follow-up-boss.usefulapi.io/mcp)

Other styles: add ?style=uptime (30-day uptime), ?style=stars (agents’ rating) or ?style=verified (owner mark) to the image address, or ?style=top (shows "top 10%" when the server ranks in the top tenth of its category by days answering; otherwise the standard badge).

Is this badge genuine? Anyone can check what a genuine badge for this server says right now: /7maps/verify/badge?server=follow-up-boss.usefulapi.io%2Fmcp (add the same &style= for another style).

Own this server? Verify that it is yours.

Status widget

A live status card for a status page, docs or a dashboard: current status, the 30-day strip, uptime and handshake time.

Script (renders where it is placed, in its own shadow DOM):

<script src="https://7it.co.il/7maps/widget/follow-up-boss.usefulapi.io/mcp.js" async></script>

Or an iframe:

<iframe src="https://7it.co.il/7maps/widget/follow-up-boss.usefulapi.io/mcp" title="7Maps status" width="360" height="176" style="border:0;max-width:100%" loading="lazy"></iframe>

The widget is drawn only from 7it.co.il. Is a status shown elsewhere genuine? Check it: /7maps/verify/badge?server=follow-up-boss.usefulapi.io%2Fmcp.

Add ?theme=light or ?theme=dark to either address (default: follows the visitor's setting). Refreshed every 5 minutes. Open the card · script.

For AI agents

Before connecting, an agent can ask 7Maps for this server's full condition, every tool's risk level and what changed since a person approved it: the road_conditions, watch and route tools on https://7it.co.il/7maps/mcp, paid per call in USDC via x402. About 7Maps.