Loading ToolBench
Comprehensive MCP server exposing all Mercury banking API features including accounts, recipients, transactions, and payment operations
Mercury MCP exposes 10 banking tools with consistent naming (verb_noun pattern: mercury_listAccounts, mercury_sendPayment) and basic descriptions. However, parameter descriptions are sparse or missing entirely. Most tools lack documented output schemas. Input schemas are present for 7/10 tools but incomplete, many parameters lack type constraints (e.g., mercury_validateRecipient.paymentMethod is a string with no enum; mercury_createRecipient.electronicRoutingInfo has nested properties but no required field declarations). Error handling and recovery guidance are absent. Security concerns: no evidence of permission checks on WRITE operations despite PermissionsManager existing. Descriptions average ~60 chars, below the 194-char baseline for A+ tools. No parameter descriptions for mercury_listAccounts, mercury_getTreasury, mercury_listRecipients, mercury_validatePayment inputs.
Create a new payment recipient in Mercury
Get detailed information for a specific Mercury account
Get current and available balance for a Mercury account
Get detailed information for a specific Mercury recipient
Get treasury account balance and information
List all Mercury accounts with balances and basic information
Four tools (mercury_listAccounts, mercury_getTreasury, mercury_listRecipients, mercury_validatePayment) have no visible input schemas.
Parameter descriptions are missing or minimal. mercury_validateRecipient.paymentMethod is a string with no enum constraint or description; mercury_createRecipient.electronicRoutingInfo is an object with nested properties but no required field list or per-property descriptions.
No output schemas documented for any tool. LLMs cannot plan downstream calls or extract required fields (e.g., does mercury_getAccount return account_id for use in mercury_sendPayment?).
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 59 | <=2025-11-25 | v2 |
List all Mercury payment recipients with basic information
Send an ACH or electronic payment to a recipient
Validate payment parameters before sending
Validate recipient information and check for duplicates
WRITE operations (mercury_sendPayment, mercury_createRecipient) lack error handling guidance, confirmation steps, or recovery instructions. No dry-run or confirmation pattern visible.
PermissionsManager exists but no evidence it is enforced on WRITE tools. mercury_sendPayment and mercury_createRecipient should gate execution behind permission checks; code shows registration but not enforcement.