Braintree MCP by usefulapi
io.usefulapi/braintreeusefulapi.iostreamable-httpv1.40.4Scanned
Search Braintree transactions, customers and payment methods, and refund or void charges.
7 tools: 2 can delete or cancel things and 5 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- No findings
The remote endpoint did not answer the last look. Remote posture
Anlyon alternative
2 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 Braintree MCP by usefulapi can do
The Braintree MCP by usefulapi is published by usefulapi.io, a domain the MCP Registry verified. It has 7 tools. It can delete or cancel things (2 tools: braintree_refund_transaction and braintree_void_transaction). 5 tools only read.
None of its tools reads private data, brings in text other people write, or sends data out.
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Last scanned Oct 25, 2026, version 1.40.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.
7 tools
Deletes or cancels 2Claude Code: deny
braintree_refund_transactionDESTRUCTIVE.No findings
Why it is in this group
- The name "braintree_refund_transaction" says "refund": a word that usually means money moves, which cannot be taken back.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it 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.
Annotations the server declares
- title: Refund a transaction
- destructiveHint: true
braintree_void_transactionDESTRUCTIVE.No findings
Why it is in this group
- The name "braintree_void_transaction" says "void": a word for removing or ending something.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it 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.
Annotations the server declares
- title: Void a transaction
- destructiveHint: true
Only reads 5Show 5 read-only tools
braintree_customer_payment_methodsList the vaulted payment methods (credit cards, PayPal accounts, etc.) for one customer, by GraphQL global Customer ID.No findings
Why it is in this group
- The description's first verb is "list": a word for reading.
Description, as the server wrote it 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 } }`.
Annotations the server declares
- title: List a customer's payment methods
- readOnlyHint: true
braintree_find_customerFetch one customer by GraphQL global Customer ID via the `node` query.No findings
Why it is in this group
- The name "braintree_find_customer" says "find": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Find a customer
- readOnlyHint: true
braintree_find_transactionFetch one transaction by its GraphQL global ID (the opaque `id` returned by braintree_search_transactions, NOT the short legacy id).No findings
Why it is in this group
- The name "braintree_find_transaction" says "find": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Find a transaction
- readOnlyHint: true
braintree_list_subscriptionsList a customer's recurring / subscription payment activity.No findings
Why it is in this group
- The name "braintree_list_subscriptions" says "list": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: List a customer's subscription activity
- readOnlyHint: true
braintree_search_transactionsSearch transactions by created-at date range, status, and/or customer.No findings
Why it is in this group
- The name "braintree_search_transactions" says "search": a word for reading.
Description, as the server wrote it 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 }`.
Annotations the server declares
- title: Search transactions
- readOnlyHint: 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 private-data or untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- 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:33 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: 2 to 0
- Protocol version: 2025-06-18 to none
- RFC 9728 protected resource metadata: https://braintree.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
- Authorization servers: https://braintree.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: 2 to 0
- Protocol version: 2025-06-18 to none
- RFC 9728 protected resource metadata: https://braintree.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
- Authorization servers: https://braintree.usefulapi.io to none
- Dynamic client registration: yes to not observed
- Client ID metadata documents: no to not observed
Install
Pinned to version 1.40.4. Values in angle brackets are yours to fill in.
claude mcp add --transport http braintree https://braintree.usefulapi.io/mcpclaude mcp add --transport http braintree https://braintree.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__braintree__braintree_find_transaction",
"mcp__braintree__braintree_search_transactions",
"mcp__braintree__braintree_find_customer",
"mcp__braintree__braintree_customer_payment_methods",
"mcp__braintree__braintree_list_subscriptions"
],
"ask": [],
"deny": [
"mcp__braintree__braintree_refund_transaction",
"mcp__braintree__braintree_void_transaction"
]
}
}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 braintree. Review it before you use it.
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/braintree/verify?hash=012905fe749177c0f8b02fc0dabdae6c3e5bf9cdf32c7f10f3b00cda92eacec5" | jq -e '.changed == false'Pinned hash 012905fe7491, from Oct 25, 2026, 23:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.usefulapi/braintree/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.usefulapi/braintree)Source: MCP Registry · repository. Synced Nov 18, 2026, 11:18 UTC.
Braintree MCP by usefulapi: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Braintree MCP by usefulapi safe?
- No scan can promise that. What its definitions show: 7 tools, 2 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 Braintree MCP by usefulapi delete data?
- Yes. 2 tools can delete, cancel or revoke something: braintree_refund_transaction and braintree_void_transaction.
Can the Braintree 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 Braintree MCP by usefulapi have?
- 7 tools: 2 destructive, 5 read. braintree_refund_transaction, braintree_void_transaction, braintree_find_transaction, braintree_search_transactions, braintree_find_customer, braintree_customer_payment_methods and braintree_list_subscriptions.
Does the Braintree MCP by usefulapi need sign-in or OAuth?
- Its remote endpoint did not answer the last anonymous look.
Does the Braintree 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 Braintree MCP by usefulapi changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Oct 25, 2026.