Encharge MCP by usefulapi
io.usefulapi/enchargeusefulapi.iostreamable-httpv1.27.4Scanned
Manage Encharge people, tags, segments and fields, and track events for email automation.
10 tools: 4 can delete or cancel things, 1 change things and 5 only read.
- Reads private data · 1
- Reads text others write · 10
- Can send data out · 0
- No findings
The remote endpoint did not answer the last look. Remote posture
Anlyon alternative
5 of these tools change something. Run those as governed actions.
Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.
Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.
Import an OpenAPI spec →What the Encharge MCP by usefulapi can do
The Encharge MCP by usefulapi is published by usefulapi.io, a domain the MCP Registry verified. It has 10 tools. It can delete or cancel things (4 tools: encharge_upsert_person, encharge_unsubscribe_person, encharge_remove_tags and encharge_track_event) and create or change data (1 tool: encharge_add_tags). 5 tools only read.
1 tool reads private data (encharge_get_people); 10 tools bring in text other people can write (encharge_get_account, encharge_get_people, encharge_list_segment_people and 7 more).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Last scanned Oct 25, 2026, version 1.27.4.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
10 tools
Deletes or cancels 4Claude Code: deny
encharge_remove_tagsWRITE: remove one or more tags from an existing person.Reads text others writeNo findings
Why it is in this group
- The name "encharge_remove_tags" says "remove": a word for removing or ending something.
- The server marks it destructive (destructiveHint: true).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it WRITE: remove one or more tags from an existing person. The tags themselves are not deleted. DELETE /tags.
Annotations the server declares
- title: Remove tags from a person
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: true
encharge_track_eventWRITE: record an event for a person through the Ingest API, for example "Registered user" or "Created Page".Reads text others writeNo findings
Why it is in this group
- The description's first verb is "write": a word for a change.
- The server marks it destructive (destructiveHint: true).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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/.
Annotations the server declares
- title: Track an event
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: false
- openWorldHint: true
encharge_unsubscribe_personWRITE: unsubscribe one person so Encharge sends them no more email.Reads text others writeNo findings
Why it is in this group
- The name "encharge_unsubscribe_person" says "unsubscribe": a word for a change.
- The server marks it destructive (destructiveHint: true).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- title: Unsubscribe a person
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: true
encharge_upsert_personWRITE: create a person, or update the one that already has this email, userId or Encharge id.Reads text others writeNo findings
Why it is in this group
- The name "encharge_upsert_person" says "upsert": a word for a change.
- The server marks it destructive (destructiveHint: true).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- title: Create or update a person
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: true
Changes things 1Claude Code: ask
encharge_add_tagsWRITE: add one or more tags to an existing person.Reads text others writeNo findings
Why it is in this group
- The name "encharge_add_tags" says "add": a word for a change.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it WRITE: add one or more tags to an existing person. Tags that do not exist yet are created. POST /tags.
Annotations the server declares
- title: Add tags to a person
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
Only reads 5Show 5 read-only tools
encharge_get_accountThe Encharge account behind the API key: account id, name, site, status, timezone, people count and active services.Reads text others writeNo findings
Why it is in this group
- The name "encharge_get_account" says "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it The Encharge account behind the API key: account id, name, site, status, timezone, people count and active services. GET /accounts/info.
Annotations the server declares
- title: Get account
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
encharge_get_peopleLook up people (contacts) by email, userId or Encharge id.Reads private dataReads text others writeNo findings
Why it is in this group
- The name "encharge_get_people" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "contact": it reads contacts.
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- untrusted-inputThe description's first sentence says "email": it reads inbound email, which other people can write.
Description, as the server wrote it 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.
Annotations the server declares
- title: Get people
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
encharge_list_fieldsList all person fields (built-in and custom) with name, title, type and whether the field is read-only.Reads text others writeNo findings
Why it is in this group
- The name "encharge_list_fields" says "list": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- title: List person fields
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
encharge_list_segment_peoplePeople in one dynamic segment, with paging (limit/offset), optional sort and a choice of person fields (attributes).Reads text others writeNo findings
Why it is in this group
- The name "encharge_list_segment_people" says "list": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- title: List people in a segment
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
encharge_list_segmentsList the dynamic segments of the account with id, name and conditions.Reads text others writeNo findings
Why it is in this group
- The name "encharge_list_segments" says "list": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it List the dynamic segments of the account with id, name and conditions. Use the ids with encharge_list_segment_people. GET /segments.
Annotations the server declares
- title: List segments
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.
- Reads private data1
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write10
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:35 UTC, unchanged since Oct 29, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- no
- HTTP status of an anonymous initialize
- not observed
- tools/list served without credentials
- no
- Tools that change things, listed without credentials
- 0
- Protocol version
- not observed
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
The probe stopped: The server redirected a POST to a different request.
Posture changes
- Oct 29, 2026
- Reachable: yes to no
- HTTP status of an anonymous initialize: 200 to none
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 5 to 0
- Protocol version: 2025-06-18 to none
- RFC 9728 protected resource metadata: https://encharge.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
- Authorization servers: https://encharge.usefulapi.io to none
- Dynamic client registration: yes to not observed
- Client ID metadata documents: no to not observed
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
PostureRemote posture changed. Reachable: yes -> no; HTTP status of an anonymous initialize: 200 -> none; tools/list served without credentials: yes -> no (and 6 more).View diff
- Reachable: yes to no
- HTTP status of an anonymous initialize: 200 to none
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 5 to 0
- Protocol version: 2025-06-18 to none
- RFC 9728 protected resource metadata: https://encharge.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
- Authorization servers: https://encharge.usefulapi.io to none
- Dynamic client registration: yes to not observed
- Client ID metadata documents: no to not observed
Install
Pinned to version 1.27.4. Values in angle brackets are yours to fill in.
claude mcp add --transport http encharge https://encharge.usefulapi.io/mcpclaude mcp add --transport http encharge https://encharge.usefulapi.io/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__encharge__encharge_get_account",
"mcp__encharge__encharge_get_people",
"mcp__encharge__encharge_list_segment_people",
"mcp__encharge__encharge_list_segments",
"mcp__encharge__encharge_list_fields"
],
"ask": [
"mcp__encharge__encharge_add_tags"
],
"deny": [
"mcp__encharge__encharge_upsert_person",
"mcp__encharge__encharge_unsubscribe_person",
"mcp__encharge__encharge_remove_tags",
"mcp__encharge__encharge_track_event"
]
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as encharge. Review it before you use it.
Capability tags behind 10 rules
- mcp__encharge__encharge_get_account untrusted-input
- mcp__encharge__encharge_get_people private-data, untrusted-input
- mcp__encharge__encharge_list_segment_people untrusted-input
- mcp__encharge__encharge_upsert_person untrusted-input
- mcp__encharge__encharge_unsubscribe_person untrusted-input
- mcp__encharge__encharge_add_tags untrusted-input
- mcp__encharge__encharge_remove_tags untrusted-input
- mcp__encharge__encharge_list_segments untrusted-input
- mcp__encharge__encharge_list_fields untrusted-input
- mcp__encharge__encharge_track_event untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.usefulapi/encharge/verify?hash=3ede03e00182840fee229224bf01b6de56ad22de3258287bc8c9ff7ddf9431b7" | jq -e '.changed == false'Pinned hash 3ede03e00182, from Oct 25, 2026, 23:20 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.usefulapi/encharge/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.usefulapi/encharge)Source: MCP Registry · repository. Synced Nov 18, 2026, 11:18 UTC.
Encharge MCP by usefulapi: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Encharge MCP by usefulapi safe?
- No scan can promise that. What its definitions show: 10 tools, 5 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Encharge MCP by usefulapi delete data?
- Yes. 4 tools can delete, cancel or revoke something: encharge_upsert_person, encharge_unsubscribe_person, encharge_remove_tags and encharge_track_event.
Can the Encharge MCP by usefulapi do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Encharge MCP by usefulapi have?
- 10 tools: 4 destructive, 1 write, 5 read. encharge_upsert_person, encharge_unsubscribe_person, encharge_remove_tags, encharge_track_event, encharge_add_tags, encharge_get_account, encharge_get_people, encharge_list_segment_people and 2 more.
Does the Encharge MCP by usefulapi need sign-in or OAuth?
- Its remote endpoint did not answer the last anonymous look.
Does the Encharge MCP by usefulapi send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Encharge MCP by usefulapi changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Oct 25, 2026.