Novai MCP Server vs Mastercard Developers MCP
A side-by-side look at the Novai MCP Server and Mastercard Developers MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Novai MCP Server for finance & fintech work as a local process; choose Mastercard Developers 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 Novai MCP Server when
- You need dedicated capabilities in the Finance & Fintech domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You have the keys it needs:
NOVAI_RPC_URL. - You want tools like
novai_get_chain_status, novai_get_block, novai_get_transaction.
Choose Mastercard Developers MCP when
- You need dedicated capabilities in the Finance & Fintech domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
get-services-list, get-documentation, get-documentation-section-content.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Finance & Fintech | Finance & Fintech |
| Quality signal | 60/100 · Good | 67/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | No auth required | No auth required |
| Pricing | Free | Free |
| Required env vars | NOVAI_RPC_URL | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1 | 55 |
| Directory activity | 5 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 12 | 9 |
| Full listing | View Novai MCP Server | View Mastercard Developers MCP |
Tools & capabilities
Novai MCP Server tools 12
novai_get_chain_statusReturn the latest committed block of the live NOVAI chain: its height, block hash, round, transaction count, state root, and parent hash. Use this to verify the chain is live and advancing, and to learn the current tip height before requesting a specific block. Takes no parameters.novai_get_blockFetch a single committed block by height or by hash. Provide exactly one of height or hash. Returns the block height, block hash, parent hash, round, state root, and transaction count, or null if no such block is known. Note: the endpoint retains a bounded recent window of blocks by height, so very old heights can return null even though they were valid blocks. Lookups by hash work for any block the node still indexes.novai_get_transactionFetch a confirmed transaction by its transaction id. Returns the block height, transaction index, sender address, nonce, fee, and payload length, or null if the transaction is not found.novai_get_ai_entityFetch an on-chain AI entity (agent) by its entity id. Returns the entity record including code hash, creator, autonomy mode, capability bits, economic and stake balances, reputation score, transaction count, and activity timestamps, or null if no entity exists for that id.novai_get_balanceFetch the balance and nonce for an account or entity address. The balance is returned as a decimal string to preserve full precision.novai_get_signals_by_heightList the signal commitments recorded at a specific block height. Each entry has a commitment hash, a numeric signal type, the height, and the issuer. Use this to see which signals were committed in a given block.novai_get_signals_by_issuerList the signal commitments issued by a given entity within a block height range. Returns commitment hash, signal type, height, and issuer for each.novai_get_signals_by_typeList the signal commitments of a given type within a block height range. The endpoint currently accepts these signal type codes: 0 Anomaly, 1 Optimization, 2 Prediction, 3 RiskScore, 4 AuditReport, 5 SpamRisk, 6 CongestionForecast. Returns commitment hash, signal type, height, and issuer for each.novai_get_oracle_anchorFetch a single oracle anchor by its signal hash. Returns the issuer entity, data hash, external timestamp, source hash, expiry and anchor heights, and data tag, or null if no anchor exists for that hash.novai_get_oracle_anchors_by_entityList oracle anchors issued by a given entity within a block height range, optionally filtered by an external timestamp range. Returns issuer entity, data hash, external timestamp, source hash, expiry and anchor heights, and data tag for each.novai_get_oracle_anchors_by_tagList oracle anchors carrying a given data tag within a block height range, optionally filtered by an external timestamp range. Returns issuer entity, data hash, external timestamp, source hash, expiry and anchor heights, and data tag for each.novai_get_memory_objectsList the on-chain memory objects owned by an entity. Each object has an object id, a numeric object type, owner, creation and update heights, and hex encoded data. Object type codes: 0 ChainSummary, 1 LabelIndex, 2 EmbeddingCommitment, 3 AnomalyLog, 4 StatisticsSnapshot, 5 ReputationEvent, 6 Rating, 7 SignalCatalog, 8 CompositionGraph, 9 VerificationRecord, 10 DelegationGrant, 11 Subscription, 12 ServiceDescriptor, 13 VkRegistration, 14 SlaAgreement, 15 PaymentChannel.
Mastercard Developers MCP tools 9
get-services-listLists all available Mastercard Developers Products and Services with their basic information including title, description, and service id. IMPORTANT: The response contains both 'Products' (business offerings) and 'Services' (technical APIs with serviceIds). Use "serviceId" for each service for any tools that require serviceId as the parameter.get-documentationProvides an overview of all available documentation for a specific Mastercard service including section titles, descriptions, and navigation links. It takes one argument: - serviceId (str): The unique identifier of the Mastercard service (e.g., 'send', 'loyalty', 'locations')get-documentation-section-contentRetrieves the complete content for a specific documentation section. IMPORTANT: A section is not a single page, but rather a collection of pages that are grouped together. It takes two arguments: - serviceId (str): The unique identifier of the Mastercard service (e.g., 'send', 'loyalty', 'locations') - sectionId (str): The specific section identifier within the service documentation (e.g., 'getting-started', 'api-reference')get-documentation-pageRetrieves the complete content of a specific documentation page. Takes one argument: - pagePath (str): The full path to the documentation page (e.g., '/send/documentation/use-cases/index.md')get-oauth10a-integration-guideRetrieves the comprehensive OAuth 1.0a integration guide including step-by-step instructions, code examples, and best practices for Mastercard APIs. Optionally specify a programming language to get language-specific examples and guidance.get-oauth20-integration-guideRetrieves the comprehensive OAuth 2.0 integration guide including step-by-step instructions, code examples, and best practices for Mastercard APIs. Optionally specify a programming language to get language-specific examples and guidance.get-openfinance-integration-guideRetrieves the comprehensive Open Finance (previously known as Open Banking) integration guide including setup instructions, API usage examples, and implementation best practices.get-api-operation-listProvides a summary of all API operations for a specific Mastercard API specification including HTTP methods, request paths, titles, and descriptions. It takes one argument: - apiSpecificationPath (str): The path to the API specification file e.g., '/open-finance-us/swagger/openbanking-us.yaml')get-api-operation-detailsProvides detailed information about a specific API operation including parameter definitions, request and response schemas, and technical specifications for successful API calls. It takes three arguments: - apiSpecificationPath (str): The path to the API specification file (e.g. The path would be /open-finance-us/swagger/openbanking-us.yaml for https://static.developer.mastercard.com/content/open-finance-us/swagger/openbanking-us.yaml, https://developer.mastercard.com/open-finance-us/swagger/openbanking-us.yaml, or /open-finance-us/swagger/openbanking-us.yaml) - method (str): The HTTP method of the operation (e.g., GET, POST, PUT, DELETE) - path (str): The API endpoint path from the specification (e.g., /payments, /accounts/{id})
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.
Novai MCP Server
{
"mcpServers": {
"0x-devc-novai-mcp-server": {
"command": "npx",
"args": [
"-y",
"novai-mcp-server"
],
"env": {
"NOVAI_RPC_URL": "YOUR_NOVAI_RPC_URL_HERE"
}
}
}
}
Mastercard Developers MCP
{
"mcpServers": {
"mastercard-developers-mcp": {
"command": "npx",
"args": [
"-y",
"@mastercard/developers-mcp"
]
}
}
}
Frequently asked questions
Novai MCP Server is categorized under Finance & Fintech and uses a local stdio subprocess. Mastercard Developers MCP belongs to Finance & Fintech and uses a local stdio subprocess. Pick Novai MCP Server for finance & fintech work and Mastercard Developers 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.
Novai MCP Server is listed as free. Auth: no auth required. Mastercard Developers MCP is listed as free. Auth: no auth required. 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 0x-devc-novai-mcp-server and mastercard-developers-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Novai MCP Server has a quality signal of 60/100 (Good) with 5 views, 0 installs and 1 GitHub stars. Mastercard Developers MCP has 67/100 (Great) with 2 views, 0 installs and 55 GitHub stars.