easypaydirect-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NMI_API_URL | No | Gateway API base URL. Defaults to https://secure.nmi.com. For EPD/white-labels, set this to your gateway's host. | https://secure.nmi.com |
| NMI_SECURITY_KEY | Yes | Your gateway API security key (a read-only key is recommended). Merchant portal → Settings → Security Keys. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_transactionA | Fetch a single transaction by its gateway transaction ID. Read-only. |
| search_transactionsA | Search transactions by date range and optional filters (condition, action type, payment type, source, email, order id). Read-only. |
| get_subscriptionA | Fetch a single recurring subscription by its subscription ID (report_type=recurring). Read-only. |
| list_subscriptionsA | List recurring subscriptions, optionally filtered by created/updated date range (report_type=recurring). Read-only. |
| list_recurring_plansA | List recurring billing plans, optionally filtered to a single plan (report_type=recurring_plans). Read-only. |
| get_customer_vault_recordA | Fetch a single stored Customer Vault record by its customer_vault_id (report_type=customer_vault). Returns stored profile data only — never full card numbers. Read-only. |
| list_customer_vaultA | List stored Customer Vault records, optionally filtered by created/updated date range (report_type=customer_vault). Read-only. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Each tool targets a distinct resource and action: plans, transactions, subscriptions, and customer vault entries. The get vs. list/search operations are clearly separated, making misselection unlikely.
Most tools follow a consistent verb_noun pattern (list_*, get_*), but 'search_transactions' deviates from the list_* convention for collection queries, and 'get_customer_vault_record' includes an extra descriptor compared to similar getters. These are minor deviations.
With 7 tools, the set is well-scoped for a read-only reporting API, covering the core entities without unnecessary redundancy or bloat.
For a read-only reporting domain, the coverage is complete: all major entities (plans, transactions, subscriptions, customer vault) have retrieval capabilities, including single-item and list/search variants. No obvious gaps are present.