Bring African Payments
to LangChain
Learn how to connect Tingg Insights to LangChain and start using 12 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the Tingg Insights MCP Server?
Connect your Tingg (Cellulant) payments account to any AI agent and simplify how you collect payments, manage disbursements, and track financial settlements across Africa through natural conversation.
What you can do
- Transaction Oversight — List and search all payment transactions and retrieve real-time status for specific checkout requests.
- Disbursement Control — Initiate and monitor payouts (B2C/B2B) to recipients across supported mobile money and bank channels.
- Settlement Tracking — List bank settlements to monitor when funds are moved from your Tingg account to your local bank.
- Payment Initiation — Programmatically create new checkout requests to collect payments via mobile money, card, or bank.
- Engagement Automation — Send transactional SMS or Email notifications to users via the Tingg Engage service.
- Performance Metrics — Retrieve high-level account metrics and payment success rates to monitor your business health.
How it works
1. Subscribe to this server
2. Enter your Tingg Client ID and Client Secret (found in your merchant portal)
3. Start managing your African payment ecosystem from Claude, Cursor, or any MCP client
Who is this for?
- Finance & Operations Managers — quickly check transaction statuses and verify bank settlements via simple AI commands.
- E-commerce & Business Owners — monitor payout progress and retrieve account performance metrics directly from the workspace.
- Product Teams — automate payment requests and trigger user notifications via the AI assistant.
Built-in capabilities (12)
Verify Tingg API connectivity
Initiate a new payment request
Retrieve performance stats
Check status of a payout
Check status of a specific transaction
Request a refund
Send money to a recipient
List bank settlements
List active webhooks
List all payouts/disbursements
List recent payment transactions
Send SMS or Email alert
Why LangChain?
LangChain's ecosystem of 500+ components combines seamlessly with Tingg Insights through native MCP adapters. Connect 12 tools via Vinkius and use ReAct agents, Plan-and-Execute strategies, or custom agent architectures. with LangSmith tracing giving full visibility into every tool call, latency, and token cost.
- —
The largest ecosystem of integrations, chains, and agents. combine Tingg Insights MCP tools with 500+ LangChain components
- —
Agent architecture supports ReAct, Plan-and-Execute, and custom strategies with full MCP tool access at every step
- —
LangSmith tracing gives you complete visibility into tool calls, latencies, and token usage for production debugging
- —
Memory and conversation persistence let agents maintain context across Tingg Insights queries for multi-turn workflows
Tingg Insights in LangChain
Tingg Insights and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Tingg Insights to LangChain through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 3,400+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Tingg Insights in LangChain
The Tingg Insights 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. All 12 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in LangChain only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.

* 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
How Vinkius secures
Tingg Insights for LangChain
Every tool call from LangChain to the Tingg Insights MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I check the status of a specific payment request via AI?
Yes! Use the get_transaction_status tool and provide the Checkout Request ID. Your agent will retrieve the real-time payment status from Tingg.
How do I see my latest bank settlements?
Run the list_account_settlements query. The agent will retrieve a list of all funds that have been settled from your Tingg account to your linked bank account.
Is it possible to send money to a recipient (payout) via AI?
Absolutely. Use the initiate_payout_request action. Provide the payout details including amount, currency, and recipient info in the JSON payload to start the disbursement.
How does LangChain connect to MCP servers?
Use langchain-mcp-adapters to create an MCP client. LangChain discovers all tools and wraps them as native LangChain tools compatible with any agent type.
Which LangChain agent types work with MCP?
All agent types including ReAct, OpenAI Functions, and custom agents work with MCP tools. The tools appear as standard LangChain tools after the adapter wraps them.
Can I trace MCP tool calls in LangSmith?
Yes. All MCP tool invocations appear as traced steps in LangSmith, showing input parameters, response payloads, latency, and token usage.
MultiServerMCPClient not found
Install: pip install langchain-mcp-adapters
