# Gladly MCP by usefulapi (remote · gladly.usefulapi.io)

Find customers, read conversations, items and tasks; add internal notes in Gladly.

- Trust score: 18/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `gladly.usefulapi.io`: 18/100 (this document), [markdown](https://verifymcp.io/servers/io-usefulapi-gladly/gladly.md), [page](https://verifymcp.io/servers/io-usefulapi-gladly/gladly)

## Channel facts

- Endpoint: `https://gladly.usefulapi.io/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.5.2`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  - HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly.
- **Schema Quality & AI Usability**: 0/100
  - Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Capabilities**: 0/100
  - Capabilities not yet verified: we couldn't read the endpoint's capabilities.

**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.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http io-usefulapi-gladly 'https://gladly.usefulapi.io/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "io-usefulapi-gladly": {
      "url": "https://gladly.usefulapi.io/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "io-usefulapi-gladly": {
      "type": "http",
      "url": "https://gladly.usefulapi.io/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.io-usefulapi-gladly]
url = "https://gladly.usefulapi.io/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-usefulapi-gladly": {
      "type": "remote",
      "url": "https://gladly.usefulapi.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-usefulapi-gladly --url 'https://gladly.usefulapi.io/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-usefulapi-gladly:
    url: "https://gladly.usefulapi.io/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "io-usefulapi-gladly": {
      "Transport": "http",
      "Url": "https://gladly.usefulapi.io/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-usefulapi-gladly -t streamable-http -u 'https://gladly.usefulapi.io/mcp'
```

### Other

```json
{
  "mcpServers": {
    "io-usefulapi-gladly": {
      "type": "http",
      "url": "https://gladly.usefulapi.io/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-02 (score 18, −48)

- [security regression] Endpoint reachability: reachable → not serving MCP
- [security regression] Tool safety: pass → unverified
- [security regression] Authorization: pass → unverified
- [security regression] Stability: 0.03 → unverified
- [functional regression] Schema quality: 100 → unverified
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified

### 2026-11-01 (score 66, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-31 (score 66)

First indexed and scored.

## MCP tools (16)

### `gladly_get_organization` (~42 tokens)

Get the organization

Get metadata about the Gladly organization: id, name, login domain, time zone, URL. Gladly API: GET /api/v1/organization.

### `gladly_list_agents` (~36 tokens)

List agents

List the agents (support users) with id, name and email address. Gladly API: GET /api/v1/agents.

### `gladly_get_agent` (~47 tokens)

Get an agent

Get one agent profile by id. Gladly API: GET /api/v1/agents/{agentId}.

Input parameters:

- `agent_id` (string, required): The agent id (from gladly_list_agents).

### `gladly_list_inboxes` (~34 tokens)

List inboxes

List the inboxes with id, name and disabled state. Gladly API: GET /api/v1/inboxes.

### `gladly_get_inbox` (~52 tokens)

Get an inbox

Get the metadata of one inbox by id. Gladly API: GET /api/v1/inboxes/{inboxId}.

Input parameters:

- `inbox_id` (string, required): The inbox id (from gladly_list_inboxes).

### `gladly_list_topics` (~47 tokens)

List topics

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.

### `gladly_list_audiences` (~36 tokens)

List audiences

List the audiences used to target answers (id, name). Gladly API: GET /api/v1/audiences.

### `gladly_find_customers` (~122 tokens)

Find customers

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.

Input parameters:

- `email` (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.

### `gladly_get_customer` (~60 tokens)

Get a customer

Get one customer profile by id: name, emails, phones, address, custom attributes. Gladly API: GET /api/v1/customer-profiles/{customerId}.

Input parameters:

- `customer_id` (string, required): The customer id (from gladly_find_customers).

### `gladly_list_customer_conversations` (~78 tokens)

List conversations of a customer

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.

Input parameters:

- `customer_id` (string, required): The customer id (from gladly_find_customers).

### `gladly_get_conversation` (~70 tokens)

Get a conversation

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}.

Input parameters:

- `conversation_id` (string, required): The conversation id (from gladly_list_customer_conversations).

### `gladly_list_conversation_items` (~78 tokens)

List the timeline of a conversation

List the timeline items of a conversation (messages, emails, calls, notes), oldest first, at most 1000. Gladly API: GET /api/v1/conversations/{conversationId}/items.

Input parameters:

- `conversation_id` (string, required): The conversation id.
- `session_id` (string): Only items of this session id.

### `gladly_get_conversation_item` (~61 tokens)

Get a conversation item

Get one conversation item (message, email, note, call) by id. Gladly API: GET /api/v1/conversation-items/{itemId}.

Input parameters:

- `item_id` (string, required): The item id (from gladly_list_conversation_items).

### `gladly_list_customer_tasks` (~72 tokens)

List tasks of a customer

List the tasks of one customer, newest first (at most 2000), optionally only OPEN or CLOSED. Gladly API: GET /api/v1/customers/{customerId}/tasks.

Input parameters:

- `customer_id` (string, required): The customer id.
- `status` (string): Only tasks with this status.

### `gladly_get_task` (~58 tokens)

Get a task

Get one task by id: body, assignee, due date, status, topics. Gladly API: GET /api/v1/tasks/{taskId}.

Input parameters:

- `task_id` (string, required): The task id (from gladly_list_customer_tasks).

### `gladly_add_conversation_note` (~91 tokens)

Add an internal note to a conversation

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.

Input parameters:

- `body` (string, required): Plain text of the note.
- `conversation_id` (string, required): The conversation id.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/io-usefulapi-gladly/gladly#diagnostics

## Score history

- 2026-11-05: 18
- 2026-11-04: 18
- 2026-11-03: 18
- 2026-11-02: 18
- 2026-11-01: 66
- 2026-10-31: 66

## Common questions

### 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.

## Links

- Remote endpoint: https://gladly.usefulapi.io/mcp
- Repository: https://github.com/m190/usefulapi-mcp
- Website: https://usefulapi.io/gladly/
- Changelog RSS feed: https://verifymcp.io/servers/io-usefulapi-gladly/gladly.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-usefulapi-gladly/gladly.json
- HTML version of this page: https://verifymcp.io/servers/io-usefulapi-gladly/gladly