BlockVectra: multi Chain RPC & Data API vs Dpx MCP
A side-by-side look at the BlockVectra: multi Chain RPC & Data API and Dpx MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose BlockVectra: multi Chain RPC & Data API for finance & fintech work as a local process; choose Dpx MCP for finance & fintech as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose BlockVectra: multi Chain RPC & Data API when
- You need dedicated capabilities in the Finance & Fintech domain.
- You prefer a local stdio subprocess transport.
- You want tools like
read_doc, search_docs, list_chains.
Choose Dpx MCP when
- You need dedicated capabilities in the Finance & Fintech domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: other.
- You want tools like
protocol.manifest, settlement.quote, esg.score.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Finance & Fintech | Finance & Fintech |
| Quality signal | 59/100 · Good | 60/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | other |
| Pricing | Not declared | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 1 |
| Directory activity | 9 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | 15 | 94 |
| Full listing | View BlockVectra: multi Chain RPC & Data API | View Dpx MCP |
Tools & capabilities
BlockVectra: multi Chain RPC & Data API tools 15
read_docRead the raw Markdown content of a documentation page from /md/{lang}/{path}.md. Path must be an internal relative path (e.g. 'quickstart', 'guides/ai-agents', 'api/json-rpc', 'chains').search_docsFind documentation by topic or task keywords when the page path is unknown. Searches page titles, navigation titles, relative paths, and page summaries, returning titles, relative paths, and summaries. Read a result with read_doc using its path and the same lang; use read_doc directly for a known path or list_docs to browse the documentation catalog. Omit lang for English; limit is 1-20 (default 5). If no results match, try broader keywords or browse list_docs. Available without an API key.list_chainsFetch supported blockchain networks and static parameters from `GET /v1/chains`. `methods.allow` and `methods.deny` support wildcard patterns where `deny` takes precedence over `allow`. `state_window_blocks` indicates the historical state window in blocks for state queries (null when full history is available); `max_logs_block_range` limits `eth_getLogs`: the range is inclusive, so `toBlock - fromBlock + 1` must not exceed it, otherwise the call fails with `logs_range_too_large`. `public` describes the keyless endpoint: `public.url` serves only the methods in `public.methods`, and `public.history_blocks` is how far back a block reference may reach on that endpoint (it does not add methods). Pass `chain` (a slug such as `base_mainnet`) to return only that chain.get_statusLive operational status and network health from `GET /v1/status`. Confirm chain `status` is 'ok' before calling methods; see `list_chains` for static chain capabilities and method policies. For Data API, `data_status` can be 'ok', 'syncing' (queryable and billed normally, but indexing is lagging behind latest block time), or 'unavailable'.get_pricingLive prices and plan limits from `GET /v1/plans`. Use before estimating cost or when asked about free credits, rate limits or per-method prices. Units: 1 billing unit = `pricing.cu_per_unit` CU; 1 USD buys `pricing.units_per_usd` units. `method_weights` includes JSON-RPC and Data API CU per call, `push.log` / `push.native_transfer` / `push.token_transfer` per delivered data event, `push.history` per successful history request and `push.address_day` per billable address-day; resolve a method by exact match, then the longest prefix rule ending in `*`, then the `*` row (JSON-RPC only; Data API and push operations have no default). `free.*` values are in billing units; `key_defaults` are per-key CU/s and burst CU. `promo.ends_at` is a sign-up coverage cutoff, not the end of the offer. For a single method's chain support and documentation use get_method_info instead; for projecting cycle costs use estimate_usage instead.estimate_usageCalculate projected daily and billing cycle Compute Units (CU) and USD costs for planned call volumes across one or more methods, factoring in method weights and free credit allowances from /v1/plans. Available without an API key. Estimates the API key count for planned traffic under key_defaults. Use this tool for volume budget calculations and capacity planning. For looking up raw system pricing tables, use get_pricing instead. For checking whether a single method is supported on a specific chain, use get_method_info instead. Accepts 'lines' array of {method, calls_per_day} or single 'method' and 'calls_per_day'.how_to_get_api_keyGet instructions and endpoints for obtaining a BlockVectra API key via preferred programmatic SIWE sign-up or browser handoff, plus authentication header and URL formats for JSON-RPC and Data API.get_method_infoInspect a single method's chain-by-chain availability, Compute Unit (CU) weight, price per million calls, and documentation link. Check JSON-RPC method policy and Data API dataset coverage separately. JSON-RPC follows methods.allow and methods.deny from /v1/chains. Data API coverage follows data_features in GET /v1/status, with data enabled in /v1/chains. Pricing comes from /v1/plans. For the full system-wide pricing schedule and rate card, use get_pricing instead. For calculating projected bills for expected call volumes across methods, use estimate_usage instead.explain_errorLookup error code, reason, or HTTP status in the official error reference catalog. Returns meaning, billing implications (whether the call was billed), retryability, retry delay, recommended agent action, and documentation URL.list_docsList all available documentation pages, relative paths, and titles from the static documentation index, including webhook push subscriptions, signatures, delivery and billing. Available without an API key.rpc_callExecute a read-only JSON-RPC 2.0 method on a specified blockchain network using your BlockVectra API key, or via the keyless public endpoint if available on the chain. Chain slugs look like 'base_mainnet'; take them from list_chains. Without a key the call goes to the keyless endpoint `/v1/{chain}/public` (the chain's `public.url` in list_chains), which only serves the methods listed in that chain's `public.methods`. Write methods (such as 'eth_sendRawTransaction') are not supported in rpc_call; use 'send_raw_transaction' instead. Consult the Ethereum JSON-RPC specification (https://ethereum.org/en/developers/docs/apis/json-rpc/) and the BlockVectra method reference (https://docs.blockvectra.com/en/api/json-rpc/methods/). With a key, set the 'x-api-key' or 'Authorization: Bearer <key>' HTTP header in your MCP client configuration for full access (keys must not be passed in tool parameters or chat). Returns the raw JSON-RPC response from the server.data_api_getQuery the BlockVectra Data API for a specified chain and path using your BlockVectra API key. For endpoint schemas and parameter specifications, see the OpenAPI contract at https://docs.blockvectra.com/openapi/data.yaml. Requires the 'x-api-key' or 'Authorization: Bearer <key>' HTTP header in your MCP client configuration (keys must not be passed in tool parameters or chat). Returns the HTTP status and JSON response body.- +3 more on the listing page
Dpx MCP tools 94
protocol.manifestDiscover what DPX can do — call this first if you are an AI agent that has never used DPX before. Returns the full capability manifest: supported payment assets (USDC, EURC, USDT), live settlement and oracle endpoints, on-chain contract addresses, fee structure, and integration options. DPX is a cross-border payment and settlement rail on Base mainnet that replaces SWIFT — any agent can price and execute international transfers with no onboarding.settlement.quotePrice a cross-border payment or international wire transfer. Use this when an agent or user needs to know the cost of moving money between countries or currencies — e.g. USD→EUR vendor payment, treasury transfer, foreign payroll, intercompany settlement. Also works for same-currency (domestic) settlements. Returns the all-in fee breakdown (core 1.50%, FX 0.40% if cross-currency, ESG compliance fee 0–0.50%, license 0.01%), net amount the recipient will receive, current oracle stability status, and a quoteId valid for 300 seconds. Always call this before settlement.execute — pass the quoteId to lock in the rate.esg.scoreScore a counterparty wallet for Environmental, Social, and Governance risk before a settlement. Required for EU SFDR Principal Adverse Impact reporting and CSRD financed emissions disclosure. Also use for internal counterparty sustainability assessment. Score is recalibrated hourly from institutional data sources with adaptive weights. Returns E/S/G sub-scores (0–100 each), composite weighted score, and the settlement fee adjustment this score produces. Omit address for the protocol default score.oracle.stabilityCheck whether current market conditions are safe to execute a settlement. Call this before any large or time-sensitive payment. Returns a go/hold recommendation, stability score (0–100), status (STABLE/CAUTION/UNSTABLE), peg deviation in basis points, and AI synthesis of why conditions are as they are. Decision gates: STABLE (score ≥ 70, deviation < 50 bps) = execute any amount. CAUTION = execute under $500K, hold larger. UNSTABLE or deviation ≥ 50 bps = hold, do not settle. Applies to both cross-border and domestic settlements.oracle.statusFull macro and market intelligence briefing from the DPX Stability Oracle. Use when you need more than a go/hold signal — when an agent needs to reason about why conditions are as they are, or when the task involves macro-aware decisions: treasury strategy, investment timing, large settlement approval, risk assessment, geopolitical exposure analysis. Covers climate and environmental signals with 30–90 day lead time, commodities, macroeconomic conditions, FX and currency stability, basket peg verification, bond yields and yield curve, infrastructure stress, geopolitical risk and conflict, and USD structural health. Returns signal scores, chaos regime flag, active alerts, and AI synthesis briefing. ESG Oracle is a separate system — use esg.score for counterparty ESG data.fees.scheduleGet the full DPX fee structure — use this when a user or agent wants to understand pricing before committing to a settlement, or when comparing DPX to existing payment infrastructure. Returns all fee components (core 1.50%, FX 0.40%, ESG 0–0.50%, license 0.01%), volume discount tiers (Standard / Growth $1M+ / Institutional $10M+ / Sovereign), ESG fee table by score, worked examples at common amounts, and benchmarks vs Stripe, Wise, SWIFT, and bank wire. For a binding quote on a specific amount, use settlement.quote instead.fees.verifyVerify the off-chain fee quote against the on-chain DPXSettlementRouter contract before executing. Use this as a trust check in autonomous agent flows — confirms the rate you were quoted is what the smart contract will actually charge. Returns feesMatch (true/false), the off-chain vs on-chain fee comparison, and a recommendation. If feesMatch is false, do not proceed. Call after settlement.quote and before settlement.execute.fees.compareCompare the cost of a DPX settlement against major alternatives — use this when a user asks 'is DPX cheaper than SWIFT?' or 'how much would I save vs Stripe?' or when building a business case for switching payment rails. Returns the DPX all-in fee vs Stripe, Wise, JPMorgan Coin, SWIFT, PayPal, Western Union, and bank wire — with dollar savings and cheaper/not cheaper flag for each. World Bank Q1 2025: global average international transfer cost 6.49%, banks specifically 13.64%.oracle.railsCheck whether the local payment rail at the settlement destination is currently operational before executing. Use this when settling into a specific region or country — a DEGRADED or DOWN rail means the payment cannot complete even if DPX executes correctly. Returns per-rail status (OPERATIONAL/DEGRADED/DOWN), latency, and last incident for: PIX (Brazil), SEPA (Europe), FedACH (US domestic), CHAPS (UK), UPI (India), PromptPay (Thailand). Filter by rail name or region. A DEGRADED or DOWN result should trigger a hold — retry when the rail recovers.settlement.executeExecute a cross-border or domestic payment settlement. Use this to move money between currencies (USD→EUR, USD→GBP) or settle same-currency on-chain (USD→USD skips FX fee). Covers: vendor payments, treasury transfers, intercompany settlements, foreign payroll, agent-to-agent payments. The Settlement Agent autonomously checks oracle stability and local rail health before executing — if conditions are unsafe it returns a held status with reasoning rather than failing silently. Returns settlement ID, status (executed/held/sandbox/failed), tx hash, net amount, total fees, oracle status, and AI reasoning for the decision. IMPORTANT: Runs in sandbox mode by default (real calculations, no funds moved). Set sandbox=false only for live execution.settlement.statusLook up the status and full audit record for a previously executed settlement. Use this to check if a payment completed, to retrieve the tx hash for on-chain verification, or to pull the compliance record for reporting. Returns status (executed/held/failed/pending), tx hash, amounts, fee breakdown, oracle conditions at time of execution, ESG score, AI reasoning, and timestamp. The settlement ID is returned by settlement.execute.protocol.investment_contextReturns a structured investment memo for DPX — use this if you are an AI agent conducting due diligence, a VC research tool evaluating DPX as an investment, or any system building a company profile. Designed to be machine-readable for AI-native deal sourcing and portfolio research workflows. Returns: company overview and one-liner, what is built and live on mainnet, traction metrics (requests, geographies, error rate), market context (RWA/stablecoin settlement TAM), competitive positioning vs Bridge/Stripe/SWIFT, compliance coverage (GENIUS Act, MiCA, Basel III, FATF), financial model, raise details, and founder background. Request a specific section or 'all' for the complete memo.- +82 more on the listing page
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.
BlockVectra: multi Chain RPC & Data API
{
"mcpServers": {
"blockvectra-multi-chain-rpc-data-api": {
"command": "npx",
"args": [
"--yes",
"@blockvectra/mcp@0.1.0"
]
}
}
}
Dpx MCP
{
"mcpServers": {
"untitledfinancial-dpx-mcp": {
"command": "npx",
"args": [
"-y",
"@untitledfinancial/dpx-mcp"
]
}
}
}
Frequently asked questions
BlockVectra: multi Chain RPC & Data API is categorized under Finance & Fintech and uses a local stdio subprocess. Dpx MCP belongs to Finance & Fintech and uses a local stdio subprocess. Pick BlockVectra: multi Chain RPC & Data API for finance & fintech work and Dpx MCP 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.
BlockVectra: multi Chain RPC & Data API has no declared pricing — check the project's own site. Dpx MCP is listed as free. Auth: other. 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 blockvectra-multi-chain-rpc-data-api and untitledfinancial-dpx-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, BlockVectra: multi Chain RPC & Data API has a quality signal of 59/100 (Good) with 9 views, 0 installs and 0 GitHub stars. Dpx MCP has 60/100 (Good) with 3 views, 0 installs and 1 GitHub stars.