_ registry / mcp streamable-http · checked 1h ago

encharge-mcp

https://encharge.usefulapi.io

Registry code: 5467340e152bb36a

api record

Tools for Encharge, hosted by usefulapi.io. Read-only tools never change data; ask the user before a tool that creates, changes or deletes Encharge data. Free plan: 100 tool calls per month. Run encharge_usage_status to see the calls used this month. If the user asks for something none of these tools can do, tell the user and, with their OK, run encharge_request_feature to record the request. Pro (unlimited calls, $9/month or $90/year): when the user wants more calls or reaches the limit, run encharge_upgrade; it returns a Stripe Checkout link for the user to open.…

endpoint
https://encharge.usefulapi.io/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is encharge-mcp live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is encharge-mcp free to use?
No — it asks for a key or a login before it will serve.
What tools does encharge-mcp have?
10 tools: encharge_list_segment_people, encharge_remove_tags, encharge_list_fields, encharge_get_account, encharge_list_segments, encharge_get_people, encharge_upsert_person, encharge_unsubscribe_person, ….
Is encharge-mcp safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
270ms

last good check

priced tools
0

of 10 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 10 tools
10 auth-required 10 of 10 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • encharge_list_segment_people auth-required never probed

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "segment_id"
  ],
  "properties": {
    "sort": {
      "type": "string",
      "maxLength": 100,
      "minLength": 1,
      "description": "Person field name to sort by."
    },
    "limit": {
      "type": "integer",
      "maximum": 100,
      "description": "People per page, 1-100 (default 25).",
      "exclusiveMinimum": 0
    },
    "order": {
      "enum": [
        "asc",
        "desc"
      ],
      "type": "string",
      "description": "Sort order (default asc)."
    },
    "offset": {
      "type": "integer",
      "maximum": 1000000,
      "minimum": 0,
      "description": "Number of people to skip (default 0). Pass the previous reply's next_offset."
    },
    "attributes": {
      "type": "array",
      "items": {
        "type": "string",
        "maxLength": 100,
        "minLength": 1
      },
      "maxItems": 50,
      "description": "Person field names to return. Default: the standard fields."
    },
    "segment_id": {
      "type": "integer",
      "maximum": 9007199254740991,
      "description": "Encharge segment id (from encharge_list_segments).",
      "exclusiveMinimum": 0
    }
  }
}
    arguments 51 lines
  • encharge_remove_tags auth-required never probed

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

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "tags"
  ],
  "properties": {
    "id": {
      "type": "string",
      "maxLength": 100,
      "minLength": 1,
      "description": "Encharge id of the person (a UUID)."
    },
    "tags": {
      "type": "array",
      "items": {
        "type": "string",
        "maxLength": 100,
        "minLength": 1
      },
      "maxItems": 50,
      "minItems": 1,
      "description": "Tag names. A tag name cannot contain a comma."
    },
    "email": {
      "type": "string",
      "format": "includes",
      "pattern": "@",
      "maxLength": 320,
      "minLength": 3,
      "description": "Email address of the person."
    },
    "userId": {
      "type": "string",
      "maxLength": 200,
      "minLength": 1,
      "description": "The userId your own app uses for the person."
    }
  }
}
    arguments 40 lines
  • encharge_list_fields auth-required 1h ago

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {}
}
    arguments 5 lines
  • encharge_get_account auth-required 1h ago

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

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {}
}
    arguments 5 lines
  • encharge_list_segments auth-required 1h ago

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

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {}
}
    arguments 5 lines
  • encharge_get_people auth-required never probed

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "people"
  ],
  "properties": {
    "people": {
      "type": "array",
      "items": {
        "type": "object",
        "properties": {
          "id": {
            "type": "string",
            "maxLength": 100,
            "minLength": 1,
            "description": "Encharge id of the person (a UUID)."
          },
          "email": {
            "type": "string",
            "format": "includes",
            "pattern": "@",
            "maxLength": 320,
            "minLength": 3,
            "description": "Email address of the person."
          },
          "userId": {
            "type": "string",
            "maxLength": 200,
            "minLength": 1,
            "description": "The userId your own app uses for the person."
          }
        }
      },
      "maxItems": 20,
      "minItems": 1,
      "description": "People to look up, each with at least one of email, userId or id."
    }
  }
}
    arguments 40 lines
  • encharge_upsert_person auth-required never probed

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {
    "id": {
      "type": "string",
      "maxLength": 100,
      "minLength": 1,
      "description": "Encharge id of the person (a UUID)."
    },
    "email": {
      "type": "string",
      "format": "includes",
      "pattern": "@",
      "maxLength": 320,
      "minLength": 3,
      "description": "Email address of the person."
    },
    "fields": {
      "type": "object",
      "description": "Other person fields by field name (see encharge_list_fields), for example { \"company\": \"Acme\", \"plan\": \"pro\" }. Dates as ISO 8601.",
      "propertyNames": {
        "type": "string",
        "maxLength": 100,
        "minLength": 1
      },
      "additionalProperties": {
        "anyOf": [
          {
            "type": "string",
            "maxLength": 10000
          },
          {
            "type": "number"
          },
          {
            "type": "boolean"
          },
          {
            "type": "null"
          }
        ]
      }
    },
    "userId": {
      "type": "string",
      "maxLength": 200,
      "minLength": 1,
      "description": "The userId your own app uses for the person."
    },
    "lastName": {
      "type": "string",
      "maxLength": 200,
      "minLength": 1,
      "description": "Last name."
    },
    "firstName": {
      "type": "string",
      "maxLength": 200,
      "minLength": 1,
      "description": "First name."
    }
  }
}
    arguments 64 lines
  • encharge_unsubscribe_person auth-required never probed

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {
    "id": {
      "type": "string",
      "maxLength": 100,
      "minLength": 1,
      "description": "Encharge id of the person (a UUID)."
    },
    "email": {
      "type": "string",
      "format": "includes",
      "pattern": "@",
      "maxLength": 320,
      "minLength": 3,
      "description": "Email address of the person."
    },
    "userId": {
      "type": "string",
      "maxLength": 200,
      "minLength": 1,
      "description": "The userId your own app uses for the person."
    }
  }
}
    arguments 26 lines
  • encharge_add_tags auth-required never probed

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

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "tags"
  ],
  "properties": {
    "id": {
      "type": "string",
      "maxLength": 100,
      "minLength": 1,
      "description": "Encharge id of the person (a UUID)."
    },
    "tags": {
      "type": "array",
      "items": {
        "type": "string",
        "maxLength": 100,
        "minLength": 1
      },
      "maxItems": 50,
      "minItems": 1,
      "description": "Tag names. A tag name cannot contain a comma."
    },
    "email": {
      "type": "string",
      "format": "includes",
      "pattern": "@",
      "maxLength": 320,
      "minLength": 3,
      "description": "Email address of the person."
    },
    "userId": {
      "type": "string",
      "maxLength": 200,
      "minLength": 1,
      "description": "The userId your own app uses for the person."
    }
  }
}
    arguments 40 lines
  • encharge_track_event auth-required never probed

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

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "name"
  ],
  "properties": {
    "name": {
      "type": "string",
      "maxLength": 200,
      "minLength": 1,
      "description": "Event name."
    },
    "tags": {
      "type": "array",
      "items": {
        "type": "string",
        "maxLength": 100,
        "minLength": 1
      },
      "maxItems": 50,
      "description": "Tags to add to the person."
    },
    "email": {
      "type": "string",
      "format": "includes",
      "pattern": "@",
      "maxLength": 320,
      "minLength": 3,
      "description": "Email address of the person."
    },
    "userId": {
      "type": "string",
      "maxLength": 200,
      "minLength": 1,
      "description": "The userId your own app uses for the person."
    },
    "properties": {
      "type": "object",
      "description": "Properties of the event; values may be nested objects, for example { \"plan\": \"Premium\", \"trial\": { \"length\": 14 } }. Dates as ISO 8601.",
      "propertyNames": {
        "type": "string",
        "maxLength": 100,
        "minLength": 1
      },
      "additionalProperties": {}
    },
    "user_fields": {
      "type": "object",
      "description": "Person fields to set on this person, by field name.",
      "propertyNames": {
        "type": "string",
        "maxLength": 100,
        "minLength": 1
      },
      "additionalProperties": {
        "anyOf": [
          {
            "type": "string",
            "maxLength": 10000
          },
          {
            "type": "number"
          },
          {
            "type": "boolean"
          },
          {
            "type": "null"
          }
        ]
      }
    }
  }
}
    arguments 75 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 5467340e152bb36a.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/5467340e152bb36a/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/5467340e152bb36a/badge.svg)](https://brick.blue/agent/5467340e152bb36a?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.

_ also on usefulapi.io 84 entries

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.

76 more sit on this domain. All of them.