io.usefulapi/follow-up-boss
REMOTE · FOLLOW-UP-BOSS.USEFULAPI.IO · SCANNED OCT 4
Search Follow Up Boss leads, review calls and deals, and add notes, tasks and deal updates.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security89
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability68
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 3566 tokens (~162/item across 22 items; 22 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
- Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage92
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 75% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 22 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the io.usefulapi/follow-up-boss MCP server?
io.usefulapi/follow-up-boss is a hosted endpoint at https://follow-up-boss.usefulapi.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · follow-up-boss.usefulapi.io
claude mcp add --transport http io-usefulapi-follow-up-boss 'https://follow-up-boss.usefulapi.io/mcp'
{
"mcpServers": {
"io-usefulapi-follow-up-boss": {
"url": "https://follow-up-boss.usefulapi.io/mcp"
}
}
} {
"servers": {
"io-usefulapi-follow-up-boss": {
"type": "http",
"url": "https://follow-up-boss.usefulapi.io/mcp"
}
}
} [mcp_servers.io-usefulapi-follow-up-boss] url = "https://follow-up-boss.usefulapi.io/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-usefulapi-follow-up-boss": {
"type": "remote",
"url": "https://follow-up-boss.usefulapi.io/mcp",
"enabled": true
}
}
} openclaw mcp add io-usefulapi-follow-up-boss --url 'https://follow-up-boss.usefulapi.io/mcp' --transport streamable-http
mcp_servers:
io-usefulapi-follow-up-boss:
url: "https://follow-up-boss.usefulapi.io/mcp" {
"McpServers": {
"io-usefulapi-follow-up-boss": {
"Transport": "http",
"Url": "https://follow-up-boss.usefulapi.io/mcp"
}
}
} assistant mcp add io-usefulapi-follow-up-boss -t streamable-http -u 'https://follow-up-boss.usefulapi.io/mcp'
{
"mcpServers": {
"io-usefulapi-follow-up-boss": {
"type": "http",
"url": "https://follow-up-boss.usefulapi.io/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 2 Oct 26 +1
- Server version: 1.3.0 → 1.5.1 functional
- 1 Oct 26 +5
- HTTPS: unverified → pass ▲ security
- Stability: unverified → 0.03 ▲ functional
- Server version: 1.0.0 → 1.3.0 functional
- 30 Sept 26 +51
- Authorization: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- First check of Judged manipulation: pass security
- First check of Authorization: partial security
- MCP protocol: unverified → fail ▼ functional
- Tool coverage: unverified → 100 ▲ functional
- First check of Schema quality: fail functional
- First check of Schema quality: excellent functional
- First check of Tool coverage: 75 functional
- First check of Schema quality: fail functional
- First check of Destructive annotations: 100 functional
- 29 Sept 26 18
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Oct 2026 · Probed https://follow-up-boss.usefulapi.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=usefulapi.io | CN=WE1,O=Google Trust Services,C=US | 13 Sept 2026 | 12 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | d9be3287b0fde9630e825ba1f79bff3f |
| SANs: usefulapi.io, *.usefulapi.io | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of follow-up-boss.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| usefulapi.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://follow-up-boss.usefulapi.io/.well-known/oauth-protected-resource/mcp"
Bearer realm="OAuth", resource_metadata="https://follow-up-boss.usefulapi.io/.well-known/oauth-protected-resource/mcp"Protected resource metadata
| Document | https://follow-up-boss.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://follow-up-boss.usefulapi.io/mcp |
| Authorisation server | https://follow-up-boss.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://follow-up-boss.usefulapi.io/mcp | Verified | 200 | |
| http (plaintext) | http://follow-up-boss.usefulapi.io/mcp | HTTPS enforced | 301 | https://follow-up-boss.usefulapi.io/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
fub_add_note Add a note ~72
Add a note to a contact's timeline. FUB: POST /v1/notes.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | Note content. |
| isHtml | boolean | – | Render HTML tags in the body. |
| personId | integer | yes | The person id. |
| subject | string | – | Note title. |
No output schema declared.
No examples provided.
fub_check_duplicate_person Check whether a person exists ~83
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.
| Name | Type | Req | Description |
|---|---|---|---|
| string | – | Email address to look for. | |
| phone | string | – | Phone number to look for. |
No output schema declared.
No examples provided.
fub_create_deal Create a deal ~206
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.
| Name | Type | Req | Description |
|---|---|---|---|
| agentCommission | integer | – | Agent commission split. |
| commissionValue | integer | – | – |
| description | string | – | – |
| dueDiligenceDate | string | – | – |
| earnestMoneyDueDate | string | – | – |
| finalWalkThroughDate | string | – | – |
| mutualAcceptanceDate | string | – | – |
| name | string | yes | Deal name. |
| peopleIds | array | – | Contact ids on the deal. |
| possessionDate | string | – | – |
| price | integer | – | – |
| projectedCloseDate | string | – | Projected close date. |
| stageId | integer | yes | Pipeline stage id. |
| teamCommission | integer | – | Team commission split. |
| userIds | array | – | User (agent) ids on the deal. |
No output schema declared.
No examples provided.
fub_create_task Create a task ~177
Create a task on a contact, assigned to a user (assignedUserId or assignedTo is required). FUB: POST /v1/tasks.
| Name | Type | Req | Description |
|---|---|---|---|
| assignedTo | string | – | Full name of the user to assign (or give assignedUserId). |
| assignedUserId | integer | – | User id to assign (or give assignedTo). |
| dueDate | string | – | YYYY-MM-DD. |
| dueDateTime | string | – | With time, e.g. 2026-11-16T15:00:00-05:00. |
| isCompleted | boolean | – | – |
| name | string | – | Task name. |
| personId | integer | yes | The person id. |
| remindSecondsBefore | integer | – | Reminder lead time; only for tasks with a due time. |
| type | string | – | – |
No output schema declared.
No examples provided.
fub_get_identity Get identity ~50
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
fub_get_person Get one person ~75
Fetch one contact by id. Pass fields="allFields" to include custom fields and everything else. FUB: GET /v1/people/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| fields | string | – | Comma-separated fields to return, or "allFields" / "allCustom". |
| id | integer | yes | The person id. |
No output schema declared.
No examples provided.
fub_list_appointments List appointments ~156
Calendar appointments with invitees, type and outcome. Filter by person, user, or a start+end window (both required together). FUB: GET /v1/appointments.
| Name | Type | Req | Description |
|---|---|---|---|
| end | string | – | Window end (ISO-8601). Must be combined with start. |
| limit | integer | – | Page size, 1-100 (FUB default 10). |
| offset | integer | – | Rows to skip. For deep paging prefer `next`. |
| personId | string | – | Person id, or a comma-separated list of ids. |
| start | string | – | Window start (ISO-8601). Must be combined with end. |
| userId | integer | – | Only appointments for this user. |
No output schema declared.
No examples provided.
fub_list_calls List calls ~124
Logged phone calls with outcome, direction and duration. Filter by person or number. FUB: GET /v1/calls.
| Name | Type | Req | Description |
|---|---|---|---|
| fromNumber | string | – | Calls from this number. |
| limit | integer | – | Page size, 1-100 (FUB default 10). |
| offset | integer | – | Rows to skip. For deep paging prefer `next`. |
| personId | integer | – | Only calls with this person. |
| phone | string | – | Calls to or from this person's number. |
| toNumber | string | – | Calls to this number. |
No output schema declared.
No examples provided.
fub_list_custom_fields List custom fields ~102
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.
| Name | Type | Req | Description |
|---|---|---|---|
| label | string | – | Find a custom field by label. |
| limit | integer | – | Page size, 1-100 (FUB default 10). |
| offset | integer | – | Rows to skip. For deep paging prefer `next`. |
No output schema declared.
No examples provided.
fub_list_deals List deals ~165
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.
| Name | Type | Req | Description |
|---|---|---|---|
| includeArchived | boolean | – | Include Archived deals. |
| includeDeleted | boolean | – | Include Deleted deals. |
| limit | integer | – | Page size, 1-100 (FUB default 10). |
| offset | integer | – | Rows to skip. For deep paging prefer `next`. |
| personId | integer | – | Only deals for this person. |
| pipelineId | integer | – | Only deals in this pipeline. |
| status | string | – | Only deals with this status. |
| userId | integer | – | Only deals for this user. |
No output schema declared.
No examples provided.
fub_list_events List lead events ~224
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.
| Name | Type | Req | Description |
|---|---|---|---|
| hasProperty | boolean | – | Only events with (or without) a property attached. |
| limit | integer | – | Page size, 1-100 (FUB default 10). |
| next | string | – | Cursor from the previous page's _metadata.next. Recommended over offset. |
| offset | integer | – | Rows to skip. For deep paging prefer `next`. |
| personId | integer | – | Only events for this person. |
| propertyAddress | string | – | Partial match on the property address. |
| type | string | – | Comma-separated event types, e.g. "Registration,Property Inquiry". One of: Registration, Inquiry, Seller Inquiry, Property Inquiry, General Inquiry, Viewed Property, Saved Property, Visited Website,… |
No output schema declared.
No examples provided.
fub_list_pipelines List deal pipelines ~54
Deal pipelines with their stages (the stage ids that fub_create_deal / fub_update_deal take). FUB: GET /v1/pipelines.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | – | Exact pipeline name. |
No output schema declared.
No examples provided.
fub_list_stages List contact stages ~102
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Page size, 1-100 (FUB default 10). |
| offset | integer | – | Rows to skip. For deep paging prefer `next`. |
| sort | string | – | Sort order. |
No output schema declared.
No examples provided.
fub_list_tasks List tasks ~234
Tasks (follow-ups, calls, showings…). Filter by person, assignee, type, completion, or due window (due="today"|"overdue"|"upcoming"). FUB: GET /v1/tasks.
| Name | Type | Req | Description |
|---|---|---|---|
| assignedTo | string | – | Only tasks assigned to this user (full name). |
| assignedUserId | integer | – | Only tasks assigned to this user id. |
| due | string | – | Due window. |
| dueEnd | string | – | Due at or before this time. |
| dueStart | string | – | Due at or after this time. |
| isCompleted | boolean | – | Completed or not. |
| limit | integer | – | Page size, 1-100 (FUB default 10). |
| name | string | – | Partial match on task name. |
| offset | integer | – | Rows to skip. For deep paging prefer `next`. |
| personId | integer | – | Only tasks for this person. |
| type | string | – | Comma-separated types. One of: Follow Up, Call, Text, Email, Appointment, Showing, Closing, Open House, Thank You. |
No output schema declared.
No examples provided.
fub_list_text_messages List text messages ~120
Text messages for a person or a phone number (message bodies may be hidden by FUB for privacy). FUB: GET /v1/textMessages.
| Name | Type | Req | Description |
|---|---|---|---|
| fromNumber | string | – | Texts sent from this number. |
| limit | integer | – | Page size, 1-100 (FUB default 10). |
| offset | integer | – | Rows to skip. For deep paging prefer `next`. |
| personId | integer | – | Only texts with this person. |
| toNumber | string | – | Texts sent to this number. |
No output schema declared.
No examples provided.
fub_list_users List users (agents) ~126
Users in the account (agents, brokers, lenders) — the ids to assign people, tasks and deals to. FUB: GET /v1/users.
| Name | Type | Req | Description |
|---|---|---|---|
| string | – | Email address. | |
| limit | integer | – | Page size, 1-100 (FUB default 10). |
| name | string | – | Exact full name. |
| offset | integer | – | Rows to skip. For deep paging prefer `next`. |
| role | string | – | e.g. "Broker", "Agent", "Lender". |
| sort | string | – | Sort order. |
No output schema declared.
No examples provided.
fub_log_call Log a call ~145
Record a phone call made or received outside FUB, with its outcome. Does not place a call. FUB: POST /v1/calls.
| Name | Type | Req | Description |
|---|---|---|---|
| duration | integer | – | Seconds. |
| fromNumber | string | – | – |
| isIncoming | boolean | yes | true for an incoming call, false for outgoing. |
| note | string | – | Call notes. |
| outcome | string | – | – |
| personId | integer | yes | The person id. |
| phone | string | yes | The number called or calling. |
| recordingUrl | string | – | – |
| toNumber | string | – | – |
| userId | integer | – | User who took the call (admins only). |
No output schema declared.
No examples provided.
fub_search_people Search people (contacts/leads) ~508
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.
| Name | Type | Req | Description |
|---|---|---|---|
| assignedPondId | integer | – | Assigned pond id. |
| assignedTo | string | – | Full name of the assigned agent. |
| assignedUserId | integer | – | Assigned agent's user id. |
| contacted | boolean | – | Whether they have been contacted. |
| createdAfter | string | – | ISO-8601 UTC, e.g. 2026-07-01T00:00:00Z. |
| string | – | Exact email address. | |
| fields | string | – | Comma-separated fields to return, or "allFields" / "allCustom". |
| firstName | string | – | Partial match on first name. |
| includeTrash | boolean | – | Include people in the Trash stage. |
| lastActivityAfter | string | – | e.g. "2026-01-31 00:00:00". |
| lastActivityBefore | string | – | e.g. "2026-01-31 00:00:00". |
| lastName | string | – | Partial match on last name. |
| limit | integer | – | Page size, 1-100 (FUB default 10). |
| name | string | – | Partial match on full name. |
| next | string | – | Cursor from the previous page's _metadata.next. Recommended over offset. |
| offset | integer | – | Rows to skip. For deep paging prefer `next`. |
| phone | string | – | Phone number. |
| priceAbove | integer | – | Price above this value. |
| priceBelow | integer | – | Price below this value. |
| smartListId | integer | – | Only people matching this Smart List. |
| sort | string | – | Sort field, e.g. "created", "lastActivity", "name"; prefix "-" for descending. |
| source | string | – | Lead source, e.g. "Zillow". |
| stage | string | – | Stage name, e.g. "Lead", "Past Client" (see fub_list_stages). |
| tags | string | – | Comma-separated tags; matches ANY ("Foo,Bar"). |
| updatedAfter | string | – | ISO-8601 UTC. |
No output schema declared.
No examples provided.
fub_send_lead_event Send in a lead / lead event ~253
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.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | Any additional information. |
| message | string | – | A message from the lead. |
| occurredAt | string | – | ISO-8601 time it happened. Events older than a day are historical and do not trigger workflows. |
| pageTitle | string | – | For Viewed Page events. |
| pageUrl | string | – | For Viewed Page events. |
| person | object | yes | The lead. |
| property | object | – | The property the event is about. |
| source | string | – | Lead source name, e.g. "MyWebsite.com". Used for Lead Flow routing. |
| system | string | – | Name of the system sending the lead. |
| type | string | yes | Event type. "Inquiry" becomes Property or General Inquiry automatically. |
No output schema declared.
No examples provided.
fub_update_deal Update a deal ~180
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| commissionValue | integer | – | – |
| description | string | – | – |
| dueDiligenceDate | string | – | – |
| earnestMoneyDueDate | string | – | – |
| finalWalkThroughDate | string | – | – |
| id | integer | yes | The deal id. |
| mutualAcceptanceDate | string | – | – |
| name | string | – | – |
| peopleIds | array | – | – |
| possessionDate | string | – | – |
| price | integer | – | – |
| projectedCloseDate | string | – | Projected close date. |
| stageId | integer | – | Move to this pipeline stage. |
| userIds | array | – | – |
No output schema declared.
No examples provided.
fub_update_person Update a person ~306
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| addresses | array | – | – |
| assignedLenderId | integer | – | – |
| assignedLenderName | string | – | – |
| assignedPondId | integer | – | – |
| assignedTo | string | – | Full name of the agent. |
| assignedUserId | integer | – | – |
| background | string | – | Background notes (multi-line). |
| contacted | boolean | – | – |
| customFields | object | – | Account custom fields, keyed by their API name (e.g. {"customBirthday": "1990-02-16"}). See the `name` column of fub_list_custom_fields. null clears a value. |
| emails | array | – | – |
| firstName | string | – | – |
| id | integer | yes | The person id. |
| lastName | string | – | – |
| mergeTags | boolean | – | Merge `tags` into the existing tags instead of replacing them. |
| phones | array | – | – |
| price | integer | – | – |
| stage | string | – | Stage name (see fub_list_stages). |
| tags | array | – | – |
| timeframeId | integer | – | – |
No output schema declared.
No examples provided.
fub_update_task Update a task ~104
Update a task — mark it complete, rename, retype or reassign it. FUB: PUT /v1/tasks/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| assignedTo | string | – | – |
| assignedUserId | integer | – | – |
| id | integer | yes | The task id. |
| isCompleted | boolean | – | Mark complete (true) or reopen (false). |
| name | string | – | – |
| personId | integer | – | – |
| type | string | – | – |
No output schema declared.
No examples provided.
What is the io.usefulapi/follow-up-boss MCP server?
io.usefulapi/follow-up-boss is an MCP server listed in the public MCP registry as io.usefulapi/follow-up-boss. Search Follow Up Boss leads, review calls and deals, and add notes, tasks and deal updates. This page covers its hosted endpoint (https://follow-up-boss.usefulapi.io/mcp).
Is the io.usefulapi/follow-up-boss MCP server safe to use?
io.usefulapi/follow-up-boss scores 75 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.usefulapi/follow-up-boss MCP server expose?
io.usefulapi/follow-up-boss exposes 22 tools: fub_get_identity, fub_search_people, fub_get_person, fub_check_duplicate_person, fub_list_events, and 17 more. Their descriptions and schemas cost roughly 3,566 tokens of context every time the server is loaded.
Does the io.usefulapi/follow-up-boss MCP server require authentication?
Yes. io.usefulapi/follow-up-boss asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the io.usefulapi/follow-up-boss MCP server still maintained?
io.usefulapi/follow-up-boss is still listed as active in the MCP registry. We last reached this channel on 4 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.