Altifigence MCP Status#

Check the current state of the local MCP process, hosted endpoint, OAuth flow, and client support.

Overview#

Altifigence has two distinct MCP surfaces. The CLI archive contains a local stdio process, while mcp.altifigence.com is a hosted Streamable HTTP endpoint with OAuth. The hosted endpoint publishes discovery and authorization metadata, but it cannot initialize an MCP session or list tools yet.

Local Stdio and Hosted HTTP Are Different#

Surface	Where transport runs	Current status
Packaged `alti-mcp` / CLI MCP process	A child process on the user’s machine using stdin/stdout	Startup requires the CLI environment configuration; listed tool calls dispatch through the CLI Cloud client
`https://mcp.altifigence.com/mcp`	Hosted protected HTTP route	Bearer challenge and OAuth metadata are active, but standard MCP initialization and tool listing do not complete

“Local MCP” means that the MCP process communicates with the client over stdio on the same machine. Individual tools may still use a remote service or send data online. The packaged process does not make the unavailable hosted MCP endpoint or the missing CLI installation report available.

Do not copy tokens into a client configuration to work around an unavailable tool runtime.

Current Endpoint State#

Endpoint	Current state
`https://mcp.altifigence.com/healthz`	Online health response
`https://mcp.altifigence.com/mcp`	Protected Streamable HTTP route; bearer challenge active
`https://mcp.altifigence.com/.well-known/oauth-protected-resource/mcp`	Protected-resource metadata available
`https://mcp.altifigence.com/.well-known/oauth-authorization-server`	Authorization-server metadata available
`https://mcp.altifigence.com/register`	Dynamic client registration route for approved public clients
Client ID metadata document	Not supported

Use /mcp as the transport path. The site root redirects only GET and HEAD; posting an MCP initialization request to the root does not provide a compatible fallback.

Why Hosted MCP Is Not Available#

The current protected route does not complete standard MCP initialize or tools/list. OAuth metadata and registration succeeding would therefore not produce a usable customer connection or tool catalog.

Client Support#

Client	Current status
ChatGPT	Setup not available while initialization and tool discovery are missing
Codex	Loopback callback shape is accepted; setup is not available while initialization and tool discovery are missing
Claude Code	Setup not available while initialization and tool discovery are missing

There is no supported client setup to copy yet. This page will add one after the hosted endpoint can authorize a client, initialize a session, list tools, and complete a read-only call.

Security#

OAuth is enforced on the protected route. Do not paste an access token into a client as a workaround for the missing runtime methods.