Affiliate Networks MCP — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Follow-up value is specific to Local affiliate-network adapters for publisher and advertiser accounts: Which experimental adapters gain maintained evidence without prematurely receiving production labels?

Reviewed Oct 5, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

Bring affiliate-network reporting into an MCP client using the user's own network credentials.

What we know

Local/remote affiliate reporting MCP with a large adapter set spanning publisher/advertiser networks; project explicitly labels most adapters experimental.

Maintenance / activity evidence

affiliate-networks-mcp 0.20.0 published 2026-07-29T07:51:35.309Z

Tracking evidence observed Oct 5, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: high.

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Primarily reporting/read access based on current public description; adapter-specific authority may vary.
Multiple network-specific credentials.
Sensitive access: Revenue/commission/conversion data, Network credentials

Primary risk is credential aggregation and inconsistent experimental adapters.

Full authority, access and evidence limits are available in Review context and Access & risk.

All limitations / Review context

Which experimental adapters gain maintained evidence without prematurely receiving production labels?

The bounded review of the publisher's documented Local affiliate-network adapters for publisher and advertiser accounts and release notices identified no disclosed material condition preventing an accurately scoped public tracking entry. The resource's operational permissions remain uncertainty; this assessment does not certify installation safety.

Primary risk is credential aggregation and inconsistent experimental adapters.
Primarily reporting/read access based on current public description; adapter-specific authority may vary.
Multiple network-specific credentials.
Affiliate performance/account data is fetched from configured networks.
Sensitive access: Revenue/commission/conversion data, Network credentials
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited.
Documented tool authority and any remote data handling must be checked before installation or use.
Tool inventory, client matrix and permissions completeness were not requirements for this Radar tracking review.
Most adapters are experimental.
Each network has its own credential/permission model and data semantics.
Remote endpoint is authentication-gated.
Exact write surface was not confirmed; treat as reporting-oriented unless a specific adapter says otherwise.
Most adapters are explicitly experimental; do not generalize behavior from one network to all.

Original activity observations

affiliate-networks-mcp 0.20.0 published 2026-07-29T07:51:35.309Z

Technical identity

npm/affiliate-networks-mcp

Exact implementation source: https://www.npmjs.com/package/affiliate-networks-mcp ↗
Reviewed resource type: MCP Server
Repository identity: bobberrisford/affiliatemcp
Package identity: npm:affiliate-networks-mcp
Service endpoint: https://mcp.agenticaffiliate.ai/mcp

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 5, 2026 · Latest source observation Oct 8, 2026

Package registry metadata ↗
affiliate-networks-mcp
Recorded package identity, distribution or download evidence.
Evidence source ↗
agenticaffiliate.ai
Source material retained for this review.
Includes references whose attribution is not established.
GitHub repository ↗
bobberrisford/affiliatemcp
Repository reference; implementation attribution is not established for every document.
Includes references whose attribution is not established.
Registry source ↗
registry.modelcontextprotocol.io/
Source material retained for this review.
Includes references whose attribution is not established.

Setup · Watchlist

Install & Agents

Publisher instructions.

Source evidence observed Oct 14, 2026.

Additional setup details required — see the specific gaps below.

Warning

Not runtime tested, no third-party installation, network authorization, paid calls, or mutation executed.
Do not claim production service is available based on README alone.
Official setup/test/install and uninstall commands; individual affiliate network authentication still required
Split multiline shell script string into distinct publisher actions: setup, test, install. Per-network credentials still required.
Official npm publisher package page README inspected for this exact npm identity; static research only. Some setup statements are conservatively summarized; no source code or live client execution checked. V2 review did not run any live client.
Check actual host syntax and supply credentials in secure client environment; do not paste placeholders verbatim.
Avoid write, payment, token transfer, publishing, sending, booking and remote account changes as tests.
Replace credential, action and registration placeholders; follow the matching publisher/client prerequisites. No execution performed.
Use the matching host, actual registration name and original installation environment; this does not revoke credentials.

