AchPay (Anas-github-acc/AchPay) is an MCP server listed on the M8ven Trust Index. It scores 62 out of 100, grade C. It declares 7 tools. No publisher has claimed this listing.

Caution

62/100

AchPay

Item: AchPay
Rating: 62
Author: M8ven

A system that let your agent make secure payment. Connect it to your agent as an MCP server.

→ Anas-github-acc/AchPay · listed on github_repo_search

Caution. Specific findings reduced this grade. They are listed on the page. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every push why connect →

Who stands behind it

Anas-github-acc

Source: github_repo_search

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

⚡ Connect GitHub for Live Monitored

Install from

GitHub

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// key findings

🚨

Secret credentials may flow to a network call

1 flow detected: MCP_HTTP_TOKEN. We can’t prove the destination matches the brand the credential belongs to.

⚠️

Known vulnerabilities in dependencies: 2 high

Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.

🔐

You'll be asked for 8 credentials: CRON_SECRET, MCP_HTTP_TOKEN, MERCHANT_SECRETS_KEY, RAZORPAY_KEY_SECRET, RAZORPAY_WEBHOOK_SECRET, SUPABASE_DEMO_MERCHANT_PASSWORD, SUPABASE_DEMO_PASSWORD, UPSTASH_REDIS_REST_TOKEN

These are read from process.env at runtime. Make sure you trust where they’ll be sent.

// tools this server exposes7 tools

These names and descriptions are the publisher's own, read from the source code. We print them as written. Our assessment is the findings above, not this list.

list_shops

List shops available to the user. Always ask which shop they want before browsing or buying when more than one is available. AchCaffeeZone is the shared test shop.

search_products

get_product_details

get_quote

create_checkout

get_order_status

list_receipts

// known CVEs in dependencies2 high4 low

Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.

highfastify@5.6.1GHSA-247c-9743-5963

Fastify has a Body Schema Validation Bypass via Leading Space in Content-Type Header

highfastify@5.6.1GHSA-jx2c-rxcm-jvmq

Fastify's Content-Type header tab character allows body validation bypass

lowfastify@5.6.1GHSA-444r-cwp2-x5xf

fastify: request.protocol and request.host Spoofable via X-Forwarded-Proto/Host from Untrusted Connections

lowfastify@5.6.1GHSA-mrq3-vjjr-p77c

Fastify Vulnerable to DoS via Unbounded Memory Allocation in sendWebStream

lowfastify@5.6.1GHSA-w2qp-rph6-63g4

fastify vulnerable to schema validation bypass via root primitive coercion mismatch

Depend on this server? Get alerted when its CVEs change.Watch this server free →

// environment variables

To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.

configAPPROVAL_TTL_SECONDS

🔐 secretCRON_SECRET

configDEMO_AUTH_REQUIRED

🔐 secretMCP_HTTP_TOKEN

configMCP_USER_ID

configMERCHANT_NAME

configMERCHANT_PRIVACY_URL

🔐 secretMERCHANT_SECRETS_KEY

configMERCHANT_TERMS_URL

configMERCHANT_URL

configPAYMENT_ADAPTER

configPUBLIC_BASE_URL

configPUBLIC_WEB_URL

configRAZORPAY_KEY_ID

🔐 secretRAZORPAY_KEY_SECRET

configRAZORPAY_MANDATE_FREQUENCY

configRAZORPAY_SBMD

🔐 secretRAZORPAY_WEBHOOK_SECRET

configSTOREFRONT_API_URL

configSUPABASE_DEMO_EMAIL

configSUPABASE_DEMO_MERCHANT_EMAIL

🔐 secretSUPABASE_DEMO_MERCHANT_PASSWORD

configSUPABASE_DEMO_MERCHANT_USER_ID

🔐 secretSUPABASE_DEMO_PASSWORD

configSUPABASE_DEMO_USER_ID

configTEST_DATABASE_URL

🔐 secretUPSTASH_REDIS_REST_TOKEN

configUPSTASH_REDIS_REST_URL

configVITEST

Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.

deployPORT

deployREDIS_URL

deploySUPABASE_ANON_KEY

deploySUPABASE_SERVICE_ROLE_KEY

deploySUPABASE_URL

// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

7/7 tools missing one or more hints — list_shops (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); search_products (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_product_details (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +4 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

License file

No license file

Add a LICENSE file (MIT, Apache-2.0, etc.).

Tool test coverage

Only 0/7 tools referenced in tests (0%)

Write tests that reference each tool by name so every tool has at least one test.

Secrets stay with their owner

1 secret sent to a request target we could not resolve (MCP_HTTP_TOKEN → dynamic) — often a configured endpoint, not necessarily third-party

Audit where credentials are sent. A NOTION_TOKEN should only reach api.notion.com — never a third-party host.

Production dependencies are patched

0 critical, 2 high severity in production deps — fastify@5.6.1 (high), fastify@5.6.1 (high)

Run npm audit fix, or upgrade the affected packages to a non-vulnerable version.

Domain consistency

npm scope @storefront doesn't match GitHub owner anas-github-acc

Use the same org name across GitHub, npm, and your homepage so users can verify the publisher.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail

The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.

// improvement guidance — verified publishers only

We have 7 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.

// embed badge in your README

[![M8ven Verified](https://m8ven.ai/badge/mcp/anas-github-acc/achpay?variant=verified)](https://m8ven.ai/mcp/anas-github-acc/achpay)

Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.

commit: fbcd03b2e20a93ccf0799ef73d6569695627b4d4

code hash: a66d73bda278f60e4aed1693b9ea629a61f3d6f5330e76919a20b63b047e17c0

view raw JSON →

Check MCPs from inside your assistant

Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check

check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern

How to add it →Free · no account needed · works in any MCP client