Gam Seller Node MCP server
io.github.juan-sibbo/gam-seller-mcp-node·v0.11.1Governed MCP seller node: buyer agents discover inventory and register intents; no ad-server writes
0 stars200 downloads/wk
Reviews
Write oneNobody has reviewed Gam Seller Node yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Gam Seller Node tools (1)
write = sends, deletes, buys or postsRead from the package source without running it. The installed server may list more.
well_known_capabilitiesReturn the signed RS256 capability document for this Seller MCP Node.
Public scan report
scanner v0.1.10 · 2026-10-31 · same rubric, same numbers if you re-run it
- Code scan105 source files scanned25/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 32 days ago12/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
How Gam Seller Node compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 88/100
- higher than 75% of 48,255 servers
- Tools
- 1
- the typical server has 7
- Tools that change things
- 0%
- typical: 0%. Fewer write tools means less an agent can break
- Downloads a week
- 200
- more than 75% of 12,191 servers with a package
What its tools let an agent do: 1 read
Release history: 2 versions in the registry since 2026-08-24, latest 2026-09-29, typically one every 36 days.
Install Gam Seller Node in Claude Code, Cursor or VS Code
Runs npx -y gam-seller-mcp-node on your machine. Read the scan report first; the gateway never runs local packages.
claude mcp add gam-seller-mcp-node -- npx -y gam-seller-mcp-node
What the publisher says
From the Gam Seller Node repository's README, as published. We do not edit it. Read it on GitHub
Governed MCP seller control-plane prototype for future GAM integration.
A Model Context Protocol server that exposes sell-side ad inventory to buyer-side AI agents: discovery, firm pricing, and a buyer-scoped soft commitment primitive. No writes to an ad server exist. The Google Ad Manager adapter is not yet connected; catalog and forecast data are synthetic.
What problem does this solve?
Sell-side ad inventory (availability, pricing, product structure) lives inside ad servers that hold commercially sensitive and sometimes personal data. Giving an AI buyer agent direct API access to GAM or a similar system creates three risks:
How it works
A buyer agent connects via MCP and gets five tools — three read-only, plus a buyer-scoped commitment primitive (create/revoke) that is the sole write surface:
Buyer agent
│
├── well_known_capabilities ← Signed trust anchor. Check this first.
│ Returns: RS256-signed capability document, node identity, privacy posture.
│
├── discover_products ← What can I buy here, and at what firm price?
│ Returns: product families the buyer is entitled to see (e.g. "Pre-Roll Video"),
│ each with its firm list price when the publisher has configured one.
│ Never returns: deal IDs, internal IDs, raw inventory, exact per-impression pricing.
│
├── get_forecast ← How available is this family next quarter?
│ Returns: Low / Mid / High availability bucket.
│ Never returns: exact impression counts, CPM curves, floor prices.
│
├── create_intent ← Commit to a product at its current firm price (with TTL).
│ Records a firm, time-boxed buying intent — rejected if the price is stale or
│ mismatched. NOT a GAM order and NOT an inventory hold; it is the handoff artifact
│ the classic sales rails pick up. Buyer-scoped: you can only ever commit as yourself.
│
└── revoke_intent ← Withdraw oneEvery call flows through the same pipeline before any domain logic runs:
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Gam Seller Node: common questions
- Is Gam Seller Node MCP server safe?
- Yes, by our scan: it is graded A (88/100). Read the Gam Seller Node safety report
- How do I install Gam Seller Node?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does Gam Seller Node need an API key?
- No secret keys are declared. It reads 1 setting from the environment.
- Is Gam Seller Node maintained?
- The last commit was 35 days ago (2026-09-29). The latest release is v0.11.1.
- How does Gam Seller Node compare with other MCP servers?
- safety score 88/100 (higher than 75% of 48,255 servers); tools 1 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.