Encharge MCP by usefulapi
REMOTE · ENCHARGE.USEFULAPI.IO
Manage Encharge people, tags, segments and fields, and track events for email automation.
Available components
Last scanned (5 hours ago)
Scores higher than 47% of remote servers
Reachable. Last reached 17 Oct 2026.
Category Marketing and SEO
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 Usability82
- 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 1237 tokens (~123/item across 10 items; 10 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 Management17
- Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 11 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.
- 17 Oct 26 +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.
- 15 Oct 26 +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.
- 14 Oct 26 +2
- The server rewrote its instructions, which are the text every model session reads security
- 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 functional
- 13 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 12 Oct 26 61
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 17 Oct 2026 · Probed https://encharge.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 encharge.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 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://encharge.usefulapi.io/.well-known/oauth-protected-resource/mcp"
Bearer realm="OAuth", resource_metadata="https://encharge.usefulapi.io/.well-known/oauth-protected-resource/mcp"Protected resource metadata
| Document | https://encharge.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://encharge.usefulapi.io/mcp |
| Authorisation server | https://encharge.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://encharge.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/encharge/ |
| http (plaintext) | http://encharge.usefulapi.io/mcp | Inconclusive | 302 | http://encharge.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 →
encharge_add_tags Add tags to a person ~98
WRITE: add one or more tags to an existing person. Tags that do not exist yet are created. POST /tags.
| Name | Type | Req | Description |
|---|---|---|---|
| string | – | Email address of the person. | |
| id | string | – | Encharge id of the person (a UUID). |
| tags | array | yes | Tag names. A tag name cannot contain a comma. |
| userId | string | – | The userId your own app uses for the person. |
No output schema declared.
No examples provided.
encharge_get_account Get account ~41
The Encharge account behind the API key: account id, name, site, status, timezone, people count and active services. GET /accounts/info.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
encharge_get_people Get people ~90
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.
| Name | Type | Req | Description |
|---|---|---|---|
| people | array | yes | People to look up, each with at least one of email, userId or id. |
No output schema declared.
No examples provided.
encharge_list_fields List person fields ~48
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
encharge_list_segment_people List people in a segment ~165
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Encharge segment id (from encharge_list_segments). |
| sort | string | – | Person field name to sort by. |
No output schema declared.
No examples provided.
encharge_list_segments List segments ~38
List the dynamic segments of the account with id, name and conditions. Use the ids with encharge_list_segment_people. GET /segments.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
encharge_remove_tags Remove tags from a person ~96
WRITE: remove one or more tags from an existing person. The tags themselves are not deleted. DELETE /tags.
| Name | Type | Req | Description |
|---|---|---|---|
| string | – | Email address of the person. | |
| id | string | – | Encharge id of the person (a UUID). |
| tags | array | yes | Tag names. A tag name cannot contain a comma. |
| userId | string | – | The userId your own app uses for the person. |
No output schema declared.
No examples provided.
encharge_track_event Track an event ~192
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/.
| Name | Type | Req | Description |
|---|---|---|---|
| string | – | Email address of the person. | |
| name | string | yes | 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. |
No output schema declared.
No examples provided.
encharge_unsubscribe_person Unsubscribe a person ~96
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
encharge_upsert_person Create or update a person ~163
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
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.
remote · encharge.usefulapi.io
claude mcp add --transport http io-usefulapi-encharge 'https://encharge.usefulapi.io/mcp'
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.