FreedomOS MCP API
API by FreedomOS · rest
FreedomOS has one HTTP API: its MCP server (Model Context Protocol, Streamable HTTP transport) at https://getfreedomos.com/api/mcp. Each request is one JSON-RPC 2.0 message sent by POST. The server speaks MCP protocol version 2024-11-05, which initialize returns. Each tool's arguments are described by its inputSchema in tools/list. Every message to this endpoint needs a bearer token: a request without one answers 401 with the sign-in challenge, so MCP hosts start sign-in. To read the tool catalog before signing in, send initialize, tools/list, and the notifications/initialized notification to the directory listing URL https://getfreedomos.com/api/mcp/directory instead. The token comes from either: - FreedomOS sign-in (OAuth 2.0 authorization code with PKCE S256 and dynamic client registration). The authorization server is named in the RFC 9728 metadata at https://getfreedomos.com/.well-known/oauth-protected-resource/api/mcp, and the 401 answer points there in its…
Endpoint: https://getfreedomos.com/
Verification: observed. Source: crawl.
Capabilities (1)
- Send one MCP JSON-RPC message