io.usefulapi/braintree
REMOTE · BRAINTREE.USEFULAPI.IO · SCANNED SEP 20
Search Braintree transactions, customers and payment methods, and refund or void charges.
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 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 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
- 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 & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability81
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 823 tokens (~117/item across 7 items; 7 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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 7 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
How do I install the io.usefulapi/braintree MCP server?
io.usefulapi/braintree is a hosted endpoint at https://braintree.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 · braintree.usefulapi.io
claude mcp add --transport http io-usefulapi-braintree 'https://braintree.usefulapi.io/mcp'
{
"mcpServers": {
"io-usefulapi-braintree": {
"url": "https://braintree.usefulapi.io/mcp"
}
}
} {
"servers": {
"io-usefulapi-braintree": {
"type": "http",
"url": "https://braintree.usefulapi.io/mcp"
}
}
} [mcp_servers.io-usefulapi-braintree] url = "https://braintree.usefulapi.io/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-usefulapi-braintree": {
"type": "remote",
"url": "https://braintree.usefulapi.io/mcp",
"enabled": true
}
}
} openclaw mcp add io-usefulapi-braintree --url 'https://braintree.usefulapi.io/mcp' --transport streamable-http
mcp_servers:
io-usefulapi-braintree:
url: "https://braintree.usefulapi.io/mcp" {
"McpServers": {
"io-usefulapi-braintree": {
"Transport": "http",
"Url": "https://braintree.usefulapi.io/mcp"
}
}
} assistant mcp add io-usefulapi-braintree -t streamable-http -u 'https://braintree.usefulapi.io/mcp'
{
"mcpServers": {
"io-usefulapi-braintree": {
"type": "http",
"url": "https://braintree.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.
- 26 Aug 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 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
- 31 Jul 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
- 30 Jul 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
- 28 Jul 26 0
- Stability: unverified → 0.03 ▲ functional
- 27 Jul 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
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://braintree.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 | 14 Sept 2026 | 13 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | d21179a0d53610f90e9bc2a614980f70 |
| SANs: usefulapi.io, braintree.usefulapi.io, *.braintree.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 braintree.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 | 200 |
WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://braintree.usefulapi.io/.well-known/oauth-protected-resource/mcp", error="invalid_token", error_description="Missing or invalid access token"
Bearer realm="OAuth", resource_metadata="https://braintree.usefulapi.io/.well-known/oauth-protected-resource/mcp", error="invalid_token", error_description="Missing or invalid access token"Protected resource metadata
| Document | https://braintree.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://braintree.usefulapi.io/mcp |
| Authorisation server | https://braintree.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://braintree.usefulapi.io/mcp | Verified | 200 | |
| http (plaintext) | http://braintree.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 →
braintree_customer_payment_methods List a customer's payment methods ~99
List the vaulted payment methods (credit cards, PayPal accounts, etc.) for one customer, by GraphQL global Customer ID. Returns each method's id, legacyId, usage, created-at, and detail type. GraphQL `node { ... on Customer { paymentMethods } }`.
| Name | Type | Req | Description |
|---|---|---|---|
| first | integer | – | Max payment methods to return. Default 50. |
| id | string | yes | GraphQL global Customer ID (opaque). |
No output schema declared.
No examples provided.
braintree_find_customer Find a customer ~89
Fetch one customer by GraphQL global Customer ID via the `node` query. Returns id, legacyId, name, company, and created-at. To also enumerate stored cards/PayPal accounts use braintree_customer_payment_methods.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | GraphQL global Customer ID (opaque). Legacy numeric ids differ — resolve them via a transaction search or the id-conversion query first. |
No output schema declared.
No examples provided.
braintree_find_transaction Find a transaction ~92
Fetch one transaction by its GraphQL global ID (the opaque `id` returned by braintree_search_transactions, NOT the short legacy id). Uses the GraphQL `node` query. Returns amount, status, timestamps, order id, and the linked customer.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | GraphQL global transaction ID (opaque, base64-looking), e.g. from a search result's `node.id`. |
No output schema declared.
No examples provided.
braintree_list_subscriptions List a customer's subscription activity ~148
List a customer's recurring / subscription payment activity. IMPORTANT: Braintree's GraphQL API does NOT expose native Subscription objects (recurring-billing management is still legacy-API only — see braintree/graphql-api issue #1). This tool therefore returns the customer's transactions (the observable evidence of subscription charges) via a TransactionSearchInput scoped to the customer; inspect each node's status/amount/createdAt to trace recurring charges. For full subscription CRUD you must use Braintree's legacy server SDK / REST API.
| Name | Type | Req | Description |
|---|---|---|---|
| customerId | string | yes | GraphQL global Customer ID whose recurring/subscription charges to list. |
| first | integer | – | Max transactions to return. Default 50. |
No output schema declared.
No examples provided.
braintree_refund_transaction Refund a transaction ~125
DESTRUCTIVE. Refund a SETTLED (or settling) transaction, returning money to the customer. Use the GraphQL global transaction ID. Omit `amount` for a full refund, or pass a decimal string for a partial refund. GraphQL mutation `refundTransaction`. For transactions not yet settled, use braintree_void_transaction instead.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | string | – | Partial-refund amount as a decimal string (e.g. "10.00"). Omit for a full refund. |
| transactionId | string | yes | GraphQL global transaction ID to refund. |
No output schema declared.
No examples provided.
braintree_search_transactions Search transactions ~188
Search transactions by created-at date range, status, and/or customer. Builds a TransactionSearchInput (operators: status `in`, createdAt `greaterThanOrEqualTo`/`lessThanOrEqualTo`, customer.id `is`). Returns a page of transaction nodes (id, legacyId, amount, status, createdAt). GraphQL `search { transactions }`.
| Name | Type | Req | Description |
|---|---|---|---|
| createdAfter | string | – | Only transactions created at or after this ISO-8601 timestamp. |
| createdBefore | string | – | Only transactions created at or before this ISO-8601 timestamp. |
| customerId | string | – | GraphQL global Customer ID to filter to one customer's transactions. |
| first | integer | – | Max transactions to return (page size). Default 25. |
| status | array | – | One or more transaction statuses to match (e.g. ["SETTLED","VOIDED"]). |
No output schema declared.
No examples provided.
braintree_void_transaction Void a transaction ~82
DESTRUCTIVE. Void (cancel) a transaction that has NOT yet settled — e.g. an authorization or one submitted-for-settlement. Use the GraphQL global transaction ID. GraphQL mutation `voidTransaction`. For already-settled transactions use braintree_refund_transaction instead.
| Name | Type | Req | Description |
|---|---|---|---|
| transactionId | string | yes | GraphQL global transaction ID to void. |
No output schema declared.
No examples provided.
What is the io.usefulapi/braintree MCP server?
io.usefulapi/braintree is an MCP server listed in the public MCP registry as io.usefulapi/braintree. Search Braintree transactions, customers and payment methods, and refund or void charges. This page covers its hosted endpoint (https://braintree.usefulapi.io/mcp).
Is the io.usefulapi/braintree MCP server safe to use?
io.usefulapi/braintree scores 86 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 io.usefulapi/braintree MCP server expose?
io.usefulapi/braintree exposes 7 tools: braintree_find_transaction, braintree_search_transactions, braintree_find_customer, braintree_customer_payment_methods, braintree_list_subscriptions, and 2 more. Their descriptions and schemas cost roughly 823 tokens of context every time the server is loaded.
Does the io.usefulapi/braintree MCP server require authentication?
Yes. io.usefulapi/braintree 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 io.usefulapi/braintree MCP server still maintained?
io.usefulapi/braintree 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.