Skip to content
Discussion options

You must be logged in to vote

First check the destination. Your installation's /mcp is the authenticated investigation endpoint; https://bicho.fyi/mcp serves public documentation only. Use a Streamable HTTP client that initializes the protocol and can send a custom bearer header. Bicho does not implement OAuth.

For an installation connection, requests need Authorization: Bearer <admin-token>, Content-Type: application/json, and Accept: application/json, text/event-stream. Both Accept media types are required even though responses use JSON. Let the MCP transport negotiate the protocol-version header.

The status narrows the problem:

  • 401: missing or invalid admin credentials. Ingest keys cannot authenticate MCP.
  • 503: th…

Replies: 1 comment

Comment options

You must be logged in to vote
0 replies
Answer selected by zapalblizh
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants