MCP Readiness Checks#

Inspect the live health and OAuth metadata without attempting an unsupported customer connection.

Overview#

You can inspect the public health and OAuth metadata. Do not start a customer connection yet: the current protected route cannot complete MCP initialization or tool discovery.

Safe Public Checks#

Bash
curl --fail https://mcp.altifigence.com/healthz
curl --fail https://mcp.altifigence.com/.well-known/oauth-protected-resource/mcp
curl --fail https://mcp.altifigence.com/.well-known/oauth-authorization-server

These responses show that the edge and discovery documents are online. They do not test MCP initialization, tool discovery, or a tool call.

Do Not Configure a Client Yet#

The transport path is https://mcp.altifigence.com/mcp, but the current runtime stops before MCP initialization and tool discovery. There is no supported client configuration or shared client ID yet.

Credential Safety#

  • Do not paste an Altifigence access token into an MCP configuration.

  • Do not commit OAuth codes, tokens, cookies, or AI-provider credentials.

  • Do not disable client approval or server certificate checks.

  • A 401 bearer challenge means authentication is enforced; it does not mean the tool runtime is available.