Back to Browse

Affiliate Router MCP Server

Developer ToolsUse Caution3.2MCP RegistryLocal
Free

Server data from the Official MCP Registry

Route x402 payments, Pyrimid affiliate splits, and referral links. Vendor-neutral, adapter-based.

About

Route x402 payments, Pyrimid affiliate splits, and referral links. Vendor-neutral, adapter-based.

Security Report

3.2
Use Caution3.2High Risk

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.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

env_vars

Check that this permission is expected for this type of plugin.

HTTP Network Access

Connects to external APIs or services over the internet.

File System Read

Reads files on your machine. Normal for tools that analyze or process local data.

File System Write

Writes or modifies files on your machine. Check that this is expected for the tool.

process_spawn

Check that this permission is expected for this type of plugin.

Unverified package source

We couldn't verify that the installable package matches the reviewed source code. Proceed with caution.

What You'll Need

Set these up before or after installing:

Dedicated low-balance Base wallet private key for x402 USDC micropayments. Do not use your primary wallet.Required

Environment variable: WALLET_PRIVATE_KEY

Your Pyrimid affiliate wallet address for on-chain commission splits (optional).Optional

Environment variable: PYRIMID_AFFILIATE_ID

How to Install

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"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub README.

affiliate-router-mcp

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.


What it does

Agents need a way to call monetizable tools without hardcoding every affiliate or payment system. affiliate-router-mcp provides:

  • Discovery — find vendors and products by category or intent
  • Routing — choose the right payment/attribution path automatically
  • Calling — execute payments with affiliate attribution
  • Link generation — inject tracking params into referral URLs
  • Telemetry — log every attributed call locally for tracking

8 Tools

ToolCostDescription
search_opportunitiesFreeFind products by category or keyword
list_affiliate_programsFreeList all vendors and their programs
get_opportunity_detailsFreeFull details on a specific vendor/product
get_best_routeFreeRecommend the best route for an intent
generate_affiliate_linkFreeBuild a tracked referral URL
call_affiliate_productvariesPay and call a product with attribution
estimate_commissionFreeProject monthly earnings at a call volume
get_affiliate_telemetryFreeView local attribution log

Adapters

Each payment or attribution system is a separate adapter. Adding a new one does not affect existing adapters.

AdapterHow it worksPaymentStatus
x402_pyrimidApprove USDC → routePayment on-chain → retry with tx hashOn-chain USDC splitTested
x402_directEIP-3009 transferWithAuthorization via Coinbase facilitatorOn-chain USDC to vendorImplemented
referral_linkInject affiliate param into URLNone — program-dependentImplemented

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.


Install

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"
      }
    }
  }
}

Environment Variables

VariableRequiredNotes
WALLET_PRIVATE_KEYFor call_affiliate_product with x402 adaptersBase wallet with USDC + ETH for gas
PYRIMID_AFFILIATE_IDNoDefault affiliate ID for Pyrimid-registered products
GUMROAD_AFFILIATE_IDNoGumroad tracking ID
PARTNERSTACK_CODENoPartnerStack referral code

Included Vendors

CoinOpAI (x402_pyrimid) — crypto intelligence API on Base mainnet

  • Kronos Signals — $0.05/call, 20% commission
  • Kronos Decision — $0.15/call, 20% commission
  • Trade Preflight — $0.05/call, 20% commission
  • Trade Audit — $0.07/call, 20% commission
  • Image Generation — $0.10/call, 20% commission

Gumroad (referral_link) — digital product marketplace, ~30% commission per product

PartnerStack (referral_link) — SaaS affiliate programs stub (add your own products)


Routing Logic

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

Package vs. Product Updates

These are independent concerns.

Package updates (this repo):

  • Adding or fixing adapters
  • Updating tool schemas
  • Changing routing or caching logic
  • Dependency bumps

Product/catalog updates (registry.json):

  • Registering new vendor endpoints
  • Changing prices or commission rates
  • Enabling affiliate eligibility on a product
  • Assigning network-specific product IDs (e.g. Pyrimid product IDs)

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.


Adding a Vendor

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": [...]
}

Telemetry

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..."
}

What's Not in v0

  • Remote registry sync
  • PartnerStack / Impact.com / Rewardful API integrations
  • Web dashboard
  • Multi-level commissions
  • Server-side redirect tracking for links

Part of the ForgeMesh Ecosystem

Infrastructure for monetized agent ecosystems.

PackageWhatInstall
affiliate-router-mcpVendor-neutral monetization routing (this package)npm i affiliate-router-mcp
coinopai-mcpPaid crypto intelligence via x402npm i coinopai-mcp
forgemesh-imagegenPaid image generation MCPnpm i forgemesh-imagegen

Each package works standalone. No shared dependency required.


License

MIT — CoinOpAI

Reviews

No reviews yet

Be the first to review this server!