Skip to content

BidGlow MCP server

io.github.bidglow-ai/bidglowbidglow-aistreamable-httpv2.0.0Scanned

Publish approved free listings and preview optional bids. No payments.

3 tools: 1 do something that can't be undone and 2 only read.

Tools: 0 delete, 1 irreversible, 0 write, 2 read.
  • Reads private data · 0
  • Reads text others write · 1
  • Can send data out · 1
  • 1 finding

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here does something that can't be undone. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the BidGlow MCP server can do

The BidGlow MCP server is published by the GitHub account bidglow-ai. It has 3 tools. It can do things that cannot be undone, such as sending, paying or publishing (publish_free), but cannot delete data. 2 tools only read.

1 tool brings in text other people can write (publish_free); 1 tool can send data out of your system (publish_free).

The fixed checks matched 1 finding (credentials-mention). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 16, 2026, version 2.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

3 tools

Can't be undone 1Claude Code: ask
  • publish_freeCreates ONE real public free listing after explicit user approval.Reads text others writeCan send data out1 finding

    Why it is in this group

    • The name "publish_free" says "publish": a word for a change that another call does not undo.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe name "publish_free" says "publish": it sends or publishes something to other people.

    Findings

    • Info

      The description mentions "credentials".

      Matched text

      description: "...se contains private reusable management credentials; never print them publicly. Does not ch..."

      What this check looks for
    Description, as the server wrote it
    Creates ONE real public free listing after explicit user approval. Save the supplied UUID and 32-byte secret securely BEFORE calling. Identical retries only. Response contains private reusable management credentials; never print them publicly. Does not charge money.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
Only reads 2Show 2 read-only tools
  • capabilitiesRead current free offer, category IDs and payment boundaries.No findings

    Why it is in this group

    • The description's first verb is "read": a word for reading.
    Description, as the server wrote it
    Read current free offer, category IDs and payment boundaries.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
  • quoteRead-only optional bid quote.No findings

    Why it is in this group

    • The description's first verb is "read": a word for reading.
    Description, as the server wrote it
    Read-only optional bid quote. Creates no payment and reserves no rank.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out1
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:02 UTC, unchanged since Nov 20, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
3
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 3 tools that change things (2 irreversible, 1 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://bidglow.ai/api/mcp: tools/list returned 5 tools to an anonymous client, including publish_and_prepare_usdc_bid (irreversible), publish_free (irreversible), recover_management (write)

    What this check looks for

Posture changes

  1. Nov 20, 2026
    • Tools that change things, listed without credentials: 1 to 3

Findings

Matches of fixed checks, with the text they matched.

1 info
  • The description mentions "credentials".

    Matched text

    description: "...se contains private reusable management credentials; never print them publicly. Does not ch..."

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. Tools that change things, listed without credentials: 1 -> 3.View diff
    • Tools that change things, listed without credentials: 1 to 3

Install

Pinned to version 2.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http bidglow https://bidglow.ai/api/mcp
claude mcp add --transport http bidglow https://bidglow.ai/api/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__bidglow__capabilities",
      "mcp__bidglow__quote"
    ],
    "ask": [
      "mcp__bidglow__publish_free"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as bidglow. Review it before you use it.

Capability tags behind 1 rule
  • mcp__bidglow__publish_free untrusted-input, outbound

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.bidglow-ai/bidglow/verify?hash=69a96f54af245f9e63b73d7e31de8c6b52193366a66bc71ae9a0c24fa11194de" | jq -e '.changed == false'

Pinned hash 69a96f54af24, from Nov 16, 2026, 22:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.bidglow-ai/bidglow/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.bidglow-ai/bidglow
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.bidglow-ai/bidglow.svg)](https://radar.anlyon.com/servers/io.github.bidglow-ai/bidglow)

Source: MCP Registry. Synced Oct 21, 2026, 18:23 UTC.

BidGlow MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the BidGlow MCP server safe?

No scan can promise that. What its definitions show: 3 tools, 1 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the BidGlow MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the BidGlow MCP server do things that cannot be undone?

Yes. 1 tool can send, pay, publish or merge: publish_free.

What tools does the BidGlow MCP server have?

3 tools: 1 irreversible, 2 read. publish_free, capabilities and quote.

Does the BidGlow MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the BidGlow MCP server send data to outside services?

1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): publish_free.

Has the BidGlow MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 16, 2026.