Rabobank MCP Training Demo
Related Servers
Alternatives to Rabobank MCP Training Demo
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceA production-grade MCP server for a fictional digital bank, exposing tools for an AI copilot to service customers across the full risk spectrum from read-only lookups to money movement and destructive admin actions, with OAuth 2.1 security and a realistic dataset.6 npm1-
- FlicenseNot gradedqualityDmaintenanceA production-grade MCP server that exposes real-time banking data replicated via Oracle GoldenGate CDC as structured tools for AI agents, enabling read, score, and write operations on customer, account, transaction, and alert data.1-
- FlicenseAqualityCmaintenanceMCP server exposing a fictional payment domain as tools, resources, and prompts, enabling reasoning over transactions, payment hubs, services, and system health.8-
- AlicenseAqualityAmaintenanceMCP server for AWS Payment Cryptography that gives AI coding assistants direct access to the APC control plane and data plane, with embedded knowledge of payment standards, HSM vendor command sets, and PCI PIN v3.1 compliance requirements.581Apache 2.0
- AlicenseNot gradedqualityCmaintenanceMCP server that enables AI agents to analyze legacy code, plan and execute software migrations, generate modern source code, and validate production-ready artifacts through a multi-agent pipeline.MIT
- AlicenseAqualityCmaintenanceArchitecture governance MCP server for AI-built codebases, enabling health checks, template management, and project scaffolding with migration support.511 npmMIT
TDQS
Scored across 4 tools
Each tool targets a distinct entity or action: customer profile, product info, API endpoint info, and architecture check. There is no overlap in purpose.
Three tools use the get_ prefix (get_customer_profile, get_product_info, get_api_endpoint_info), while one uses run_ (run_architecture_check). The pattern is mostly consistent but has a minor deviation.
With 4 tools, the server is well-scoped for a training demo. Each tool covers a different aspect, and the count is appropriate without being bloated or thin.
The tools cover the main read-only operations for a demo (customer, product, API info, and architecture check). Missing CRUD operations or additional resources like accounts/transactions could be considered gaps, but the demo purpose is adequately served.