Braintree MCP by usefulapi
REMOTE · BRAINTREE.USEFULAPI.IO
Search Braintree transactions, customers and payment methods, and refund or void charges.
Available components
Last scanned (1 hour ago)
Scores higher than 4% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Finance and Payments
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 yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- 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
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 Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 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.
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.
- 2 Nov 26 −61
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: pass → unverified ▼ security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 31 Oct 26 +2
- Authorization: partial → pass ▲ security
- MCP protocol: fail → pass ▲ functional
- New prompt “check_a_customer_s_saved_payment_methods” functional
- New prompt “find_failed_or_unsettled_payments_in_a_date_range” functional
- New prompt “look_into_one_transaction_and_its_customer” functional
- New prompt “refund_or_void_a_transaction” functional
- New prompt “trace_a_customer_s_recurring_charges” functional
- MCP protocol version: 2025-06-18 → 2025-11-25 functional
- Server version: 1.31.0 → 1.33.0 functional
- Server version: 1.30.0 → 1.31.0 functional
- Server version: 1.29.2 → 1.30.0 functional
- 30 Oct 26 0
- Server version: 1.29.1 → 1.29.2 functional
- Server version: 1.29.0 → 1.29.1 functional
- 29 Oct 26 0
- Server version: 1.28.0 → 1.29.0 functional
- Server version: 1.27.0 → 1.28.0 functional
- 28 Oct 26 0
- Server version: 1.25.0 → 1.27.0 functional
- 27 Oct 26 0
- Server version: 1.24.0 → 1.25.0 functional
- 25 Oct 26 0
- Server version: 1.23.0 → 1.24.0 functional
- Server version: 1.22.0 → 1.23.0 functional
- Server version: 1.21.3 → 1.22.0 functional
- Server version: 1.21.0 → 1.21.3 functional
- 24 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Server version: 1.20.0 → 1.21.0 functional
- Server version: 1.19.0 → 1.20.0 functional
- Server version: 1.17.0 → 1.19.0 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 5 Nov 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 | 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 braintree.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 38690 | 8 | Verified |
| usefulapi.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 302 |
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 | Redirected | 302 | https://usefulapi.io/braintree/ |
| http (plaintext) | http://braintree.usefulapi.io/mcp | Inconclusive | 302 | http://braintree.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 →
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.
How do I install the Braintree MCP by usefulapi server?
Braintree MCP by usefulapi 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'
What is the Braintree MCP by usefulapi server?
Braintree MCP by usefulapi is 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 Braintree MCP by usefulapi server safe to use?
Braintree MCP by usefulapi scores 18 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 Braintree MCP by usefulapi server expose?
Braintree MCP by usefulapi 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 Braintree MCP by usefulapi server require authentication?
Its publisher declares no required credentials for Braintree MCP by usefulapi. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the Braintree MCP by usefulapi server still maintained?
Braintree MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.