MCP discovery page

GET

/mcp-bot

const url = 'https://example.com/api/mcp-bot';
const options = {method: 'GET'};

try {
  const response = await fetch(url, options);
  const data = await response.json();
  console.log(data);
} catch (error) {
  console.error(error);
}

curl --request GET \
  --url https://example.com/api/mcp-bot

Returns the JSON discovery document (server name, version, POST endpoint, and — when unauthenticated — the authorization-server metadata URL) so an agent that lands here learns how to connect instead of seeing a bare 401. Requesting Accept: text/event-stream asks for the 2025-era standalone notification stream, which stateless serving does not provide: that is answered 405.

Responses

200

Discovery document

application/json

object

required

boolean

data

required

object

name

required

string

version

required

string

protocol

required

string

auth_required

required

boolean

tools_available_after_auth

boolean

discovery

required

object

next_step

required

string

endpoint

required

string format: uri

authorization_server

Present only on the unauthenticated response.

string format: uri

401

Not authenticated

application/json

object

error

required

Human-readable error message

string

code

Stable machine-readable error code for client branching

string

fieldErrors

First validation message per field path

object

key

additional properties

string

issues

Structured validation issues (Zod)

Array<object>

object

path

required

string

message

required

string

retryAfter

Seconds until rate limit resets (429 responses)

number

reconnect

True if re-linking GitHub may fix the issue

boolean

405

No standalone notification stream. Stateless serving has no session to attach one to; modern clients receive notifications on the subscriptions/listen response instead.