1Forge Finance APIs MCP Configuration
The 1Forge Finance APIs MCP configuration provides a hosted JSON schema that connects AI assistants — including Claude Desktop, Cursor, Windsurf, and VS Code Copilot — to the 1Forge Finance APIs API via the Model Context Protocol. This configuration maps 2 API endpoints as callable tools, including Get quotes for all symbols, Get a list of symbols for which we provide real-time quotes. No authentication credentials are needed — it works out of the box. The configuration is auto-generated from the 1Forge Finance APIs OpenAPI specification (v0.0.1) and has a quality score of 28/99 (fair documentation coverage). Use the hosted URL below to auto-load this schema into any compatible MCP client.
Quick Specs Reference
Hosted Config URL
Use this hosted URL in any client that supports remote MCP schema auto-loading.
https://mcpbridge.org/config/1forge-com.jsonOne-Click Client Setup
Copy the configurations below to wire your local coding assistant directly.
Claude Desktop
claude_desktop_config.json{
"mcpServers": {
"1forge-com": {
"command": "npx",
"args": [
"-y",
"@mcp/1forge-com"
],
"env": {
"1FORGE_FINANCE_APIS_API_KEY": "your_1forge_finance_apis_api_key"
}
}
}
}Cursor & VS Code
MCP Server URL Setup{
"mcpServers": {
"1forge-com": {
"url": "https://mcpbridge.org/config/1forge-com.json"
}
}
}Raw Configuration JSON
For local command line wrappers or dynamic shell bindings.
{
"mcpServers": {
"1forge-com": {
"command": "npx",
"args": ["-y","@mcp/1forge-com"],
"env": {
"1FORGE_FINANCE_APIS_API_KEY": "your_1forge_finance_apis_api_key"
}
}
}
}Required Environment Keys
Substitute these secrets inside your configuration directory environment definitions.
1FORGE_FINANCE_APIS_API_KEYyour_1forge_finance_apis_api_key with your secret key credentialMapped Web APIs & Tools
The following routes will be exposed directly as protocol tools for the LLM.
/quotesGet quotes for all symbols
/symbolsGet a list of symbols for which we provide real-time quotes
Similar Configurations
Stripe API
Process payments, manage subscriptions, and handle billing. Let your AI agent interact with Stripe seamlessly.
https://mcpbridge.org/config/stripe.jsonStripe API
The Stripe API is a comprehensive, RESTful interface provided by Stripe, Inc. that enables developers to programmatically manage all aspects of an online payment ecosystem. Core capabilities span the entire transaction lifecycle, including accepting payments, managing subscriptions, handling disputes, processing payouts, and orchestrating complex multi-party financial workflows. The provided endpoints specifically target the Connect product, which allows platforms and marketplaces to manage connected accounts (sellers, service providers, or sub-merchants), their associated bank accounts, and account onboarding via account links. Typical enterprise use cases include building global marketplaces, gig economy platforms, SaaS with revenue sharing, and any system requiring automated, multi-stakeholder financial operations. Consumer applications might involve freelancer tools or peer-to-peer payment interfaces that leverage these account management functions. When exposed as tools to an AI coding assistant via the Model Context Protocol, this API transforms from a static documentation reference into a dynamic, actionable financial operations layer. The AI gains the ability to interact directly with a live Stripe environment, enabling it to understand the real-time state of connected accounts and programmatically initiate financial workflows. This provides immense value by bridging the gap between high-level, natural language instructions and precise, low-level API calls. An AI agent can serve as an intelligent intermediary that interprets a developer's intent—such as "onboard a new seller"—and translates it into the correct sequence of API calls to create an account, generate an onboarding link, and verify the resulting status, thereby accelerating development and reducing boilerplate code creation. In practice, a developer can instruct the AI to perform a variety of dynamic, context-aware tasks. For instance, the agent can be directed to "query the details and payout status of connected account 'acct_123'" using the GET /v1/accounts/{account} endpoint. It could also be instructed to "create and securely provision a new sub-merchant account for our vendor in Canada," which would involve a POST to /v1/accounts with appropriate parameters. Furthermore, the AI can manage financial relationships by executing a command like "link the external bank account ending in 4242 to the platform account for payouts," utilizing the POST /v1/accounts/{account}/bank_accounts endpoint. These examples demonstrate how the AI can automate complex account lifecycle management, from onboarding to payout configuration, based on natural language directives. Crucially, while the API interaction itself may be facilitated without a traditional user login in an MCP server context, proper authentication with Stripe is mandatory and security is paramount. Developers must secure their Stripe API keys (both secret and publishable) and never expose secret keys in client-side code or version control. The MCP server should be configured to use a secret key with permissions scoped strictly to the necessary operations, adhering to the principle of least privilege. If using OAuth for Connect, appropriate scopes must be assigned. All sensitive credentials should be injected via environment variables or a secure secrets manager. The server must enforce strict input validation on all parameters passed to the Stripe endpoints to prevent injection attacks and ensure data integrity, treating the AI's generated payloads with the same scrutiny as human-written code.
https://mcpbridge.org/config/stripe-com.jsonAdyen Account API
The Account API is a foundational RESTful service provided by Adyen for the comprehensive management of account-related entities within a classic marketplace or platform integration. It serves as the primary programmatic interface for orchestrating the lifecycle of accounts, account holders, and their associated legal and financial components on the Adyen payments platform. Its core capabilities encompass the creation, retrieval, and deletion of critical data structures, including the accounts themselves, account holder profiles, bank accounts, legal arrangements, shareholder records, and signatory details. Typical use cases are prevalent in enterprise-grade platform operations: onboarding new merchants or sellers by creating account holders and linking their bank accounts for payouts, performing due diligence by managing legal and shareholder information, generating necessary financial documents via tax form retrieval, and finally, executing the secure closure of accounts or account holder relationships when required. This API is the engine behind programmatic account management for businesses that have already established their Adyen platform integration. When exposed as a set of tools through the Model Context Protocol (MCP) for integration with AI coding assistants like Claude Desktop, Cursor, or Cline, this API unlocks significant value by transforming repetitive, multi-step account management workflows into intuitive, natural language-driven tasks. An AI agent can directly interact with the API's endpoints to perform complex queries and updates, acting as a highly efficient co-pilot for platform developers and operations teams. Instead of manually composing HTTP requests or navigating a separate dashboard, a developer can instruct the AI to perform actions conversationally. For example, the AI can be tasked to "generate a summary of all account holders created in the last 7 days and their current status" by leveraging the getAccountHolder endpoint, or it can "draft the payload needed to add a new shareholder to account holder AH_123 for compliance review." This integration shifts the developer's focus from low-level API mechanics to higher-level business logic and decision-making, dramatically accelerating development, debugging, and administrative processes. In practice, a developer can instruct an AI assistant to execute a wide range of dynamic tasks using this MCP server. The AI agent can query records to audit account setups, such as "list all bank accounts linked to account holder ID 456 to verify payout destinations." It can automate compliance updates by crafting requests to "remove a dormant signatory from legal arrangement LA_789" using the deleteSignatories endpoint, or facilitate data cleanup by "deleting all test bank accounts under account ACC_TEST." The agent can also assist in lifecycle management by preparing and executing the calls needed to "close the account for a terminated merchant" or "generate a tax form for account holder AH_001 for the fiscal year." These workflows empower developers to handle bulk operations, validate data integrity, and respond to operational events through simple instructions, with the AI managing the precise API calls and data structures behind the scenes. While the basic specification notes "None" for authentication, this is a critical implementation detail that requires careful attention for production security. Developers must treat this API with the utmost care, as it handles sensitive financial and identity data. The foundational security principle is implementing robust authentication and authorization, typically via Adyen's API keys or OAuth, ensuring each request is properly signed and originates from a trusted source. Adherence to the principle of least privilege is paramount; the API credentials used should have only the permissions absolutely necessary for the task at hand, whether that is read-only access for reporting or specific write permissions for creating accounts. When configuring an MCP server for an AI assistant, credentials must be managed securely outside of the codebase, using environment variables or a secrets manager, never embedded in client-side code. Developers should also ensure that any tool exposed to an AI is wrapped in validation logic to prevent malformed or malicious payloads, and that all actions are logged for audit trails, given the irreversible nature of operations like account closure.
https://mcpbridge.org/config/adyen-com-accountservice.jsonAdyen BinLookup API
The Adyen BinLookup API is a critical financial data service provided by Adyen, a leading global payment platform, designed to enable merchants and payment service providers to enhance transaction decisioning and optimize payment acceptance rates. At its core, this API allows developers to submit a payment card's Bank Identification Number (BIN)—the first six to eight digits of a card number—to retrieve essential metadata that is pivotal for payment processing and risk assessment. The two primary endpoints, GET3DSAvailability and GETCostEstimate, serve distinct yet complementary purposes. The former checks for 3D Secure 2.x compatibility, determining whether an issuer supports this fraud-prevention protocol and which authentication version is applicable. The latter provides a real-time cost estimate for processing a transaction, factoring in the card's country, brand, and issuing bank to calculate interchange fees and scheme costs. Typical use cases are widespread in enterprise e-commerce and subscription billing platforms, where dynamically routing payments, pre-qualifying transactions for specific authentication methods, and providing upfront cost transparency to consumers can significantly reduce cart abandonment and optimize profitability. When exposed as toolsets through a Model Context Protocol (MCP) server for AI coding assistants like Claude Desktop or Cursor, the Adyen BinLookup API transforms from a static data endpoint into an intelligent, context-aware resource for development and operational tasks. The primary value lies in enabling the AI to programmatically and dynamically access live payment infrastructure data, removing the need for developers to manually look up BIN information or hard-code static card data. This allows an AI assistant to become an active participant in building and debugging payment flows. For instance, an AI can validate the integration of payment forms in real-time, cross-reference card details with Adyen's database to verify they are test or live BINs, and simulate how different card types would be processed before a transaction is ever submitted. It effectively bridges the gap between code and the complex, real-world rules of the payment ecosystem, fostering smarter, data-driven development workflows. Practical workflow examples illustrate how a developer can instruct an AI agent to perform sophisticated tasks using this MCP-connected API. A developer could command the AI to "Scan this new checkout form, extract all visible BIN prefixes, and use Adyen's tools to generate a report showing which ones support 3D Secure and their estimated processing cost." The AI would then query the endpoints and produce a detailed analysis. In a debugging scenario, one might instruct: "This EU-based user's transaction failed authentication; use the BIN 4000000000000000 to check 3D Secure availability and get a cost estimate for a card issued in Germany." The AI would execute the lookups, returning actionable data that points to whether the issue was an authentication problem or a routing miscalculation. Furthermore, for building dashboards or internal tools, a developer can direct the AI to "Create a script that uses the BIN lookup to fetch and cache cost estimates for the top 100 card BINs we encounter, updating the cache daily." This automates a previously manual data-aggregation task. Critical security and configuration guidelines are paramount when deploying this API, especially within an MCP context. Although the system prompt indicates "None" for authentication, the official Adyen documentation specifies that all calls require authentication via an API credential, typically using a merchant account-specific API key or a combination of a username and password, passed via HTTP Basic Authentication. Best practices must be strictly followed: first, adhere to the principle of least privilege by generating a dedicated API user with permissions restricted solely to the BinLookup service, avoiding use of a primary or high-privilege account key. Second, all communication must occur over TLS 1.2+ encryption. Third, the API key or credentials must be stored securely, never exposed in client-side code or public repositories, and injected into the environment of the MCP server or AI assistant runtime via secure secrets management. When configuring the MCP server, ensure it acts as a secure proxy, handling authentication internally and not exposing raw credentials to the AI model. Developers should also implement rate limiting and error handling in their integration to manage quota and gracefully handle API response variations.
https://mcpbridge.org/config/adyen-com-binlookupservice.json