Pobuca Connect MCP by usefulapi
REMOTE · POBUCA-CONNECT.USEFULAPI.IO
Read and update Pobuca Connect contacts and organizations; look up teams and custom fields.
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 Usability74
- 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 3899 tokens (~229/item across 17 items; 17 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 Coverage85
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 56% 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 17 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 18 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 0
- Stability: unverified → 0.03 ▲ functional
- Server version: 1.1.0 → 1.1.3 functional
- 24 Oct 26 60
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://pobuca-connect.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 pobuca-connect.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://pobuca-connect.usefulapi.io/.well-known/oauth-protected-resource/mcp"
Bearer realm="OAuth", resource_metadata="https://pobuca-connect.usefulapi.io/.well-known/oauth-protected-resource/mcp"Protected resource metadata
| Document | https://pobuca-connect.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://pobuca-connect.usefulapi.io/mcp |
| Authorisation server | https://pobuca-connect.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://pobuca-connect.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/pobuca-connect/ |
| http (plaintext) | http://pobuca-connect.usefulapi.io/mcp | Inconclusive | 302 | http://pobuca-connect.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 →
pobuca_create_contact Create contact ~466
WRITE: create a new contact in the Pobuca Connect address book. Needs at least a first name, last name or email. Not idempotent: calling it twice creates two contacts, so search with pobuca_list_contacts first. POST /api/v1/Contacts.
| Name | Type | Req | Description |
|---|---|---|---|
| allowEmails | boolean | – | Consent flag: may this contact be emailed. |
| allowPhones | boolean | – | Consent flag: may this contact be phoned. |
| allowSms | boolean | – | Consent flag: may this contact be sent SMS. |
| birthday | string | – | Birthday as an ISO date, e.g. 1985-04-23. |
| comments | string | – | Free-text notes on the contact. |
| customFields | array | – | Custom field values (see pobuca_list_custom_fields). |
| departmentId | string | – | Id of the department (from pobuca_list_departments). |
| string | – | Work email. | |
| string | – | – | |
| firstName | string | – | – |
| gender | string | – | – |
| homeCity | string | – | – |
| homePhone | string | – | – |
| homePostalCode | string | – | – |
| homeState | string | – | – |
| homeStreet | string | – | – |
| jobTitle | string | – | – |
| lastName | string | – | – |
| string | – | – | |
| middleName | string | – | – |
| mobilePhone | string | – | – |
| nickname | string | – | – |
| organizationId | string | – | Id of the organization this contact belongs to (from pobuca_list_organizations). |
| otherEmail | string | – | – |
| personalEmail | string | – | – |
| suffix | string | – | – |
| tags | array | – | Tags (replaces the existing tags on update). |
| teamId | string | – | Id of the team that owns this contact (from pobuca_list_teams). |
| titleSalutation | string | – | Salutation, e.g. Mr, Ms, Dr. |
| string | – | – | |
| website | string | – | – |
| workCity | string | – | – |
| workPhone | string | – | – |
| workPostalCode | string | – | – |
| workState | string | – | – |
| workStreet | string | – | – |
No output schema declared.
No examples provided.
pobuca_create_organization Create organization ~315
WRITE: create a new organization (company) in Pobuca Connect. Not idempotent: calling it twice creates two organizations, so search with pobuca_list_organizations first. POST /api/v1/Organizations.
| Name | Type | Req | Description |
|---|---|---|---|
| allowEmails | boolean | – | Consent flag: may this organization be emailed. |
| allowPhones | boolean | – | Consent flag: may this organization be phoned. |
| allowSms | boolean | – | Consent flag: may this organization be sent SMS. |
| billingCity | string | – | – |
| billingPostalCode | string | – | – |
| billingState | string | – | – |
| billingStreet | string | – | – |
| comments | string | – | Free-text notes on the organization. |
| customFields | array | – | Custom field values (see pobuca_list_custom_fields). |
| string | – | – | |
| fax | string | – | – |
| industryId | string | – | Id from pobuca_list_industries. |
| name | string | yes | Organization name. |
| organizationTypeId | string | – | Id from pobuca_list_organization_types. |
| phone | string | – | – |
| primaryContactId | string | – | Id of the primary contact (from the matching list tool). |
| profession | string | – | – |
| shippingCity | string | – | – |
| shippingPostalCode | string | – | – |
| shippingState | string | – | – |
| shippingStreet | string | – | – |
| tags | array | – | Tags (replaces the existing tags on update). |
| website | string | – | – |
No output schema declared.
No examples provided.
pobuca_get_contact Get contact ~59
One contact by id, with all phone numbers, emails, addresses, organization, team, tags and custom fields. GET /api/v1/Contacts/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| contact_id | string | yes | Contact id (from pobuca_list_contacts). |
No output schema declared.
No examples provided.
pobuca_get_me Get current user ~41
The Pobuca Connect user this API key acts as: id, first name, last name and email. GET /api/v1/Users/Me.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
pobuca_get_organization Get organization ~58
One organization by id, with addresses, type, industry, primary contact, tags and custom fields. GET /api/v1/Organizations/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| organization_id | string | yes | Organization id (from pobuca_list_organizations). |
No output schema declared.
No examples provided.
pobuca_get_team Get team ~42
One team by id. GET /api/v1/Teams/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| team_id | string | yes | Team id (from pobuca_list_teams). |
No output schema declared.
No examples provided.
pobuca_list_contacts List contacts ~230
List contacts (people) with names, phones, emails, addresses, organization, team, tags and custom fields. Paged: 50 per call at most; pass next_skip as skip for the next page. Supports OData $filter and $orderby. To find recently changed contacts use $filter like "updatedat ge 2026-10-01T00:00:00Z". GET /api/v1/Contacts.
| Name | Type | Req | Description |
|---|---|---|---|
| filter | string | – | OData $filter expression, e.g. "updatedat ge 2026-10-01T00:00:00Z" or "startswith(lastname,'Pap')". Field names are case-insensitive. |
| include_deleted | boolean | – | Also return deleted records (default false). |
| orderby | string | – | OData $orderby, e.g. "lastname asc" or "updatedat desc". |
| skip | integer | – | Results to skip. Pass the previous reply's next_skip to get the next page. |
| top | integer | – | Results to return, 1-50 (default 50). |
No output schema declared.
No examples provided.
pobuca_list_countries List countries ~186
List countries with their codes. Paged: 50 per call at most; pass next_skip as skip for the next page. Supports OData $filter and $orderby. GET /api/v1/Countries.
| Name | Type | Req | Description |
|---|---|---|---|
| filter | string | – | OData $filter expression, e.g. "updatedat ge 2026-10-01T00:00:00Z" or "startswith(lastname,'Pap')". Field names are case-insensitive. |
| include_deleted | boolean | – | Also return deleted records (default false). |
| orderby | string | – | OData $orderby, e.g. "lastname asc" or "updatedat desc". |
| skip | integer | – | Results to skip. Pass the previous reply's next_skip to get the next page. |
| top | integer | – | Results to return, 1-50 (default 50). |
No output schema declared.
No examples provided.
pobuca_list_custom_fields List custom fields ~226
List the custom fields defined for contacts, organizations ('Group') or users, with type (Text or Dropdown) and, for dropdowns, the available options. Use the ids and option ids in the customFields of a contact or organization. GET /api/v1/CustomFields/{entityType}.
| Name | Type | Req | Description |
|---|---|---|---|
| entity_type | string | yes | Which records the fields belong to: Contact, Group (organizations) or User. |
| filter | string | – | OData $filter expression, e.g. "updatedat ge 2026-10-01T00:00:00Z" or "startswith(lastname,'Pap')". Field names are case-insensitive. |
| include_deleted | boolean | – | Also return deleted records (default false). |
| orderby | string | – | OData $orderby, e.g. "lastname asc" or "updatedat desc". |
| skip | integer | – | Results to skip. Pass the previous reply's next_skip to get the next page. |
| top | integer | – | Results to return, 1-50 (default 50). |
No output schema declared.
No examples provided.
pobuca_list_departments List departments ~192
List departments (ids for the departmentId of a contact). Paged: 50 per call at most; pass next_skip as skip for the next page. Supports OData $filter and $orderby. GET /api/v1/Departments.
| Name | Type | Req | Description |
|---|---|---|---|
| filter | string | – | OData $filter expression, e.g. "updatedat ge 2026-10-01T00:00:00Z" or "startswith(lastname,'Pap')". Field names are case-insensitive. |
| include_deleted | boolean | – | Also return deleted records (default false). |
| orderby | string | – | OData $orderby, e.g. "lastname asc" or "updatedat desc". |
| skip | integer | – | Results to skip. Pass the previous reply's next_skip to get the next page. |
| top | integer | – | Results to return, 1-50 (default 50). |
No output schema declared.
No examples provided.
pobuca_list_industries List industries ~194
List industries (ids for the industryId of an organization). Paged: 50 per call at most; pass next_skip as skip for the next page. Supports OData $filter and $orderby. GET /api/v1/Industries.
| Name | Type | Req | Description |
|---|---|---|---|
| filter | string | – | OData $filter expression, e.g. "updatedat ge 2026-10-01T00:00:00Z" or "startswith(lastname,'Pap')". Field names are case-insensitive. |
| include_deleted | boolean | – | Also return deleted records (default false). |
| orderby | string | – | OData $orderby, e.g. "lastname asc" or "updatedat desc". |
| skip | integer | – | Results to skip. Pass the previous reply's next_skip to get the next page. |
| top | integer | – | Results to return, 1-50 (default 50). |
No output schema declared.
No examples provided.
pobuca_list_organization_types List organization types ~196
List organization types (ids for the organizationTypeId of an organization). Paged: 50 per call at most; pass next_skip as skip for the next page. Supports OData $filter and $orderby. GET /api/v1/OrganizationTypes.
| Name | Type | Req | Description |
|---|---|---|---|
| filter | string | – | OData $filter expression, e.g. "updatedat ge 2026-10-01T00:00:00Z" or "startswith(lastname,'Pap')". Field names are case-insensitive. |
| include_deleted | boolean | – | Also return deleted records (default false). |
| orderby | string | – | OData $orderby, e.g. "lastname asc" or "updatedat desc". |
| skip | integer | – | Results to skip. Pass the previous reply's next_skip to get the next page. |
| top | integer | – | Results to return, 1-50 (default 50). |
No output schema declared.
No examples provided.
pobuca_list_organizations List organizations ~206
List organizations (companies) with phone, email, website, billing and shipping addresses, type, industry, tags and custom fields. Paged: 50 per call at most; pass next_skip as skip for the next page. Supports OData $filter and $orderby. GET /api/v1/Organizations.
| Name | Type | Req | Description |
|---|---|---|---|
| filter | string | – | OData $filter expression, e.g. "updatedat ge 2026-10-01T00:00:00Z" or "startswith(lastname,'Pap')". Field names are case-insensitive. |
| include_deleted | boolean | – | Also return deleted records (default false). |
| orderby | string | – | OData $orderby, e.g. "lastname asc" or "updatedat desc". |
| skip | integer | – | Results to skip. Pass the previous reply's next_skip to get the next page. |
| top | integer | – | Results to return, 1-50 (default 50). |
No output schema declared.
No examples provided.
pobuca_list_team_members List team members ~195
List which users belong to which team, with their role in the team. Paged: 50 per call at most; pass next_skip as skip for the next page. Supports OData $filter and $orderby. GET /api/v1/UserTeams.
| Name | Type | Req | Description |
|---|---|---|---|
| filter | string | – | OData $filter expression, e.g. "updatedat ge 2026-10-01T00:00:00Z" or "startswith(lastname,'Pap')". Field names are case-insensitive. |
| include_deleted | boolean | – | Also return deleted records (default false). |
| orderby | string | – | OData $orderby, e.g. "lastname asc" or "updatedat desc". |
| skip | integer | – | Results to skip. Pass the previous reply's next_skip to get the next page. |
| top | integer | – | Results to return, 1-50 (default 50). |
No output schema declared.
No examples provided.
pobuca_list_teams List teams ~191
List teams (the groups that own and share contacts). Paged: 50 per call at most; pass next_skip as skip for the next page. Supports OData $filter and $orderby. GET /api/v1/Teams.
| Name | Type | Req | Description |
|---|---|---|---|
| filter | string | – | OData $filter expression, e.g. "updatedat ge 2026-10-01T00:00:00Z" or "startswith(lastname,'Pap')". Field names are case-insensitive. |
| include_deleted | boolean | – | Also return deleted records (default false). |
| orderby | string | – | OData $orderby, e.g. "lastname asc" or "updatedat desc". |
| skip | integer | – | Results to skip. Pass the previous reply's next_skip to get the next page. |
| top | integer | – | Results to return, 1-50 (default 50). |
No output schema declared.
No examples provided.
pobuca_update_contact Update contact ~480
WRITE: change fields of an existing contact; only the fields you pass are sent. Overwrites the previous values (tags and customFields are replaced as given). Look the contact up first and confirm the right one. PATCH /api/v1/Contacts/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| allowEmails | boolean | – | Consent flag: may this contact be emailed. |
| allowPhones | boolean | – | Consent flag: may this contact be phoned. |
| allowSms | boolean | – | Consent flag: may this contact be sent SMS. |
| birthday | string | – | Birthday as an ISO date, e.g. 1985-04-23. |
| comments | string | – | Free-text notes on the contact. |
| contact_id | string | yes | Contact id (from pobuca_list_contacts). |
| customFields | array | – | Custom field values (see pobuca_list_custom_fields). |
| departmentId | string | – | Id of the department (from pobuca_list_departments). |
| string | – | Work email. | |
| string | – | – | |
| firstName | string | – | – |
| gender | string | – | – |
| homeCity | string | – | – |
| homePhone | string | – | – |
| homePostalCode | string | – | – |
| homeState | string | – | – |
| homeStreet | string | – | – |
| jobTitle | string | – | – |
| lastName | string | – | – |
| string | – | – | |
| middleName | string | – | – |
| mobilePhone | string | – | – |
| nickname | string | – | – |
| organizationId | string | – | Id of the organization this contact belongs to (from pobuca_list_organizations). |
| otherEmail | string | – | – |
| personalEmail | string | – | – |
| suffix | string | – | – |
| tags | array | – | Tags (replaces the existing tags on update). |
| teamId | string | – | Id of the team that owns this contact (from pobuca_list_teams). |
| titleSalutation | string | – | Salutation, e.g. Mr, Ms, Dr. |
| string | – | – | |
| website | string | – | – |
| workCity | string | – | – |
| workPhone | string | – | – |
| workPostalCode | string | – | – |
| workState | string | – | – |
| workStreet | string | – | – |
No output schema declared.
No examples provided.
pobuca_update_organization Update organization ~341
WRITE: change fields of an existing organization; only the fields you pass are sent. Overwrites the previous values (tags and customFields are replaced as given). Look the organization up first and confirm the right one. PATCH /api/v1/Organizations/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| allowEmails | boolean | – | Consent flag: may this organization be emailed. |
| allowPhones | boolean | – | Consent flag: may this organization be phoned. |
| allowSms | boolean | – | Consent flag: may this organization be sent SMS. |
| billingCity | string | – | – |
| billingPostalCode | string | – | – |
| billingState | string | – | – |
| billingStreet | string | – | – |
| comments | string | – | Free-text notes on the organization. |
| customFields | array | – | Custom field values (see pobuca_list_custom_fields). |
| string | – | – | |
| fax | string | – | – |
| industryId | string | – | Id from pobuca_list_industries. |
| name | string | – | Organization name. |
| organizationTypeId | string | – | Id from pobuca_list_organization_types. |
| organization_id | string | yes | Organization id (from pobuca_list_organizations). |
| phone | string | – | – |
| primaryContactId | string | – | Id of the primary contact (from the matching list tool). |
| profession | string | – | – |
| shippingCity | string | – | – |
| shippingPostalCode | string | – | – |
| shippingState | string | – | – |
| shippingStreet | string | – | – |
| tags | array | – | Tags (replaces the existing tags on update). |
| website | string | – | – |
No output schema declared.
No examples provided.
How do I install the Pobuca Connect MCP by usefulapi server?
Pobuca Connect MCP by usefulapi is a hosted endpoint at https://pobuca-connect.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 · pobuca-connect.usefulapi.io
claude mcp add --transport http io-usefulapi-pobuca-connect 'https://pobuca-connect.usefulapi.io/mcp'
What is the Pobuca Connect MCP by usefulapi server?
Pobuca Connect MCP by usefulapi is listed in the public MCP registry as io.usefulapi/pobuca-connect. Read and update Pobuca Connect contacts and organizations; look up teams and custom fields. This page covers its hosted endpoint (https://pobuca-connect.usefulapi.io/mcp).
Is the Pobuca Connect MCP by usefulapi server safe to use?
Pobuca Connect 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 Pobuca Connect MCP by usefulapi server expose?
Pobuca Connect MCP by usefulapi exposes 17 tools: pobuca_get_me, pobuca_list_contacts, pobuca_get_contact, pobuca_create_contact, pobuca_update_contact, and 12 more. Their descriptions and schemas cost roughly 3,618 tokens of context every time the server is loaded.
Does the Pobuca Connect MCP by usefulapi server require authentication?
Yes. Pobuca Connect 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 Pobuca Connect MCP by usefulapi server still maintained?
Pobuca Connect 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.