io.usefulapi/recharge
REMOTE · RECHARGE.USEFULAPI.IO · SCANNED SEP 20
Read subscriptions, customers, charges, orders; skip charges, cancel or activate subscriptions.
Available components
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 Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 401, which proves neither a plaintext path nor enforcement. 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
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability0
- Instruction-quality not yet verified: the AI judgement didn't run.Unverified
- Nothing to assess: this server exposes no tool/resource definitions to measure a footprint for. See how to fix → Fail
- Nothing to assess: this server has no tools to check for usage examples. See how to fix → Fail
Stability & Change Management0
- Stability check failed: schema churn in the 6 days we've observed: 15 tool removals, 0 breaking changes, 1 auth/transport breaks, 0 additions. See how to fix → Fail
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools.Unverified
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Unverified: 2 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.
How do I install the io.usefulapi/recharge MCP server?
io.usefulapi/recharge is a hosted endpoint at https://recharge.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 · recharge.usefulapi.io
claude mcp add --transport http io-usefulapi-recharge 'https://recharge.usefulapi.io/mcp'
{
"mcpServers": {
"io-usefulapi-recharge": {
"url": "https://recharge.usefulapi.io/mcp"
}
}
} {
"servers": {
"io-usefulapi-recharge": {
"type": "http",
"url": "https://recharge.usefulapi.io/mcp"
}
}
} [mcp_servers.io-usefulapi-recharge] url = "https://recharge.usefulapi.io/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-usefulapi-recharge": {
"type": "remote",
"url": "https://recharge.usefulapi.io/mcp",
"enabled": true
}
}
} openclaw mcp add io-usefulapi-recharge --url 'https://recharge.usefulapi.io/mcp' --transport streamable-http
mcp_servers:
io-usefulapi-recharge:
url: "https://recharge.usefulapi.io/mcp" {
"McpServers": {
"io-usefulapi-recharge": {
"Transport": "http",
"Url": "https://recharge.usefulapi.io/mcp"
}
}
} assistant mcp add io-usefulapi-recharge -t streamable-http -u 'https://recharge.usefulapi.io/mcp'
{
"mcpServers": {
"io-usefulapi-recharge": {
"type": "http",
"url": "https://recharge.usefulapi.io/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 20 Sept 26 −42
- Authorization: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Stability: 0.17 → fail ▼ security
- Schema quality: excellent → unverified ▼ functional
- Schema quality: fail → unverified ▼ functional
- Schema quality: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 19 Sept 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.
- 17 Sept 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.
- 15 Sept 26 +1
- Stability: unverified → 0.03 ▲ functional
- 14 Sept 26 +52
- Authorization: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- First check of Judged manipulation: pass security
- Schema quality: unverified → fail ▼ functional
- Schema quality: unverified → fail ▼ functional
- MCP protocol: unverified → fail ▼ functional
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Schema quality: unverified → excellent ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- First check of Destructive annotations: 50 functional
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 3 Aug 26 0
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: fail → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: fail → unverified ▼ functional
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 20 Sept 2026 · Probed https://recharge.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 | 16 Sept 2026 | 15 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | ce00ae835ab140120e18dba8a14d13d3 |
| SANs: usefulapi.io, recharge.usefulapi.io, *.recharge.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 recharge.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 No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://recharge.usefulapi.io/mcp | Verified | 200 | |
| http (plaintext) | http://recharge.usefulapi.io/mcp | Inconclusive | 401 |
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 →
No tool schema has been captured from this endpoint yet.
What is the io.usefulapi/recharge MCP server?
io.usefulapi/recharge is an MCP server listed in the public MCP registry as io.usefulapi/recharge. Read subscriptions, customers, charges, orders; skip charges, cancel or activate subscriptions. This page covers its hosted endpoint (https://recharge.usefulapi.io/mcp).
Is the io.usefulapi/recharge MCP server safe to use?
io.usefulapi/recharge scores 31 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.
Does the io.usefulapi/recharge MCP server require authentication?
No. We connected to io.usefulapi/recharge without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.usefulapi/recharge MCP server still maintained?
io.usefulapi/recharge is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.