Attribloom — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Monitor identity continuity, MCP tool inventory, permissions and adoption.

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

Best fit

Affiliate attribution / commission reporting with tenant-scoped MCP

What we know

Affiliate attribution / commission reporting with tenant-scoped MCP. Published by the owner of npm package @attribloom/mcp. Affiliate attribution and commission data for iOS (StoreKit 2) and Shopify.

Maintenance / activity evidence

217 npm downloads, 2026-09-09 to 2026-10-08

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

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Affiliate campaign and merchant store information is account-scoped; published read-only data access requires scoped tenant API key. Complete write authority is not verified.
Tenant-scoped API key
Sensitive access: Service account information and data accessible by supplied credentials

Affiliate campaign and merchant store information is account-scoped; published read-only data access requires scoped tenant API key.
Public listing suitability does not imply safe installation or entitlement to access third-party accounts.

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

Popularity

· 217 package downloads / 30 days

Downloads observed Oct 10, 2026.

Exact npm package @attribloom/mcp; provider interval 2026-09-09–2026-10-08 (inclusive); observed 2026-10-10T04:43:53Z.

All limitations / Review context

Has @attribloom/mcp changed publishing identity, permissions, install requirements, or risk exposure?

Published package documentation reviewed; public listing with prominently disclosed risks: Affiliate campaign and merchant store information is account-scoped; published read-only data access requires scoped tenant API key.

Affiliate campaign and merchant store information is account-scoped; published read-only data access requires scoped tenant API key.
Public listing suitability does not imply safe installation or entitlement to access third-party accounts.
Tenant-scoped API key
Sensitive access: Service account information and data accessible by supplied credentials
Complete write authority is not verified.
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
Respect upstream entitlements, version constraints and least-privilege setup.
Write actions/tool inventory not confirmed against exact tool documentation; listed action classes remain illustrative or context-dependent. Empty inventory does not establish read-only.
Publicly documented capabilities are not a guarantee of a safe deployment; review third-party data processing and access scopes.
Public exact-package npm downloads observed for recent 30-day window.

Original activity observations

217 npm downloads, 2026-09-09 to 2026-10-08

Technical identity

npm/@attribloom/mcp

Exact implementation source: https://www.npmjs.com/package/@attribloom/mcp ↗
Reviewed resource type: MCP Server
Package identity: npm:@attribloom/mcp

Evidence & Sources

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

Reviewed Oct 10, 2026 · Latest source observation Oct 10, 2026

Registry source ↗
registry.modelcontextprotocol.io/v0/servers
Source material retained for this review.
Package registry ↗
@attribloom/mcp
Recorded package identity, distribution or download evidence.

Setup · Watchlist

Install & Agents

Publisher instructions.

Source evidence observed Oct 14, 2026.

Additional setup details required — see the specific gaps below.

Warning

Provider-specific API credentials and dashboard revocation path must be separately confirmed; no unsafe generic CLI revoke.
Publisher baseline documentation retained; live recheck unavailable. This update does not establish a fresh publisher-source verification.
Reviewed actionability is baseline documentation only; client compatibility and runtime operation have not been verified.
Literal command/entry path confirmed against official README; does not validate runtime or host compatibility.
Prior reviewed safety note: Do not delete user data or assume this cancels upstream authorizations.
Reviewed against publisher package README; command may need explicit client environment and prerequisites.
Client removal, software uninstall, persistent-data deletion and credential revocation are separate actions.

Install / connect
MCP100 setup guide
Publisher-documented install or connect path; prerequisites and any extra host configuration remain required.
publisher install or stdio launch · retained baseline · Publisher instructions
npx -y @attribloom/mcp
reviewed install or registration · Claude Code only · retained baseline · MCP100 composed guide
claude mcp add attribloom --env ATTRIBLOOM_API_KEY=<YOUR_KEY> -- npx -y @attribloom/mcp
Configure / authenticate
MCP100 setup guide
Set ATTRIBLOOM_API_KEY from Dashboard > Settings > API keys for data tools.
Check connection
Suggested check
Inspect tool list, then use readonly organization data request.
Remove / uninstall / revoke
MCP100 setup guide
If registered in Claude Code under the name `attribloom`, remove the client entry with `claude mcp remove attribloom`. For other MCP hosts remove the matching server/connector in that host’s MCP settings. Remove a globally installed software package separately if applicable; this does not delete data or revoke a service credential.
Client removal, software uninstall, persistent-data deletion and credential revocation are separate actions.
Remove client registration · Claude Code only · MCP100 composed guide
claude mcp remove attribloom

Official Documentation & Sources

https://www.npmjs.com/package/@attribloom/mcp ↗

What it does

Affiliate attribution / commission reporting with tenant-scoped MCP. Published by the owner of npm package @attribloom/mcp. Affiliate attribution and commission data for iOS (StoreKit 2) and Shopify.

Capability: Productivity & Collaboration
Resource type: MCP Server
Industry: Media & Marketing
Best fit: Affiliate attribution / commission reporting with tenant-scoped MCP

Representative uses

Affiliate attribution / commission reporting with tenant-scoped MCP

Limitations

Affiliate campaign and merchant store information is account-scoped; published read-only data access requires scoped tenant API key.
Publicly documented capabilities are not a guarantee of a safe deployment; review third-party data processing and access scopes.
Public exact-package npm downloads observed for recent 30-day window.

Reviewed access

Access & risk

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

Authentication: Tenant-scoped API key
Permissions: Affiliate campaign and merchant store information is account-scoped; published read-only data access requires scoped tenant API key.
Data handling: Affiliate campaign and merchant store information is account-scoped; published read-only data access requires scoped tenant API key.
Cost: Credit/subscription costs may apply; inspect provider docs
Risk and cautions: Affiliate campaign and merchant store information is account-scoped; published read-only data access requires scoped tenant API key.

Access scope and cautions

Write actions: Not verified
Sensitive access: Service account information and data accessible by supplied credentials
Risk level: medium
Security notes: Affiliate campaign and merchant store information is account-scoped; published read-only data access requires scoped tenant API key. Public listing suitability does not imply safe installation or entitlement to access third-party accounts.

The reviewed evidence does not establish the complete write authority of this MCP. Consult the unresolved evidence before granting write access.

FAQ

Based on reviewed evidence as of 2026-10-10T04:43:53Z. Watchlist tracking is not a recommendation or a security certification.

What setup and authentication are documented?

A complete connection procedure is not verified. Client notes: Do not infer shell entrypoint or automated credential setup if a command is not explicitly verified. These facts do not supply missing installation commands, credentials or a verified authentication procedure. Authentication: Tenant-scoped API key

Can it modify data or perform write operations?

Not verified. The available evidence does not establish the complete write authority. Recorded permission context: Affiliate campaign and merchant store information is account-scoped; published read-only data access requires scoped tenant API key.

What data-handling boundary should I consider?

Affiliate campaign and merchant store information is account-scoped; published read-only data access requires scoped tenant API key. Recorded sensitive-access context: Service account information and data accessible by supplied credentials.

What limitations and risks should I check before use?

Affiliate campaign and merchant store information is account-scoped; published read-only data access requires scoped tenant API key. Publicly documented capabilities are not a guarantee of a safe deployment; review third-party data processing and access scopes. Public exact-package npm downloads observed for recent 30-day window. Public listing suitability does not imply safe installation or entitlement to access third-party accounts. Respect upstream entitlements, version constraints and least-privilege setup.

What cost model is recorded?

The reviewed cost model is Credit/subscription costs may apply; inspect provider docs. This classification does not establish current prices, quotas or the cost of every downstream operation. Check the applicable service terms before authorizing paid actions.