mcp-registry/io.github.bidglow-ai/bidglow · v2.0.0
As of 2026-10-17 10:11 UTC, the Bidglow Ai Bidglow MCP server is up with a Glimind reliability score of 86/100 (grade B). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 2 outages in 90 days, with a median recovery of 7 minutes.
Publish approved free website listings and prepare read-only bid quotes. No payment tool.
Claude Code
claude mcp add --transport http bidglow-ai-bidglow-mcp-server https://bidglow.ai/api/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"bidglow-ai-bidglow-mcp-server": {
"type": "http",
"url": "https://bidglow.ai/api/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
11 parameter(s) across 2 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call.
Handshake + tools/list takes ~2,824 ms.
Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.
In the last 30 days: 1 tool(s) removed and 0 schema change(s).
Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts.
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably.
Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.bidglow-ai/bidglow"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.github.bidglow-ai/bidglow"}) over MCP.
publish_free ~258 tokensquote ~132 tokenscapabilities ~56 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fio.github.bidglow-ai%2Fbidglow?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.github.bidglow-ai%2Fbidglow?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.bidglow-ai%2Fbidglow.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.bidglow-ai%2Fbidglow.svg :target: https://glimind.com/server/mcp-registry%2Fio.github.bidglow-ai%2Fbidglow?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:eb6cd047f80dad45…, first seen 2026-10-17, included at leaf 13518 of 17,378. Version history · verify what your client received.
Compare: most reliable other servers · most reliable communication servers · most reliable finance servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-17 10:11 UTC, the Bidglow Ai Bidglow MCP server is up with a Glimind reliability score of 86/100 (grade B). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 2 outages in 90 days, with a median recovery of 7 minutes.
Bidglow Ai Bidglow MCP server advertises 3 tools, including capabilities, publish_free, quote.
Point your MCP client at this streamable-http endpoint: https://bidglow.ai/api/mcp
Glimind scanned all 3 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.