Which countries are supported by the Fintoc MCP server?

Fintoc currently supports major financial institutions in Chile (cl) and Mexico (mx). You can use the 'list_institutions' tool to see the specific banks available in each region.

Can I filter bank movements by specific dates using the agent?

Yes! The 'list_movements' tool accepts 'since' and 'until' parameters in ISO format. For example, you can ask the agent to 'List movements from 2023-01-01 to 2023-01-31' for a specific account.

How secure is my bank data when using Fintoc through Vinkius?

Your security is paramount. Vinkius encrypts your Fintoc Secret Key at rest and only injects it into the isolated execution environment. Fintoc uses read-only access for movements and bank-grade security for all operations.

Fintoc MCP Server for CrewAI 12 tools — connect in under 2 minutes

Name: Fintoc
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 12 Tools Framework

Connect your CrewAI agents to Fintoc through Vinkius, pass the Edge URL in the `mcps` parameter and every Fintoc tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

python

from crewai import Agent, Task, Crew

agent = Agent(
    role="Fintoc Specialist",
    goal="Help users interact with Fintoc effectively",
    backstory=(
        "You are an expert at leveraging Fintoc tools "
        "for automation and data analysis."
    ),
    # Your Vinkius token. get it at cloud.vinkius.com
    mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)

task = Task(
    description=(
        "Explore all available tools in Fintoc "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 12 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About Fintoc MCP Server

Connect your Fintoc account to any AI agent and automate your open banking and payment operations through the Model Context Protocol (MCP). Fintoc is the leading API for financial integration in Latin America (Chile and Mexico), allowing you to securely access real-time bank data and programmatically initiate transfers.

When paired with CrewAI, Fintoc becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Fintoc tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.

What you can do

Bank Connectivity — List and manage your active bank links to maintain persistent access to financial data.
Account Inspections — Fetch detailed information for all linked bank accounts, including available balances and holder details.
Movement History — Retrieve transaction history (movements) for any account with powerful filtering options by date.
Payment Initiation — Create and monitor payment intents to automate bank transfers directly through the agent.
Subscription Tracking — List and manage active subscriptions to keep track of recurring payments.
Institution Discovery — Discover supported banks and financial institutions across different countries (Chile and Mexico).
Real-time Monitoring — Fetch specific movement details or payment intent statuses to keep your financial operations in sync.

The Fintoc MCP Server exposes 12 tools through the Vinkius. Connect it to CrewAI in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Fintoc to CrewAI via MCP

Follow these steps to integrate the Fintoc MCP Server with CrewAI.

Install CrewAI

Run pip install crewai

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com

Customize the agent

Adjust the role, goal, and backstory to fit your use case

Run the crew

Run python crew.py. CrewAI auto-discovers 12 tools from Fintoc

Why Use CrewAI with the Fintoc MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with Fintoc through the Model Context Protocol.

Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools

CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the `mcps` parameter and agents auto-discover every available tool at runtime

Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls

Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

Fintoc + CrewAI Use Cases

Practical scenarios where CrewAI combined with the Fintoc MCP Server delivers measurable value.

Automated multi-step research: a reconnaissance agent queries Fintoc for raw data, then a second analyst agent cross-references findings and flags anomalies. all without human handoff

Scheduled intelligence reports: set up a crew that periodically queries Fintoc, analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain Fintoc tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow

Compliance and audit automation: a compliance agent queries Fintoc against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

Fintoc MCP Tools for CrewAI (12)

These 12 tools become available when you connect Fintoc to CrewAI via MCP:

create_payment_intent

Create a payment intent

get_account

Get account details

get_link

Get link details

get_movement

Get movement details

get_payment_intent

Get payment intent details

get_subscription

Get subscription details

list_accounts

List accounts for a link

list_institutions

List supported institutions

list_links

List all links

list_movements

List movements for an account

list_payment_intents

List payment intents

list_subscriptions

List subscriptions

Example Prompts for Fintoc in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with Fintoc immediately.

"List all my bank accounts linked to Fintoc."

"Show me the last 5 transactions for account 'acc_9876'."

"Which banks are supported in Chile (cl)?"

Troubleshooting Fintoc MCP Server with CrewAI

Common issues when connecting Fintoc to CrewAI through the Vinkius, and how to resolve them.

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.

Rate limiting or 429 errors

Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

Fintoc + CrewAI FAQ

Common questions about integrating Fintoc MCP Server with CrewAI.

How does CrewAI discover and connect to MCP tools?

CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.

Can different agents in the same crew use different MCP servers?

Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.

What happens when an MCP tool call fails during a crew run?

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.

Can CrewAI agents call multiple MCP tools in parallel?

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.

Can I run CrewAI crews on a schedule (cron)?

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.