AgencyBloc MCP by usefulapi
REMOTE · AGENCYBLOC.USEFULAPI.IO
Read and update AgencyBloc individuals, groups, policies and agents; log activities and notes.
Available components
Last scanned (5 hours ago)
Scores higher than 46% of remote servers
Reachable. Last reached 25 Oct 2026.
Category CRM and Sales
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 Security78
- 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 enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven. View diagnostics → Unverified
- 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 & Reachability0
- Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability73
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 3587 tokens (~163/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 Management3
- Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage84
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 53% 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
- We read all 22 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 23 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
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.
- 25 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- Server version: 1.1.0 → 1.1.3 functional
- 24 Oct 26 59
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 25 Oct 2026 · Probed https://agencybloc.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 agencybloc.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 38690, 57355 | 8, 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 | 302 |
WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://agencybloc.usefulapi.io/.well-known/oauth-protected-resource/mcp"
Bearer realm="OAuth", resource_metadata="https://agencybloc.usefulapi.io/.well-known/oauth-protected-resource/mcp"Protected resource metadata
| Document | https://agencybloc.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://agencybloc.usefulapi.io/mcp |
| Authorisation server | https://agencybloc.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://agencybloc.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/agencybloc/ |
| http (plaintext) | http://agencybloc.usefulapi.io/mcp | Inconclusive | 302 | http://agencybloc.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 →
agencybloc_create_activity Create activity ~340
WRITE: log an activity (call, task, renewal reminder) on a group, individual, agent, carrier or lead. Status, type, method and priority are the text values of the account's dropdowns (My Agency Settings > Data Administration); unknown values are created. When the status is not Complete the activity is a follow-up: give follow_up_user_id and follow_up_date (and start/end times), and AgencyBloc assigns it to that user. Nothing is sent to the customer. Activities cannot be edited or deleted through the API. Returns the new activityID. POST activities/create.
| Name | Type | Req | Description |
|---|---|---|---|
| activity_date | string | – | Defaults to today. |
| entity_id | integer | yes | Id of the record. |
| entity_type | string | yes | – |
| follow_up_all_day | boolean | – | – |
| follow_up_date | string | – | A date, yyyy-mm-dd. |
| follow_up_end_time | string | – | 24-hour HH:MM or HH:MM:SS. |
| follow_up_start_time | string | – | 24-hour HH:MM or HH:MM:SS. |
| follow_up_user_id | integer | – | AgencyBloc user the follow-up is assigned to. |
| method | string | yes | Activity method, e.g. Phone or Email. |
| notes | string | yes | The activity text. |
| priority | string | yes | e.g. Low, Medium or High. |
| related_policy_id | integer | – | A policy of this group or individual. |
| status | string | yes | e.g. Complete or In Progress. |
| subject | string | yes | – |
| type | string | yes | Activity type, e.g. Renewal. |
No output schema declared.
No examples provided.
agencybloc_create_group Create group ~261
WRITE: create a new group (employer / business account) in AgencyBloc. It does not check for duplicates: search first. Returns the new groupID. POST groups/create.
| Name | Type | Req | Description |
|---|---|---|---|
| account_manager | string | – | A user id or the exact user name in AgencyBloc. |
| address_type | string | – | Address label (e.g. Home, Business, Mailing); used with the address fields below. |
| business_phone | string | – | – |
| city | string | – | – |
| custom_fields | object | – | Custom field values keyed by the exact custom field NAME configured in AgencyBloc (sent as custom_<name>). Separate several values of a checkbox-list field with ||. |
| dba | string | – | Doing-business-as name. |
| description | string | – | – |
| employees | integer | – | Number of employees. |
| group_name | string | yes | – |
| industry | string | – | – |
| servicing_agent_id | integer | – | – |
| state | string | – | Two-letter state abbreviation. |
| status | string | – | – |
| street1 | string | – | – |
| street2 | string | – | – |
| type | string | – | Group type as configured in the account. |
| website | string | – | – |
| zip | string | – | – |
No output schema declared.
No examples provided.
agencybloc_create_individual Create individual ~328
WRITE: create a new individual (client or contact) in AgencyBloc. Needs first and last name; everything else is optional. It does not check for duplicates: search first. Returns the new individualID. POST individuals/create.
| Name | Type | Req | Description |
|---|---|---|---|
| address_type | string | – | Address label (e.g. Home, Business, Mailing); used with the address fields below. |
| birth_date | string | – | A date, yyyy-mm-dd. |
| business_phone | string | – | – |
| cell_phone | string | – | – |
| city | string | – | – |
| custom_fields | object | – | Custom field values keyed by the exact custom field NAME configured in AgencyBloc (sent as custom_<name>). Separate several values of a checkbox-list field with ||. |
| string | – | – | |
| first_name | string | yes | – |
| gender | string | – | – |
| group_id | integer | – | Group the individual belongs to. |
| home_phone | string | – | – |
| last_name | string | yes | – |
| lead_source | string | – | – |
| middle_initial | string | – | – |
| servicing_agent_id | integer | – | – |
| state | string | – | Two-letter state abbreviation. |
| status | string | – | Status as configured in the account; an unknown value is created. |
| street1 | string | – | – |
| street2 | string | – | – |
| tags | string | – | Tags (replaces existing tags on update; an empty string clears them). |
| type | string | – | Type as configured in the account; an unknown value is created. |
| zip | string | – | – |
No output schema declared.
No examples provided.
agencybloc_create_note Add note ~128
WRITE: add one note (subject + body) to an agent, group, individual or policy. AgencyBloc never allows notes to be edited or deleted through the API (audit rule), so the note is permanent. Pinning a note unpins the previously pinned one. Returns the new note id. POST notes/create.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | – |
| entity_id | integer | yes | Id of the record. |
| entity_type | string | yes | – |
| pinned | boolean | – | Pin the note (unpins any other pinned note). Default false. |
| subject | string | yes | – |
No output schema declared.
No examples provided.
agencybloc_create_policy Create policy ~283
WRITE: create a policy on an existing group or individual. Needs the holder (entity_id + entity_type), coverage type, status and the carrier's full name; unknown coverage types / statuses are created in the account. Returns the new policyID. POST policies/create.
| Name | Type | Req | Description |
|---|---|---|---|
| app_submit_date | string | – | A date, yyyy-mm-dd. |
| carrier | string | yes | The carrier's full name. |
| coverage_type | string | yes | – |
| custom_fields | object | – | Custom field values keyed by the exact custom field NAME configured in AgencyBloc (sent as custom_<name>). Separate several values of a checkbox-list field with ||. |
| effective_date | string | – | A date, yyyy-mm-dd. |
| entity_id | integer | yes | The groupID or individualID that holds the policy. |
| entity_type | string | yes | – |
| lives | integer | – | Number of covered lives. |
| notes | string | – | The policy's own notes field. |
| pay_frequency | string | – | Payment frequency as configured in the account (e.g. Monthly). |
| policy_number | string | – | – |
| premium | number | – | Premium amount. |
| renewal_date | string | – | A date, yyyy-mm-dd. |
| servicing_agent_id | integer | – | – |
| status | string | yes | – |
| term_date | string | – | A date, yyyy-mm-dd. |
No output schema declared.
No examples provided.
agencybloc_get_activities Get activities by id ~44
Activities by id (1-50 ids), e.g. the ids shown on a policy or individual. POST activity/list.
| Name | Type | Req | Description |
|---|---|---|---|
| activity_ids | array | yes | – |
No output schema declared.
No examples provided.
agencybloc_get_agent Get agent ~60
One agent by id, with agencies, addresses and custom fields (and activities when include_activities is true). POST agents/detail.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | integer | yes | – |
| include_activities | boolean | – | Also return the activities (default false). |
No output schema declared.
No examples provided.
agencybloc_get_group Get group ~60
One group by id, with addresses, policies and custom fields (and activities when include_activities is true). POST groups/detail.
| Name | Type | Req | Description |
|---|---|---|---|
| group_id | integer | yes | – |
| include_activities | boolean | – | Also return the activities (default false). |
No output schema declared.
No examples provided.
agencybloc_get_individual Get individual ~66
One individual by id, with addresses, policies and custom fields (and activities when include_activities is true). National ids are removed. POST individuals/detail.
| Name | Type | Req | Description |
|---|---|---|---|
| include_activities | boolean | – | Also return the activities (default false). |
| individual_id | integer | yes | – |
No output schema declared.
No examples provided.
agencybloc_get_lead Get sales record (lead) ~40
One Sales Enablement record (lead) by record id. POST salesEnablement/Leads/detail.
| Name | Type | Req | Description |
|---|---|---|---|
| record_id | integer | yes | – |
No output schema declared.
No examples provided.
agencybloc_get_policy Get policy ~45
One policy by id: holder, agent, carrier, status, dates, premium, coverages and custom fields. POST policies/detail.
| Name | Type | Req | Description |
|---|---|---|---|
| policy_id | integer | yes | – |
No output schema declared.
No examples provided.
agencybloc_list_activities List activities of a record ~80
All activities (tasks, calls, renewals) logged on one group, individual, agent, carrier or lead: date, subject, notes, status, type, method, priority and follow-up. There is no paging. POST activities/list.
| Name | Type | Req | Description |
|---|---|---|---|
| entity_id | integer | yes | Id of the record. |
| entity_type | string | yes | – |
No output schema declared.
No examples provided.
agencybloc_list_notes List notes of a record ~69
Notes (subject, body, author, dates, pinned flag, attachment names) on one agent, group, individual or policy, newest change first. There is no paging. POST notes/list.
| Name | Type | Req | Description |
|---|---|---|---|
| entity_id | integer | yes | Id of the record. |
| entity_type | string | yes | – |
No output schema declared.
No examples provided.
agencybloc_search_agents Search agents ~107
Search agents (producers) by name, email or phone. Returns id, name, email and phones. POST agents/search.
| Name | Type | Req | Description |
|---|---|---|---|
| string | – | – | |
| first_name | string | – | – |
| last_name | string | – | – |
| limit | integer | – | Most records to return, 1-500 (default 50). There is no paging: narrow with filters if more may exist. |
| phone | string | – | Matches the home, cell or business phone. |
No output schema declared.
No examples provided.
agencybloc_search_carriers Search carriers ~84
Search insurance carriers by name or phone. Returns id, name, abbreviation and phones. POST carriers/search.
| Name | Type | Req | Description |
|---|---|---|---|
| carrier_name | string | – | – |
| limit | integer | – | Most records to return, 1-500 (default 50). There is no paging: narrow with filters if more may exist. |
| phone | string | – | Matches any carrier phone. |
No output schema declared.
No examples provided.
agencybloc_search_groups Search groups ~122
Search groups (employer / business accounts) in AgencyBloc by name, type or phone. Returns id, name, type and phone. POST groups/search.
| Name | Type | Req | Description |
|---|---|---|---|
| business_phone | string | – | – |
| group_name | string | – | – |
| limit | integer | – | Most records to return, 1-500 (default 50). There is no paging: narrow with filters if more may exist. |
| type | string | – | The group type as configured in the account. |
| updated_since | string | – | Only groups modified on/after this date. |
No output schema declared.
No examples provided.
agencybloc_search_individuals Search individuals ~201
Search individuals (clients and contacts) in AgencyBloc. All filters are optional and combine; with none you get the first records. Returns id, name, email, birth date, phones and last-updated time (national ids such as SSN are never returned). Use updated_since to find recently changed people. POST individuals/search.
| Name | Type | Req | Description |
|---|---|---|---|
| string | – | – | |
| first_name | string | – | – |
| group_id | integer | – | Only members of this group. |
| last_name | string | – | – |
| limit | integer | – | Most records to return, 1-500 (default 50). There is no paging: narrow with filters if more may exist. |
| phone | string | – | Matches the home, cell or business phone. |
| updated_before | string | – | Only records updated before this (exclusive). |
| updated_since | string | – | Only records updated on/after this (inclusive); results then run oldest update first. |
No output schema declared.
No examples provided.
agencybloc_search_leads_by_phone Search sales records (leads) by phone ~65
Find Sales Enablement records (leads) by phone number; the search is by phone only. Only accounts with the Sales Enablement module have them. POST salesEnablement/leads/searchphone.
| Name | Type | Req | Description |
|---|---|---|---|
| phone | string | yes | Phone number to look up. |
No output schema declared.
No examples provided.
agencybloc_search_policies Search policies ~259
Search policies by number, coverage type, carrier, holder, servicing agent, application date or last update. Returns id, holder, policy number, carrier, status, coverage type, effective and renewal dates. Use submitted_after/updated_since for recent business. POST policies/search.
| Name | Type | Req | Description |
|---|---|---|---|
| carrier | string | – | Carrier name. |
| coverage_type | string | – | Coverage type as configured in the account (e.g. Medicare Supplement). |
| entity_id | integer | – | Holder id (group or individual id); give entity_type too. |
| entity_type | string | – | Whether entity_id is a Group or an Individual. |
| limit | integer | – | Most records to return, 1-500 (default 50). There is no paging: narrow with filters if more may exist. |
| policy_number | string | – | – |
| servicing_agent_id | integer | – | – |
| submitted_after | string | – | Application submitted on/after this date. |
| submitted_before | string | – | Application submitted on/before this date (AgencyBloc includes the date itself). |
| updated_before | string | – | Only records updated before this (exclusive). |
| updated_since | string | – | Only records updated on/after this (inclusive); results then run oldest update first. |
No output schema declared.
No examples provided.
agencybloc_update_group Update group ~188
WRITE: change fields of an existing group (including its name); fields you leave out are not sent. Returns the groupID. POST groups/update.
| Name | Type | Req | Description |
|---|---|---|---|
| account_manager | string | – | A user id or the exact user name in AgencyBloc. |
| business_phone | string | – | – |
| custom_fields | object | – | Custom field values keyed by the exact custom field NAME configured in AgencyBloc (sent as custom_<name>). Separate several values of a checkbox-list field with ||. |
| dba | string | – | Doing-business-as name. |
| description | string | – | – |
| employees | integer | – | Number of employees. |
| group_id | integer | yes | – |
| group_name | string | – | – |
| industry | string | – | – |
| servicing_agent_id | integer | – | – |
| type | string | – | Group type as configured in the account. |
| website | string | – | – |
No output schema declared.
No examples provided.
agencybloc_update_individual Update individual ~248
WRITE: change fields of an existing individual; fields you leave out are not sent. Tags are replaced (empty string clears them). Addresses are not changed here. Returns the individualID. POST individuals/update.
| Name | Type | Req | Description |
|---|---|---|---|
| birth_date | string | – | A date, yyyy-mm-dd. |
| business_phone | string | – | – |
| cell_phone | string | – | – |
| custom_fields | object | – | Custom field values keyed by the exact custom field NAME configured in AgencyBloc (sent as custom_<name>). Separate several values of a checkbox-list field with ||. |
| string | – | – | |
| gender | string | – | – |
| group_id | integer | – | Group the individual belongs to. |
| home_phone | string | – | – |
| individual_id | integer | yes | – |
| lead_source | string | – | – |
| middle_initial | string | – | – |
| servicing_agent_id | integer | – | – |
| status | string | – | Status as configured in the account; an unknown value is created. |
| tags | string | – | Tags (replaces existing tags on update; an empty string clears them). |
| type | string | – | Type as configured in the account; an unknown value is created. |
No output schema declared.
No examples provided.
agencybloc_update_policy Update policy ~241
WRITE: change fields of an existing policy (status, carrier, dates, premium ...); fields you leave out are not sent. Returns the policyID. POST policies/update.
| Name | Type | Req | Description |
|---|---|---|---|
| app_submit_date | string | – | A date, yyyy-mm-dd. |
| carrier | string | – | – |
| coverage_type | string | – | – |
| custom_fields | object | – | Custom field values keyed by the exact custom field NAME configured in AgencyBloc (sent as custom_<name>). Separate several values of a checkbox-list field with ||. |
| effective_date | string | – | A date, yyyy-mm-dd. |
| lives | integer | – | Number of covered lives. |
| notes | string | – | The policy's own notes field. |
| pay_frequency | string | – | Payment frequency as configured in the account (e.g. Monthly). |
| policy_id | integer | yes | – |
| policy_number | string | – | – |
| premium | number | – | Premium amount. |
| renewal_date | string | – | A date, yyyy-mm-dd. |
| servicing_agent_id | integer | – | – |
| status | string | – | – |
| term_date | string | – | A date, yyyy-mm-dd. |
No output schema declared.
No examples provided.
How do I install the AgencyBloc MCP by usefulapi server?
AgencyBloc MCP by usefulapi is a hosted endpoint at https://agencybloc.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 · agencybloc.usefulapi.io
claude mcp add --transport http io-usefulapi-agencybloc 'https://agencybloc.usefulapi.io/mcp'
What is the AgencyBloc MCP by usefulapi server?
AgencyBloc MCP by usefulapi is listed in the public MCP registry as io.usefulapi/agencybloc. Read and update AgencyBloc individuals, groups, policies and agents; log activities and notes. This page covers its hosted endpoint (https://agencybloc.usefulapi.io/mcp).
Is the AgencyBloc MCP by usefulapi server safe to use?
AgencyBloc MCP by usefulapi scores 60 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 AgencyBloc MCP by usefulapi server expose?
AgencyBloc MCP by usefulapi exposes 22 tools: agencybloc_search_individuals, agencybloc_get_individual, agencybloc_search_groups, agencybloc_get_group, agencybloc_search_policies, and 17 more. Their descriptions and schemas cost roughly 3,319 tokens of context every time the server is loaded.
Does the AgencyBloc MCP by usefulapi server require authentication?
Yes. AgencyBloc MCP by usefulapi 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 AgencyBloc MCP by usefulapi server still maintained?
AgencyBloc MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 25 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.