Gladly MCP by usefulapi
REMOTE · GLADLY.USEFULAPI.IO
Find customers, read conversations, items and tasks; add internal notes in Gladly.
Available components
Last scanned (4 hours ago)
Scores higher than 4% of remote servers
Reachable. Last reached 5 Nov 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 Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- 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
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 Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
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 Nov 26 −48
- Endpoint reachability: reachable → not serving MCP ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: pass → unverified ▼ security
- Stability: 0.03 → unverified ▼ security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 1 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 31 Oct 26 66
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 5 Nov 2026 · Probed https://gladly.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 gladly.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 38690 | 8 | Verified |
| usefulapi.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 302 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://gladly.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/gladly/ |
| http (plaintext) | http://gladly.usefulapi.io/mcp | Inconclusive | 302 | http://gladly.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 →
gladly_add_conversation_note Add an internal note to a conversation ~91
WRITE: add an internal note to a conversation. The note is for agents only; the customer does not see it. Each call adds a NEW note, so do not repeat a call that succeeded. Gladly API: POST /api/v1/conversations/{conversationId}/notes.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | Plain text of the note. |
| conversation_id | string | yes | The conversation id. |
No output schema declared.
No examples provided.
gladly_find_customers Find customers ~122
Find customer profiles by EXACTLY ONE identifier: email, phone number (E.164, for example +16505551987) or externalCustomerId. Returns at most 50 profiles, newest update first. Gladly API: GET /api/v1/customer-profiles.
| Name | Type | Req | Description |
|---|---|---|---|
| string | – | Customer email address. | |
| external_customer_id | string | – | Customer id in your own system of record (only for older Lookup Adaptors). |
| phone_number | string | – | Phone number in E.164 format, for example +16505551987. |
No output schema declared.
No examples provided.
gladly_get_agent Get an agent ~47
Get one agent profile by id. Gladly API: GET /api/v1/agents/{agentId}.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | The agent id (from gladly_list_agents). |
No output schema declared.
No examples provided.
gladly_get_conversation Get a conversation ~70
Get the metadata of one conversation: assignee, inbox, topics, custom attributes, status. A merged conversation returns the surviving one. Gladly API: GET /api/v1/conversations/{conversationId}.
| Name | Type | Req | Description |
|---|---|---|---|
| conversation_id | string | yes | The conversation id (from gladly_list_customer_conversations). |
No output schema declared.
No examples provided.
gladly_get_conversation_item Get a conversation item ~61
Get one conversation item (message, email, note, call) by id. Gladly API: GET /api/v1/conversation-items/{itemId}.
| Name | Type | Req | Description |
|---|---|---|---|
| item_id | string | yes | The item id (from gladly_list_conversation_items). |
No output schema declared.
No examples provided.
gladly_get_customer Get a customer ~60
Get one customer profile by id: name, emails, phones, address, custom attributes. Gladly API: GET /api/v1/customer-profiles/{customerId}.
| Name | Type | Req | Description |
|---|---|---|---|
| customer_id | string | yes | The customer id (from gladly_find_customers). |
No output schema declared.
No examples provided.
gladly_get_inbox Get an inbox ~52
Get the metadata of one inbox by id. Gladly API: GET /api/v1/inboxes/{inboxId}.
| Name | Type | Req | Description |
|---|---|---|---|
| inbox_id | string | yes | The inbox id (from gladly_list_inboxes). |
No output schema declared.
No examples provided.
gladly_get_organization Get the organization ~42
Get metadata about the Gladly organization: id, name, login domain, time zone, URL. Gladly API: GET /api/v1/organization.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
gladly_get_task Get a task ~58
Get one task by id: body, assignee, due date, status, topics. Gladly API: GET /api/v1/tasks/{taskId}.
| Name | Type | Req | Description |
|---|---|---|---|
| task_id | string | yes | The task id (from gladly_list_customer_tasks). |
No output schema declared.
No examples provided.
gladly_list_agents List agents ~36
List the agents (support users) with id, name and email address. Gladly API: GET /api/v1/agents.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
gladly_list_audiences List audiences ~36
List the audiences used to target answers (id, name). Gladly API: GET /api/v1/audiences.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
gladly_list_conversation_items List the timeline of a conversation ~78
List the timeline items of a conversation (messages, emails, calls, notes), oldest first, at most 1000. Gladly API: GET /api/v1/conversations/{conversationId}/items.
| Name | Type | Req | Description |
|---|---|---|---|
| conversation_id | string | yes | The conversation id. |
| session_id | string | – | Only items of this session id. |
No output schema declared.
No examples provided.
gladly_list_customer_conversations List conversations of a customer ~78
List the conversations of one customer, oldest first (at most 100; the reply says if it was cut). Each has topics, status and assignee. Gladly API: GET /api/v1/customers/{customerId}/conversations.
| Name | Type | Req | Description |
|---|---|---|---|
| customer_id | string | yes | The customer id (from gladly_find_customers). |
No output schema declared.
No examples provided.
gladly_list_customer_tasks List tasks of a customer ~72
List the tasks of one customer, newest first (at most 2000), optionally only OPEN or CLOSED. Gladly API: GET /api/v1/customers/{customerId}/tasks.
| Name | Type | Req | Description |
|---|---|---|---|
| customer_id | string | yes | The customer id. |
| status | string | – | Only tasks with this status. |
No output schema declared.
No examples provided.
gladly_list_inboxes List inboxes ~34
List the inboxes with id, name and disabled state. Gladly API: GET /api/v1/inboxes.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
gladly_list_topics List topics ~47
List the conversation topics (id, name, parentId, disabled). Use it to turn the topicIds of a conversation into names. Gladly API: GET /api/v1/topics.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the Gladly MCP by usefulapi server?
Gladly MCP by usefulapi is a hosted endpoint at https://gladly.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 · gladly.usefulapi.io
claude mcp add --transport http io-usefulapi-gladly 'https://gladly.usefulapi.io/mcp'
What is the Gladly MCP by usefulapi server?
Gladly MCP by usefulapi is listed in the public MCP registry as io.usefulapi/gladly. Find customers, read conversations, items and tasks; add internal notes in Gladly. This page covers its hosted endpoint (https://gladly.usefulapi.io/mcp).
Is the Gladly MCP by usefulapi server safe to use?
Gladly MCP by usefulapi scores 18 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 Gladly MCP by usefulapi server expose?
Gladly MCP by usefulapi exposes 16 tools: gladly_get_organization, gladly_list_agents, gladly_get_agent, gladly_list_inboxes, gladly_get_inbox, and 11 more. Their descriptions and schemas cost roughly 984 tokens of context every time the server is loaded.
Does the Gladly MCP by usefulapi server require authentication?
Its publisher declares no required credentials for Gladly MCP by usefulapi. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the Gladly MCP by usefulapi server still maintained?
Gladly MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.