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.

BagIQ MCP

REMOTE · DATA.BAGIQ.APP · SCANNED SEP 26

Analyse disc golf bag gaps and overlap, recommend discs, and open an interactive Bag Map.

Available components

+3 this week 67 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security46
Transport & Reachability100
Schema Quality & AI Usability68
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1009 tokens (~168/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management63
  • Stability observed for 19 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
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 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 BagIQ MCP server?

BagIQ MCP is a hosted endpoint at https://data.bagiq.app/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · data.bagiq.app

# add to Claude Code
claude mcp add --transport http frankbongo-bagiq 'https://data.bagiq.app/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "frankbongo-bagiq": {
      "url": "https://data.bagiq.app/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "frankbongo-bagiq": {
      "type": "http",
      "url": "https://data.bagiq.app/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.frankbongo-bagiq]
url = "https://data.bagiq.app/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "frankbongo-bagiq": {
      "type": "remote",
      "url": "https://data.bagiq.app/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add frankbongo-bagiq --url 'https://data.bagiq.app/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  frankbongo-bagiq:
    url: "https://data.bagiq.app/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "frankbongo-bagiq": {
      "Transport": "http",
      "Url": "https://data.bagiq.app/mcp"
    }
  }
}
# add to Vellum
assistant mcp add frankbongo-bagiq -t streamable-http -u 'https://data.bagiq.app/mcp'
// mcp.json
{
  "mcpServers": {
    "frankbongo-bagiq": {
      "type": "http",
      "url": "https://data.bagiq.app/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

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.

  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 24 Sept 26 +1

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

  • 22 Sept 26 +1

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

  • 20 Sept 26 +1

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

  • 18 Sept 26 +1

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

  • 16 Sept 26 +1

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

  • 14 Sept 26 +1

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

  • 12 Sept 26 +1

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

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 26 Sept 2026 · Probed https://data.bagiq.app/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=bagiq.app CN=WE1,O=Google Trust Services,C=US 11 Sept 2026 10 Dec 2026 ECDSA 256 ECDSA-SHA256 1ca355c9bb26a1ce0e3f767f44c20331
SANs: bagiq.app, data.bagiq.app, *.data.bagiq.app
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of data.bagiq.app. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
app. present 23684 8 Verified
bagiq.app. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://data.bagiq.app/mcp Verified 200
http (plaintext) http://data.bagiq.app/mcp Served over HTTP 200
MCP tools · 6 exposed · ~1,009 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
analyze_bag ~211

Performs a complete BagIQ analysis on a player's disc golf bag. Can accept a list of discs OR a BagIQ share link (e.g. 'https://app.bagiq.app/?s=4fisr8a7'). Returns slot coverage percentage, bag identity label (e.g. 'Overstable-heavy', 'Chaos bag'), top missing shot gaps, redundant overlaps, and mapped flight coordinates.

NameTypeReqDescription
discsarray–List of discs currently in the bag (optional if share_url or share_id is provided)
preferred_brandstring–Optional preferred brand for recommendations (e.g. 'Innova', 'Discraft')
share_idstring–Optional BagIQ short share ID (e.g. '4fisr8a7')
share_urlstring–Optional BagIQ share link (e.g. 'https://app.bagiq.app/?s=4fisr8a7' or 'https://app.bagiq.app/?discs=...')

No output schema declared.

No examples provided.

build_minimal_bag ~152

Extracts an optimal 3-to-5 disc minimalist setup from a larger bag, maximizing shot coverage while detailing necessary compromises. Accepts discs list or a BagIQ share link.

NameTypeReqDescription
discsarray–Full disc collection or bag (optional if share_url or share_id is provided)
share_idstring–Optional BagIQ short share ID (e.g. '4fisr8a7')
share_urlstring–Optional BagIQ share link (e.g. 'https://app.bagiq.app/?s=4fisr8a7')
target_countinteger–Target number of discs in the minimal bag (2..6, default 3)

No output schema declared.

No examples provided.

detect_overlap ~133

Detects redundant molds occupying the same flight slot or shot role, ranking pairs by overlap severity and recommending which disc to keep vs cut. Accepts discs list or a BagIQ share link.

NameTypeReqDescription
discsarray–List of discs in the bag (minimum 2 discs, optional if share_url or share_id is provided)
share_idstring–Optional BagIQ short share ID (e.g. '4fisr8a7')
share_urlstring–Optional BagIQ share link (e.g. 'https://app.bagiq.app/?s=4fisr8a7')

No output schema declared.

No examples provided.

find_bag_gaps ~143

Identifies missing shot shapes and unserved flight slots across BagIQ's 9 core slot targets (putter, midrange, fairway, and distance drivers), ranking voids by severity. Accepts discs list or a BagIQ share link.

NameTypeReqDescription
discsarray–List of discs in the bag (optional if share_url or share_id is provided)
share_idstring–Optional BagIQ short share ID (e.g. '4fisr8a7')
share_urlstring–Optional BagIQ share link (e.g. 'https://app.bagiq.app/?s=4fisr8a7')

No output schema declared.

No examples provided.

get_shared_bag ~163

Retrieves and inspects a player's saved disc golf bag from a BagIQ share link (e.g. 'https://app.bagiq.app/?s=4fisr8a7'), short share ID, or slug link. Returns the full disc breakdown with plastics, wear states, confidence ratings, slot coverage, and interactive BagIQ deep links.

NameTypeReqDescription
share_idstring–BagIQ short share ID (e.g. '4fisr8a7')
share_urlstring–BagIQ share link URL (e.g. 'https://app.bagiq.app/?s=4fisr8a7' or 'https://app.bagiq.app/?discs=innova-destroyer,discraft-buzzz')

No output schema declared.

No examples provided.

recommend_bag_fillers ~207

Suggests the highest-rated discs to fill missing shot slots or close voids in the bag based on BagIQ matrix coordinates and DiscList ratings, with interactive 1-click 'Add to Bag' deep links. Accepts discs list or a BagIQ share link.

NameTypeReqDescription
brandstring–Optional brand filter for recommendations
discsarray–Current bag contents (optional if share_url or share_id is provided)
gap_idstring–Specific gap ID to fill (e.g. 'fairway-understable', 'approach-overstable', 'mid-neutral')
limitinteger–Number of recommendations per gap (1..5, default 3)
share_idstring–Optional BagIQ short share ID (e.g. '4fisr8a7')
share_urlstring–Optional BagIQ share link (e.g. 'https://app.bagiq.app/?s=4fisr8a7')

No output schema declared.

No examples provided.

Common questions

What is the BagIQ MCP server?

BagIQ MCP is listed in the public MCP registry as io.github.frankbongo/bagiq. Analyse disc golf bag gaps and overlap, recommend discs, and open an interactive Bag Map. This page covers its hosted endpoint (https://data.bagiq.app/mcp).

Is the BagIQ MCP server safe to use?

BagIQ MCP scores 67 out of 100 on VerifyMCP. 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 BagIQ MCP server expose?

BagIQ MCP exposes 6 tools: analyze_bag, find_bag_gaps, detect_overlap, recommend_bag_fillers, build_minimal_bag, get_shared_bag. Their descriptions and schemas cost roughly 1,009 tokens of context every time the server is loaded.

Does the BagIQ MCP server require authentication?

No. We connected to BagIQ MCP without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the BagIQ MCP server still maintained?

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