io.github.koda-ai-studio/agent-bom
agent-bom
Is the agent-bom MCP server down? No. It is up and needs auth (HTTP 401), probed 2026-11-13.
AI supply-chain BOM: agents, MCP servers, packages and recorded reach. Scan and investigate via MCP.
needs auth probed 2026-11-15 · unchanged since 2026-11-13 · HTTP 401 · Bearer
Streamable HTTP error: Error POSTing to endpoint: {"error": "invalid_token", "error_description": "Authentication required"}- Endpoint
- https://agent-bom-mcp.up.railway.app/mcp (streamable-http)
- Host
- agent-bom-mcp.up.railway.app
- Getting access
- OAuth with dynamic client registration. A client such as Claude Code, Cursor or npx mcpcost auth https://agent-bom-mcp.up.railway.app/mcp registers itself and opens the consent page; the publisher has nothing to set up for you.
Authorization server keycloak-production-c86c.up.railway.app, PKCE S256, grants authorization_code, client_credentials, implicit, password, refresh_token.
Scopes read.
Read from the server's public OAuth metadata, without a token. Method. - Repository
- https://github.com/koda-ai-studio/agent-bom
- Registry
- active, updated 2026-11-13 · registry entry
- Changes
- 4 recorded, reachable in 4 of them. A row is added when the result, the tool count or the cost changes.
Compare this server with others.
More servers
Servers that mention studio.
- UGC, the Human Ad Network africa.ugc/ugc · needs auth
- Apatero Studio ai.apatero/studio · needs auth
- AI Media Studio ai.b77/ai-media-studio · needs auth
- Bloopo — AI Ad & Creative Studio ai.bloopo/bloopo · needs auth
- CNAPS.ai MCP Server ai.cnaps/studio · needs auth
- Clip Studio MCP ai.clipstudio/mcp · needs auth
- Context Studios MCP ai.contextstudios/mcp · alive
- ai.corduroy-labs/updates · alive
History
We add a row when the result changes. A server with no change keeps its last row.
| Probed | Result | Init | Tools | Claude | o200k |
|---|---|---|---|---|---|
| 2026-11-04 11:29 | needs auth | ||||
| 2026-11-03 08:39 | alive | 2.4 s | 8 | 7.9k | 4.6k |
| 2026-10-29 07:45 | alive | 3.0 s | 8 | 7.8k | 4.5k |
| 2026-10-23 06:52 | alive | 3.8 s | 8 | 4.3k |
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- The server answers HTTP 401 to an unauthenticated initialize, so the probe cannot list its tools. That is correct for a private server. Some public servers answer initialize and tools/list without credentials and ask for auth on tool calls only; those get a token count here.
Fixed something? Probe it now, with the same steps as the daily run. This page updates with the next daily run.