Server data from the Official MCP Registry
Route x402 payments, Pyrimid affiliate splits, and referral links. Vendor-neutral, adapter-based.
Route x402 payments, Pyrimid affiliate splits, and referral links. Vendor-neutral, adapter-based.
The affiliate-router-mcp server implements monetization routing with reasonable architectural patterns but has significant security concerns around private key handling, insufficient input validation, and weak error handling that could expose sensitive information. The server requires WALLET_PRIVATE_KEY for payment operations—a critical credential that deserves stronger protection. Network access is appropriate for the domain, but credential handling and validation gaps present moderate risk to users who deploy this server. Supply chain analysis found 3 known vulnerabilities in dependencies (0 critical, 3 high severity). Package verification found 1 issue.
7 files analyzed · 16 issues found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
This plugin requests these system permissions. Most are normal for its category.
Unverified package source
We couldn't verify that the installable package matches the reviewed source code. Proceed with caution.
Set these up before or after installing:
Environment variable: WALLET_PRIVATE_KEY
Environment variable: PYRIMID_AFFILIATE_ID
Add this to your MCP configuration file:
{
"mcpServers": {
"io-github-forgemeshlabs-affiliate-router-mcp": {
"env": {
"WALLET_PRIVATE_KEY": "your-wallet-private-key-here",
"PYRIMID_AFFILIATE_ID": "your-pyrimid-affiliate-id-here"
},
"args": [
"-y",
"affiliate-router-mcp"
],
"command": "npx"
}
}
}From the project's GitHub README.
Vendor-neutral monetization routing for agent tools. One MCP server that discovers, routes, and attributes revenue across paid APIs, referral links, and affiliate programs.
Source: https://github.com/forgemeshlabs/affiliate-router-mcp
The router is not tied to any single payment network or affiliate system. Adapters are pluggable. The registry is a local JSON file you control.
Status: experimental · v0.1.6
Disclaimer: This MCP does not guarantee payouts. It routes attribution data according to each vendor/program's rules. Commission distribution is enforced by the vendor's payment system, not by this router.
Agents need a way to call monetizable tools without hardcoding every affiliate
or payment system. affiliate-router-mcp provides:
| Tool | Cost | Description |
|---|---|---|
search_opportunities | Free | Find products by category or keyword |
list_affiliate_programs | Free | List all vendors and their programs |
get_opportunity_details | Free | Full details on a specific vendor/product |
get_best_route | Free | Recommend the best route for an intent |
generate_affiliate_link | Free | Build a tracked referral URL |
call_affiliate_product | varies | Pay and call a product with attribution |
estimate_commission | Free | Project monthly earnings at a call volume |
get_affiliate_telemetry | Free | View local attribution log |
Each payment or attribution system is a separate adapter. Adding a new one does not affect existing adapters.
| Adapter | How it works | Payment | Status |
|---|---|---|---|
x402_pyrimid | Approve USDC → routePayment on-chain → retry with tx hash | On-chain USDC split | Tested |
x402_direct | EIP-3009 transferWithAuthorization via Coinbase facilitator | On-chain USDC to vendor | Implemented |
referral_link | Inject affiliate param into URL | None — program-dependent | Implemented |
Pyrimid is the first fully tested paid affiliate adapter. It is not the only supported model. Future adapters may include: PartnerStack, Rewardful, Impact, Commission Junction, coupon/promo code injection, API-key partner programs, and other emerging agent commerce protocols.
npm install -g affiliate-router-mcp
Or with Claude Code / any MCP client:
{
"mcpServers": {
"affiliate-router": {
"command": "affiliate-router-mcp",
"env": {
"WALLET_PRIVATE_KEY": "0x...",
"PYRIMID_AFFILIATE_ID": "af_your_id",
"GUMROAD_AFFILIATE_ID": "your-gumroad-id"
}
}
}
}
| Variable | Required | Notes |
|---|---|---|
WALLET_PRIVATE_KEY | For call_affiliate_product with x402 adapters | Base wallet with USDC + ETH for gas |
PYRIMID_AFFILIATE_ID | No | Default affiliate ID for Pyrimid-registered products |
GUMROAD_AFFILIATE_ID | No | Gumroad tracking ID |
PARTNERSTACK_CODE | No | PartnerStack referral code |
CoinOpAI (x402_pyrimid) — crypto intelligence API on Base mainnet
Gumroad (referral_link) — digital product marketplace, ~30% commission per product
PartnerStack (referral_link) — SaaS affiliate programs stub (add your own products)
call_affiliate_product(vendor_id, product_id, params, affiliate_id?)
↓
resolve affiliate_id: tool arg → env var → null
↓
adapter = vendor.affiliate_system
↓
x402_pyrimid + affiliate_id present?
cache VALID → Pyrimid split flow (affiliate earns commission)
cache INVALID → x402_direct fallback (vendor gets 100%)
cache UNKNOWN → try Pyrimid → cache result → fallback on failure
x402_direct → EIP-3009 payment, no affiliate split
referral_link → inject tracking param, no payment
These are independent concerns.
Package updates (this repo):
Product/catalog updates (registry.json):
Adding a vendor to registry.json does not require a package release.
Releasing a new package version does not require products to be re-registered.
Edit registry.json. No code changes needed for referral-link vendors.
x402 vendors require a funded wallet. Pyrimid vendors additionally require
on-chain registration to obtain a vendor_id and per-product pyrimid_product_id.
{
"id": "my_vendor",
"name": "My Vendor",
"affiliate_system": "referral_link",
"affiliate_config": {
"tracking_param": "ref",
"affiliate_id_env": "MY_VENDOR_REF_CODE",
"commission_pct": 25
},
"products": [...]
}
All call_affiliate_product calls append to logs/affiliate-telemetry.jsonl:
{
"ts": "2026-05-14T17:07:01Z",
"vendor_id": "coinopai",
"product_id": "kronos_signals",
"amount_usd": 0.05,
"affiliate_id": "af_your_id",
"payment_type": "x402_pyrimid",
"commission_est_usd": 0.0099,
"status": "success",
"tx_hash": "0x..."
}
Infrastructure for monetized agent ecosystems.
| Package | What | Install |
|---|---|---|
| affiliate-router-mcp | Vendor-neutral monetization routing (this package) | npm i affiliate-router-mcp |
| coinopai-mcp | Paid crypto intelligence via x402 | npm i coinopai-mcp |
| forgemesh-imagegen | Paid image generation MCP | npm i forgemesh-imagegen |
Each package works standalone. No shared dependency required.
MIT — CoinOpAI
Be the first to review this server!
by Modelcontextprotocol · Developer Tools
Web content fetching and conversion for efficient LLM usage
by Modelcontextprotocol · Developer Tools
Read, search, and manipulate Git repositories programmatically
by Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.