F
Warning
26/100
17 hours ago

aipaygen-mcp

250+ AI-powered MCP tools: research, write, code, translate, scrape, sentiment, vision, RAG, agent memory, marketplace, trading signals, and more. 15 models across 7 providers. Pay-per-use via API key or x402 USDC micropayments.

Warning. Serious findings were identified. Review the full report before connecting. 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 pushwhy connect →

Who stands behind it

Damien829

Source: Glama · also listed on PulseMCP

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 →

Install from

M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.

// key findings
🚨
Secret credentials may flow to a network call
25 flows detected: AIPAYGEN_API_KEY, APIFY_TOKEN, INDEXNOW_KEY. We can’t prove the destination matches the brand the credential belongs to.
🔐
You'll be asked for 34 credentials: AIPAYGEN_API_KEY, AIPAYGEN_X402_TOKEN, ADMIN_SECRET, ANTHROPIC_API_KEY, STRIPE_SECRET_KEY, STRIPE_WEBHOOK_SECRET, STRIPE_PUBLISHABLE_KEY, CDP_API_KEY_SECRET, AIPAYGEN_TOKEN, JWT_SECRET, APIFY_TOKEN, GITHUB_TOKEN, INDEXNOW_KEY, REDDIT_CLIENT_SECRET, REDDIT_PASSWORD, TWITTER_BEARER_TOKEN, APIFY_API_TOKEN, RESEND_API_KEY, OPENAI_API_KEY, GOOGLE_API_KEY, DEEPSEEK_API_KEY, TOGETHER_API_KEY, XAI_API_KEY, MISTRAL_API_KEY, COHERE_API_KEY, PERPLEXITY_API_KEY, DEVTO_API_KEY, TELEGRAM_BOT_TOKEN, AGENT_PRIVATE_KEY, CSRF_SECRET, GOOGLE_CLIENT_SECRET, GITHUB_CLIENT_SECRET, SECRET_KEY, AIPAYGEN_PRIVATE_KEY
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// 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.
🔐 secretAIPAYGEN_API_KEYexport =apk_your_key_here
configAIPAYGEN_BASE_URL
🔐 secretAIPAYGEN_X402_TOKEN
configDAILY_COST_LIMIT_USD
🔐 secretADMIN_SECRET
configWALLET_ADDRESS
configFACILITATOR_URL
🔐 secretANTHROPIC_API_KEY
🔐 secretSTRIPE_SECRET_KEY
🔐 secretSTRIPE_WEBHOOK_SECRET
🔐 secretSTRIPE_PUBLISHABLE_KEY
configBASE_URL
configCDP_API_KEY_ID
🔐 secretCDP_API_KEY_SECRET
configADSENSE_PUB_ID
configGA4_MEASUREMENT_ID
configAIPAYGEN_CLIENT_ID
configAIPAYGEN_REQUEST_SIGNATURE
config_AIPAYGEN_FREE_TIER
configAIPAYGEN_FORCE_MODEL
🔐 secretAIPAYGEN_TOKEN
configACCOUNTS_DB
🔐 secretJWT_SECRET
configADMIN_EMAIL
🔐 secretAPIFY_TOKEN
configCRYPTO_MIN_DEPOSIT_USD
configCRYPTO_MAX_DEPOSIT_USD
configCRYPTO_FEE_PERCENT
configCRYPTO_BASE_CONFIRMATIONS
configCRYPTO_POLL_INTERVAL
configCRYPTO_BASE_RPC
configCRYPTO_SOLANA_RPC
configCRYPTO_HD_MNEMONIC
🔐 secretGITHUB_TOKEN
🔐 secretINDEXNOW_KEY
configREDDIT_CLIENT_ID
🔐 secretREDDIT_CLIENT_SECRET
configREDDIT_USERNAME
🔐 secretREDDIT_PASSWORD
🔐 secretTWITTER_BEARER_TOKEN
🔐 secretAPIFY_API_TOKEN
configEAS_SCHEMA_UID
configBASE_RPC_URL
🔐 secretRESEND_API_KEY
🔐 secretOPENAI_API_KEY
🔐 secretGOOGLE_API_KEY
🔐 secretDEEPSEEK_API_KEY
🔐 secretTOGETHER_API_KEY
🔐 secretXAI_API_KEY
🔐 secretMISTRAL_API_KEY
🔐 secretCOHERE_API_KEY
🔐 secretPERPLEXITY_API_KEY
configOLLAMA_BASE_URL
🔐 secretDEVTO_API_KEY
configSESSIONS_DB
configSHOWCASE_DB
🔐 secretTELEGRAM_BOT_TOKEN
configWEBHOOKS_DB
configX402_MAX_PER_CALL
configX402_DAILY_BUDGET
🔐 secretAGENT_PRIVATE_KEY
🔐 secretCSRF_SECRET
configEVM_NETWORK
configOAUTH_BASE_URL
configGOOGLE_CLIENT_ID
🔐 secretGOOGLE_CLIENT_SECRET
configGITHUB_CLIENT_ID
🔐 secretGITHUB_CLIENT_SECRET
🔐 secretSECRET_KEY
configAPP_NAME
configSTRIPE_PRICE_STARTER
configSTRIPE_PRICE_PRO
configSTRIPE_PRICE_BUSINESS
configDATABASE_PATH
configRATE_LIMIT_PER_MINUTE
🔐 secretAIPAYGEN_PRIVATE_KEY
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployPORT
// 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

427/427 tools missing one or more hints — research (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); summarize (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); analyze (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +424 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.

Tool test coverage

Only 111/427 tools referenced in tests (26%)

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

Secrets stay with their owner

11 secret/sensitive values flow into network calls (STRIPE_WEBHOOK_SECRET → dynamic, STRIPE_WEBHOOK_SECRET → dynamic) (14 other flows matched canonical API hosts)

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

Secrets never reach shell commands

1 secret value passed to shell commands — possible command injection

Never pass secrets through shell commands. Use library APIs that accept credentials as arguments.

Secrets not logged

24 secret values sent to console.log

Redact or omit secret values from log output.

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 6 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/damien829-aipaygen-aw8ivg?variant=verified)](https://m8ven.ai/mcp/damien829-aipaygen-aw8ivg)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 36370d3313697a8551ff989358377184354cda16
code hash: c82abca4216d0c747dac8f1f2762f84ac6ebd2b234d854bad90bba58c9ab17ad
verified: 8/19/2026, 9:55:55 AM
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