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.
git clone --depth 1 https://github.com/asgard-ai-platform/mcp-newebpayWrote 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/mcp/asgard-ai-platform/mcp-newebpay/newebpay)<a href="https://agentmods.dev/mcp/asgard-ai-platform/mcp-newebpay/newebpay"><img src="https://agentmods.dev/badge/mcp/asgard-ai-platform/mcp-newebpay/newebpay/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/mcp/asgard-ai-platform/mcp-newebpay/newebpay"><img src="https://agentmods.dev/badge/mcp/asgard-ai-platform/mcp-newebpay/newebpay.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
newebpay 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 9d ago.
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.
What it actually says
{
"newebpay": {
"command": "python",
"args": [
"mcp_server.py"
],
"cwd": "${PWD}",
"env": {
"PYTHONPATH": "${PWD}",
"NEWEBPAY_ENV": "${NEWEBPAY_ENV}",
"NEWEBPAY_NDNF_MERCHANT_ID": "${NEWEBPAY_NDNF_MERCHANT_ID}",
"NEWEBPAY_NDNF_HASH_KEY": "${NEWEBPAY_NDNF_HASH_KEY}",
"NEWEBPAY_NDNF_HASH_IV": "${NEWEBPAY_NDNF_HASH_IV}",
"NEWEBPAY_NDNP_MERCHANT_ID": "${NEWEBPAY_NDNP_MERCHANT_ID}",
"NEWEBPAY_NDNP_HASH_KEY": "${NEWEBPAY_NDNP_HASH_KEY}",
"NEWEBPAY_NDNP_HASH_IV": "${NEWEBPAY_NDNP_HASH_IV}"
}
}
}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.
- 9d ago First seen · 19 lines scan A 88fbde30fd83
newebpay is an MCP server published in the GitHub repository asgard-ai-platform/mcp-newebpay (2 stars, last pushed 5mo ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. 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-08-31.
Other mcp servers, from other repositories
stripe-mcp-server
MCP server for Stripe API — customers, charges, payments, subscriptions, products, and invoices. Runs locally from the stripe-mcp-server npm package.
shopify-mcp
MCP server for Shopify Admin API — product, order, customer, inventory, and fulfillment management. Runs locally from the @purplesquirrel/shopify-mcp npm package.
stripe
Python bindings for the Stripe API. Runs locally from the stripe Python package.
tegro-money
MCP server for Tegro.Money — connect Claude, Cursor and other AI tools to the Tegro.Money payment API (balances, shops, orders, payouts, rates). Read-only, secure, your API key never leaves your machine. Runs locally from the @tegroton/tegro-money-mcp npm package. Needs 2 environment variables to run.
agent-commerce-payments-mcp
MCP server for agent commerce payments. Features create invoice, process payment, escrow funds. From MEOK AI Labs. Runs locally from the agent-commerce-payments-mcp Python package.
myfatoorah-mcp
Safely connect AI agents to MyFatoorah payments, invoices, payment methods, and refunds. Runs locally from the myfatoorah-mcp npm package. Needs 3 environment variables to run.