AI supply-chain BOM: agents, MCP servers, packages and recorded reach. Scan and investigate via MCP.
Connect Remote server
claude mcp add --transport http agent-bom https://agent-bom-mcp.up.railway.app/mcp --header "Authorization: Bearer <YOUR_API_KEY>"
{
"mcpServers": {
"agent-bom": {
"url": "https://agent-bom-mcp.up.railway.app/mcp",
"headers": {
"Authorization": "Bearer <YOUR_API_KEY>"
}
}
}
}
{
"servers": {
"agent-bom": {
"type": "http",
"url": "https://agent-bom-mcp.up.railway.app/mcp",
"headers": {
"Authorization": "Bearer <YOUR_API_KEY>"
}
}
}
}
Settings > Connectors > Add custom connector
URL: https://agent-bom-mcp.up.railway.app/mcp
Replace the values in angle brackets with your own. Keys stay on your machine; we never see them.
Tools
This server asks for a key before it lists its tools. Connect it with your own key to see them.
Headers
| Name | Description |
|---|---|
AuthorizationOptional, secret | Optional. Without it, only the read-only lookup tools (check, intel_lookup) answer. A deployment bearer token unlocks the rest. |
Details
| Endpoint | https://agent-bom-mcp.up.railway.app/mcp (Streamable HTTP) |
| Package | [email protected] (PYPI, stdio) |
| First published | 13 Nov 2026 |
| Last updated | 13 Nov 2026 |
| Registry name | io.github.koda-ai-studio/agent-bom |
More ai and media servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.
