Bgg MCP
BGG MCP provides access to BoardGameGeek and a variety of board game related data through the Model Context Protocol. Enabling retrieval and filtering of board game data, user collections, and profiles.
Is Bgg MCP safe? Thin or incomplete trust evidence. Review carefully before production use.
Compare Bgg MCP
How does it stack up against its MCP Servers neighbours?
- Financial Modeling Prep MCP Server +0.2 higher
- Home Assistant Vibecode Agent +0.2 higher
- DexPaprika same score
In detail: Bgg MCP scores 49.1/100 (Grade D), ranked #959 of 1325 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 4.3/10; 24% of recent commits are signed; last pushed 2026-08-20. Every point is earned from checkable signals — never paid placement. How scoring works →
How Bgg MCP compares in MCP Servers
- #552 Financial Modeling Prep MCP Server 49.3 +0.2
- #553 Home Assistant Vibecode Agent 49.3 +0.2
- #554 Bgg MCP 49.1 this agent
- #555 DexPaprika 49.1 ±0
- #556 CometChat Docs 49.0 −0.1
Bars show each HVTrust score; the tick marks Bgg MCP’s 49.1.
Where the 49.1 comes from
HVTrust dimensions vs the MCP Servers average
49.1 / 100 · 100.0% confidenceBgg MCP MCP Servers average (775 agents)
Quick Trust Read
How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade D reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →
Rank Trend
Activity & Reach
Analysis
Activity Inputs
35.9 / 100Supply Chain Trust
Common questions about Bgg MCP
Does Bgg MCP publish package provenance?
Does Bgg MCP have an OpenSSF Scorecard?
Is Bgg MCP actively maintained?
What license does Bgg MCP use?
Are Bgg MCP's commits signed?
Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.
AI agent surface
MCP, providers, tool surface
These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →
- MCP signal live
- External deps live
- Tool / plugin surface live
- Package provenance drift live
Detected changes to Bgg MCP's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.
Maintain Bgg MCP?
For maintainers
HVTrust scores Bgg MCP from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.
Reputation Timeline
Signal history
Embed Badge Badge guide for maintainers →
For maintainers
[](https://hvtracker.net/agents/bgg-mcp)
<a href="https://hvtracker.net/agents/bgg-mcp"><img src="https://hvtracker.net/badge/bgg-mcp.svg" alt="HVTrust"></a>
Other agents in MCP Servers
GitHub REST API (repo, commits, stars, forks, license) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON