Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add praveendias1180/easypaydirect-mcp --skill easypaydirectgit clone --depth 1 https://github.com/praveendias1180/easypaydirect-mcpWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/praveendias1180/easypaydirect-mcp/easypaydirect)<a href="https://agentmods.dev/skills/praveendias1180/easypaydirect-mcp/easypaydirect"><img src="https://agentmods.dev/badge/skills/praveendias1180/easypaydirect-mcp/easypaydirect/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/praveendias1180/easypaydirect-mcp/easypaydirect"><img src="https://agentmods.dev/badge/skills/praveendias1180/easypaydirect-mcp/easypaydirect.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00093 | $0.01310 |
| Opus 5 | $0.00046 | $0.00655 |
| Sonnet 5 | $0.00019 | $0.00262 |
| Haiku 4.5 | $0.00009 | $0.00131 |
Grade A, and why
easypaydirect scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Easy Pay Direct / NMI gateway
The easypaydirect MCP server gives you seven read-only tools over the gateway's
Query API. Nothing here can charge, refund, void, or change a subscription — if the
user asks for that, say it has to be done in the gateway portal, and never imply you did it.
| Tool | Use it for |
|---|---|
search_transactions |
"Did X pay?", declines, refunds, anything by email / order id / date / status |
get_transaction |
Full detail of one transaction id (every action on it) |
get_subscription |
One recurring subscription by id |
list_subscriptions |
Subscriptions created/updated in a date range |
list_recurring_plans |
Plan templates (name, amount, frequency) — call with no args to find a plan by name |
get_customer_vault_record |
One stored customer profile by vault id |
list_customer_vault |
Vault records created/updated in a date range |
Picking the right call
- "Did this customer pay?" / "why did their card fail?" →
search_transactionswithemail(addstart_date/end_dateto narrow). Thenget_transactionon the ids that matter to see every action. - "What is this customer's billing set-up?" → find their transactions by email, read the
customer_vault_id/ subscription ids from them, thenget_customer_vault_recordandget_subscription. - "Which plan is 'Monthly Pro'?" →
list_recurring_planswith no arguments, match onplan_name, then use itsplan_id. - Failures only →
condition: "failed"; refunds →action_type: "refund"; ACH only →transaction_type: "ck".
Reading results
Responses are the gateway's XML turned into JSON, so they are nested:
- The root is
nm_response. Records sit undernm_response.transaction,nm_response.subscription,nm_response.plan, ornm_response.customer_vault.customer. - One match is an object; several matches are an array. Handle both. An empty
nm_responsemeans no records matched — say so plainly. - A transaction's
actionis its history (sale, settle, refund, return, …), again an object for one entry or an array for several. The latest action tells you where the money actually is; the top-levelconditionsummarises it. - Every value is a string, including amounts. Don't do float maths on them carelessly; keep two decimals.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- yesterday First seen · 88 lines · 93 tokens per session scan A f4b6a013c02b
easypaydirect is a skill published in the GitHub repository praveendias1180/easypaydirect-mcp (0 stars, last pushed yesterday), licensed MIT. It adds 93 tokens to every session and 1,310 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-14.
Other skills, from other repositories
okx-cex-portfolio
This skill should be used when the user asks about 'account balance', 'how much USDT do I have', 'my funding account', 'show my positions', 'open positions', 'position P&L', 'unrealized PnL', 'closed positions', 'position history', 'realized PnL', 'account bills', 'transaction history', 'trading fees', 'fee tier'…
agoragentic-transaction-assurance
Prepare, evaluate, and reconcile autonomous agent transactions without self-granting payment or owner authority. Use when an agent must bind principal authority, seller terms, payment evidence, execution, delivered outcome, and reconciliation; handle paid retries safely; or prepare an authority request for owner…
stripe
Query and manage Stripe resources (customers, payments, subscriptions). Reads from apps/website/.env. Write operations blocked on live keys.
recurrent-payment
A recurring-payment workflow for T-Kassa, a payment service. It links a customer's card during an initial payment and later charges that saved payment authorisation for a subscription.
refund-payment
A payment procedure for refunding a completed T-Kassa payment or cancelling a payment that is still on hold. T-Kassa is a payment service, and the procedure can also send the required closing receipt.
hive-query
Default entry point for any live crypto question when Hive MCP is connected — prices, wallets, tokens, DeFi, NFTs, Solana, security, markets, DEX, networks, RWA perps. Use it whenever the answer depends on live or on-chain data instead of answering from memory, even if the user never mentions Hive. Routes intent to a…