Debitura.MCP vs Solana MCP by Vybe
A side-by-side look at the Debitura.MCP and Solana MCP by Vybe MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Debitura.MCP for finance & fintech work over a hosted endpoint; choose Solana MCP by Vybe for finance & fintech over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Debitura.MCP when
- You need dedicated capabilities in the Finance & Fintech domain.
- You prefer a remote HTTP/SSE transport.
- You want tools like
ping, list_cases, get_case.
Choose Solana MCP by Vybe when
- You need dedicated capabilities in the Finance & Fintech domain.
- You prefer a remote HTTP/SSE transport.
- You want tools like
list-endpoints, get-endpoint, search-endpoints.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Finance & Fintech | Finance & Fintech |
| Quality signal | 59/100 · Good | 63/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Remote HTTP/SSE |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 2,136 |
| Directory activity | 1 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 16 | 7 |
| Full listing | View Debitura.MCP | View Solana MCP by Vybe |
Tools & capabilities
Debitura.MCP tools 16
pingVerify the connection to Debitura and show which creditor account the API key belongs to. Call this first to confirm the integration is set up correctly.list_casesList the creditor's debt collection cases with pagination, status filtering, and sorting. Returns compact case summaries: reference, debtor name + country, amounts, lifecycle, partner, key dates. Use get_case for full detail on a specific case. Lifecycle values (statuses filter and output): `PendingContractSigning` · `PendingVerificationInternal` · `PendingVerification` · `NeedsAdditionalDetails` · `Leads` · `LeadsQuoteGiven` · `Active` · `Paused` · `Closed` · `Merged` Sortable fields: `DateCreated` · `DateUpdated` · `DateFinished` · `DateCollectionStarted` · `DueDate` · `Date` · `GrossAmount` · `Remainder` · `InterestFees` · `CollectionFees` Sort format: `Field:asc` or `Field:desc`, e.g. `GrossAmount:desc` Note: results include the creditor's own test cases; the `isTestCase` flag on each case marks them.get_caseFetch one collection case in full detail. Look it up by Debitura case ID (GUID), by your own creditor reference (e.g. invoice number), or by the Debitura case reference shown in the portal. Provide exactly one of the three identifiers.get_case_activityFetch the chronological timeline of a case — what has happened so far: status changes, partner actions, communications, and payments. Returns an envelope `{ items, currentEngagementPhase }`: `items` is the chronological event list, and `currentEngagementPhase` is the case's current engagement phase ("Pre-legal", "Legal", or "Enforcement"; null when no active engagement exists).get_case_messagesRead the chat conversation on a case between you and the collection partner handling it. Each message includes: senderName, role (Creditor / Partner / Managed by partner), sentAt (UTC), message. See the debitura://glossary/chat-roles resource for what each role means.get_case_paymentsList every payment recorded on a case — money recovered so far.get_case_contract_statusCheck which contracts (e.g. debt collection agreement, power of attorney) are signed or still blocking a case, including signing URLs for any outstanding documents.preview_caseDry-run a collection case BEFORE creating it: returns eligibility, the assigned collection partner, pricing (success fee), and any contracts that would need signing. Nothing is persisted. ALWAYS call this before create_case and show the user the pricing and requirements.list_team_membersList the team members on the creditor's Debitura account. Use this to resolve a valid sender (userId or email) before calling send_case_message, or a case owner for create_case.list_case_filesList all documents attached to a case: file name, document type, description, upload date, and a time-limited SAS download URL. Each file also carries downloadUrlExpiresAt (UTC) — when the download URL stops working, so a cached URL can be refreshed in time. Use upload_case_file to attach new documents.get_account_summaryReturn a count of cases per lifecycle stage for the creditor's account. Useful for a quick portfolio overview without listing all cases. Stages: PendingContractSigning, PendingVerificationInternal, PendingVerification, NeedsAdditionalDetails, Leads, LeadsQuoteGiven, Active, Paused, Closed, Merged. Note: these counts include the creditor's own test cases; list_cases exposes the `isTestCase` flag that marks them.list_tasksList every open task (action-item) across your whole account — things the platform needs you to do before a case (or your account) can proceed: reply to a chat, sign a contract, assign a bank account, and so on. Use get_case_tasks instead to scope this to one case. Tasks auto-resolve once the underlying condition clears — e.g. replying to a case's chat makes its ReplyToChat task disappear on its own. Treat this as a live work queue, not a log: a task seen on one call may no longer be open on the next. Every task carries a solutionUrl — an absolute link a human can open to resolve it in one click, whatever the type. Some types (today: ReplyToChat, ClientInputRequired, MoreInfoNeeded) additionally carry a non-null `action` pointing at the exact API call that resolves them — for those, call send_case_message with the task's caseId instead of sending a human to solutionUrl. Tasks without an action rely on solutionUrl alone. Task types: Generic, ReplyToChat, SelectQuoteWinner, ReviewPartner, ClientInputRequired, SignContract, MoreInfoNeeded, AssignBankAccount, CaseValidationNeedsInfo.- +4 more on the listing page
Solana MCP by Vybe tools 7
list-endpointsLists all API paths and their HTTP methods with summaries, organized by path. Results can be passed directly into 'get-endpoint'.get-endpointGets detailed information about a specific API endpoint, including security schemes and serverssearch-endpointsPerforms a deep search through paths, operations, and parameters to discover relevant API endpoints. Use this tool to find specific API capabilities, required parameters, or data models based on search keywords. Results can be passed directly into 'get-endpoint'.query-vybe-apiRuns a read-only GET request against a documented /v4 path on the Vybe Solana API (see https://docs.vybenetwork.com) and returns live Solana data: token prices, holders, liquidity and candles; wallet balances, PnL, counterparties and DeFi positions; markets, trades, transfers, top traders and labeled accounts. Use list-endpoints or search-endpoints to find a path and get-endpoint to check its parameters first. This tool cannot create, modify, or delete anything.query-vybe-api-batchReads Solana wallet data for many addresses in one call from the Vybe Solana API (see https://docs.vybenetwork.com). These endpoints use a POST body only to carry the list of wallet addresses; they do not create, modify, or delete any data. Use query-vybe-api for single-wallet and all other reads.build-vybe-transactionBuilds an unsigned Solana transaction with the Vybe Solana API (see https://docs.vybenetwork.com) for a token swap, a token-account close, or an MEV withdrawal, and returns it as base64 for the user to review and sign in their own wallet. This tool never signs, submits, or broadcasts a transaction, never moves funds on its own, and never accepts private keys. Use query-vybe-api with /v4/trading/swap-quote first when the user only wants a price quote.pay-with-x402Before calling any Vybe endpoint without an API key (e.g. AI agent, throwaway script, premium-only path), use this to access the same endpoint via x402 pay-per-call USDC on Solana.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Debitura.MCP
{
"mcpServers": {
"debitura-debitura-mcp": {
"url": "https://mcp.debitura.com/mcp"
}
}
}
Solana MCP by Vybe
{
"mcpServers": {
"solana-mcp-by-vybe": {
"url": "https://mcp.vybenetwork.xyz/mcp"
}
}
}
Frequently asked questions
Debitura.MCP is categorized under Finance & Fintech and uses a remote HTTP/SSE transport. Solana MCP by Vybe belongs to Finance & Fintech and uses a remote HTTP/SSE transport. Pick Debitura.MCP for finance & fintech work and Solana MCP by Vybe for finance & fintech.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Debitura.MCP has no declared pricing — check the project's own site. Solana MCP by Vybe has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add debitura-debitura-mcp and solana-mcp-by-vybe as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Debitura.MCP has a quality signal of 59/100 (Good) with 1 views, 0 installs and 0 GitHub stars. Solana MCP by Vybe has 63/100 (Good) with 0 views, 0 installs and 2,136 GitHub stars.