# Encharge MCP by usefulapi (remote · encharge.usefulapi.io)

Manage Encharge people, tags, segments and fields, and track events for email automation.

- Trust score: 65/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-17

## Components

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

## Channel facts

- Endpoint: `https://encharge.usefulapi.io/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.0.0`

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

- **Endpoint Security**: 78/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - 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.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly.
- **Schema Quality & AI Usability**: 82/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1237 tokens (~123/item across 10 items; 10 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 17/100
  - Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the Encharge MCP by usefulapi server?

Encharge MCP by usefulapi is a hosted endpoint at https://encharge.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-encharge 'https://encharge.usefulapi.io/mcp'
```

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "io-usefulapi-encharge": {
      "type": "http",
      "url": "https://encharge.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-10-17 (score 65, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-15 (score 64, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-14 (score 63, +2)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional] The server now declares the “prompts” capability
- [functional] First check of Schema quality: 100
- [functional] New prompt “getting_started”
- [functional] Server version: 1.0.0 → 1.1.0

### 2026-10-13 (score 61, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-12 (score 61)

First indexed and scored.

## MCP tools (10)

### `encharge_get_account` (~41 tokens)

Get account

The Encharge account behind the API key: account id, name, site, status, timezone, people count and active services. GET /accounts/info.

### `encharge_get_people` (~90 tokens)

Get people

Look up people (contacts) by email, userId or Encharge id. Pass up to 20 people, each with at least one identifier. Returns each person with all fields, tags and segment data; a person that does not exist is left out. GET /people.

Input parameters:

- `people` (array, required): People to look up, each with at least one of email, userId or id.

### `encharge_list_segment_people` (~165 tokens)

List people in a segment

People in one dynamic segment, with paging (limit/offset), optional sort and a choice of person fields (attributes). Use encharge_list_segments for segment ids and encharge_list_fields for field names. GET /segments/{segmentId}/people.

Input parameters:

- `attributes` (array): Person field names to return. Default: the standard fields.
- `limit` (integer): People per page, 1-100 (default 25).
- `offset` (integer): Number of people to skip (default 0). Pass the previous reply's next_offset.
- `order` (string): Sort order (default asc).
- `segment_id` (integer, required): Encharge segment id (from encharge_list_segments).
- `sort` (string): Person field name to sort by.

### `encharge_upsert_person` (~163 tokens)

Create or update a person

WRITE: create a person, or update the one that already has this email, userId or Encharge id. Only the fields you pass are set. Use encharge_add_tags for tags. POST /people.

Input parameters:

- `email` (string): Email address of the person.
- `fields` (object): Other person fields by field name (see encharge_list_fields), for example { "company": "Acme", "plan": "pro" }. Dates as ISO 8601.
- `firstName` (string): First name.
- `id` (string): Encharge id of the person (a UUID).
- `lastName` (string): Last name.
- `userId` (string): The userId your own app uses for the person.

### `encharge_unsubscribe_person` (~96 tokens)

Unsubscribe a person

WRITE: unsubscribe one person so Encharge sends them no more email. The person stays in Encharge. Identify them by email, userId or Encharge id. POST /people/unsubscribe.

Input parameters:

- `email` (string): Email address of the person.
- `id` (string): Encharge id of the person (a UUID).
- `userId` (string): The userId your own app uses for the person.

### `encharge_add_tags` (~98 tokens)

Add tags to a person

WRITE: add one or more tags to an existing person. Tags that do not exist yet are created. POST /tags.

Input parameters:

- `email` (string): Email address of the person.
- `id` (string): Encharge id of the person (a UUID).
- `tags` (array, required): Tag names. A tag name cannot contain a comma.
- `userId` (string): The userId your own app uses for the person.

### `encharge_remove_tags` (~96 tokens)

Remove tags from a person

WRITE: remove one or more tags from an existing person. The tags themselves are not deleted. DELETE /tags.

Input parameters:

- `email` (string): Email address of the person.
- `id` (string): Encharge id of the person (a UUID).
- `tags` (array, required): Tag names. A tag name cannot contain a comma.
- `userId` (string): The userId your own app uses for the person.

### `encharge_list_segments` (~38 tokens)

List segments

List the dynamic segments of the account with id, name and conditions. Use the ids with encharge_list_segment_people. GET /segments.

### `encharge_list_fields` (~48 tokens)

List person fields

List all person fields (built-in and custom) with name, title, type and whether the field is read-only. Use the names in encharge_upsert_person. GET /fields.

### `encharge_track_event` (~192 tokens)

Track an event

WRITE: record an event for a person through the Ingest API, for example "Registered user" or "Created Page". The person is created or updated from `user`. Use the event name "identify" to only create or update a person. Needs the account write key. POST https://ingest.encharge.io/v1/.

Input parameters:

- `email` (string): Email address of the person.
- `name` (string, required): Event name.
- `properties` (object): Properties of the event; values may be nested objects, for example { "plan": "Premium", "trial": { "length": 14 } }. Dates as ISO 8601.
- `tags` (array): Tags to add to the person.
- `userId` (string): The userId your own app uses for the person.
- `user_fields` (object): Person fields to set on this person, by field name.

## Diagnostics

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

## Score history

- 2026-10-17: 65
- 2026-10-16: 64
- 2026-10-15: 64
- 2026-10-14: 63
- 2026-10-13: 61
- 2026-10-12: 61

## Common questions

### What is the Encharge MCP by usefulapi server?

Encharge MCP by usefulapi is listed in the public MCP registry as io.usefulapi/encharge. Manage Encharge people, tags, segments and fields, and track events for email automation. This page covers its hosted endpoint (https://encharge.usefulapi.io/mcp).

### Is the Encharge MCP by usefulapi server safe to use?

Encharge MCP by usefulapi scores 65 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 Encharge MCP by usefulapi server expose?

Encharge MCP by usefulapi exposes 10 tools: encharge_get_account, encharge_get_people, encharge_list_segment_people, encharge_upsert_person, encharge_unsubscribe_person, and 5 more. Their descriptions and schemas cost roughly 1,027 tokens of context every time the server is loaded.

### Does the Encharge MCP by usefulapi server require authentication?

Yes. Encharge 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 Encharge MCP by usefulapi server still maintained?

Encharge MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 17 October 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://encharge.usefulapi.io/mcp
- Repository: https://github.com/m190/usefulapi-mcp
- Website: https://usefulapi.io/encharge/
- Changelog RSS feed: https://verifymcp.io/servers/io-usefulapi-encharge/encharge.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-usefulapi-encharge/encharge.json
- HTML version of this page: https://verifymcp.io/servers/io-usefulapi-encharge/encharge