Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Attribloom

NPM · @ATTRIBLOOM/MCP · SCANNED SEP 20

Affiliate attribution and commission data for iOS (StoreKit 2) and Shopify

Available components

0 this week 78 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
  • Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 60 days ago).Pass
  • Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability76
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 151 tokens (~21/item across 7 items; 7 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
  • Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the Attribloom MCP server?

Attribloom runs locally as an npm package, launched with npx -y @attribloom/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @attribloom/mcp

# add to Claude Code
claude mcp add com-attribloom-mcp -- npx -y @attribloom/mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "com-attribloom-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@attribloom/mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "com-attribloom-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@attribloom/mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add com-attribloom-mcp -- npx -y @attribloom/mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-attribloom-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@attribloom/mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-attribloom-mcp --command npx --arg -y --arg @attribloom/mcp
# ~/.hermes/config.yaml
mcp_servers:
  com-attribloom-mcp:
    command: "npx"
    args: ["-y", "@attribloom/mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "com-attribloom-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@attribloom/mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add com-attribloom-mcp -t stdio -c npx -a -y @attribloom/mcp
// mcp.json
{
  "mcpServers": {
    "com-attribloom-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@attribloom/mcp"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 20 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 15 Sept 26 +1
    • Stability: 0.97 → pass security
  • 13 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 10 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

  • 9 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 8 Sept 26 +1
    • Stability: 0.97 → pass security
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 20 Sept 2026 · Analysed npm/@attribloom/mcp@0.1.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 96 packages
Packages resolved 96
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 7 exposed · ~151 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
campaign_readout ~26

Read conversions + matured commission summary for the tenant (No-Lie real ledger sums)

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

connect_store_guidance ~25

How to connect Shopify or an iOS app (no API key required)

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_started_guidance ~23

Public onboarding steps for Attribloom (no API key required)

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_campaigns ~19

List the tenant's campaigns and their commission rules

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_payouts ~16

List the tenant's payouts

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

payout_eligibility ~20

Check per-affiliate available balance vs payout threshold

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

whoami ~22

Prove the API key works and show the tenant + granted scopes

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Common questions

What is the Attribloom MCP server?

Attribloom is an MCP server listed in the public MCP registry as com.attribloom/mcp. Affiliate attribution and commission data for iOS (StoreKit 2) and Shopify. This page covers its npm package (@attribloom/mcp).

Is the Attribloom MCP server safe to use?

Attribloom scores 78 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Attribloom MCP server expose?

Attribloom exposes 7 tools: get_started_guidance, connect_store_guidance, whoami, list_campaigns, campaign_readout, and 2 more. Their descriptions and schemas cost roughly 151 tokens of context every time the server is loaded.

Is the Attribloom MCP server still maintained?

Attribloom is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the Attribloom MCP server under?

Attribloom declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.