Install / connect
Publisher instructions
Official setup/test/install and uninstall commands; individual affiliate network authentication still required | Publisher npm README revisited on 2026-10-14; exact identity retained.
Reviewed setup example · Publisher instructions
npx affiliate-networks-mcp setup
Reviewed setup example · Publisher instructions
npx affiliate-networks-mcp test
Reviewed setup example · Publisher instructions
npx affiliate-networks-mcp install
Configure / authenticate
MCP100 setup guide
Use publisher setup wizard, then `npx affiliate-networks-mcp install --codex` for Codex or select the installed host. Configure network credentials in the guided secure setup.
Check connection
Suggested check
`npx affiliate-networks-mcp test` returns per-network status; tool discovery is a separate MCP check.
Remove / uninstall / revoke
MCP100 setup guide
If installed via Claude Code with this exact registration key, unregister it using the shown host command. For publisher .mcpb extension, remove it in Claude Desktop Settings > Extensions; for a different client edit its MCP settings.
Remove named client registration · Claude Code only · MCP100 composed guide
claude mcp remove affiliate-networks-mcp

Official Documentation & Sources

What it does

Local/remote affiliate reporting MCP with a large adapter set spanning publisher/advertiser networks; project explicitly labels most adapters experimental.

Capability: Data & Databases
Resource type: MCP Server
Industry: Media & Marketing
Best fit: Bring affiliate-network reporting into an MCP client using the user's own network credentials.

Representative uses

Read affiliate network reporting
Query publisher/advertiser metrics across configured networks
Use network-specific adapters with BYO credentials

Limitations

Most adapters are experimental.
Each network has its own credential/permission model and data semantics.
Remote endpoint is authentication-gated.
Exact write surface was not confirmed; treat as reporting-oriented unless a specific adapter says otherwise.
Most adapters are explicitly experimental; do not generalize behavior from one network to all.

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: Multiple network-specific credentials.
Permissions: Primarily reporting/read access based on current public description; adapter-specific authority may vary.
Data handling: Affiliate performance/account data is fetched from configured networks.
Cost: network_dependent
Risk and cautions: Primary risk is credential aggregation and inconsistent experimental adapters.

Access scope and cautions

Write actions: None in the reviewed inventory
Sensitive access: Revenue/commission/conversion data Network credentials
Risk level: moderate

FAQ

Based on reviewed evidence as of 2026-10-08. Watchlist tracking is not a recommendation or a security certification.

Which tasks are documented for this implementation?

The reviewed tasks include: Read affiliate network reporting; Query publisher/advertiser metrics across configured networks; Use network-specific adapters with BYO credentials.

What setup and authentication are documented?

Recorded installation/entrypoint step: npx -y affiliate-networks-mcp. Recorded endpoint: https://mcp.agenticaffiliate.ai/mcp. Recorded transport: stdio, streamable_http. Recorded environment-variable notes: Network-specific credentials. No configuration values are supplied here. Prerequisites: Credentials for desired affiliate networks. These are the documented setup details, not a claim that installation or client compatibility was independently tested. Authentication: Bring-your-own affiliate-network keys; remote endpoint requires auth.

Can it modify data or perform write operations?

The reviewed inventory lists no write actions. An empty inventory alone does not establish read-only authority. Recorded permission boundary: Primarily reporting/read access based on current public description; adapter-specific authority may vary.

What data-handling boundary should I consider?

Affiliate performance/account data is fetched from configured networks. Recorded sensitive-access context: Revenue/commission/conversion data; Network credentials.

What limitations and risks should I check before use?

Primary risk is credential aggregation and inconsistent experimental adapters. Most adapters are experimental. Each network has its own credential/permission model and data semantics. Remote endpoint is authentication-gated. Exact write surface was not confirmed; treat as reporting-oriented unless a specific adapter says otherwise. Most adapters are explicitly experimental; do not generalize behavior from one network to all. Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited. Documented tool authority and any remote data handling must be checked before installation or use.