The read-only hosted MCP endpoint is https://api.oddswire.io/mcp. It exposes bounded data and account-observation tools through the same API permissions and metering.
Connect with OAuth
Use an existing Oddswire owner/admin workspace with its active API key.
Add the server URL in your MCP host’s custom connector settings and choose OAuth.
Complete the Oddswire Clerk sign-in and review consent. The tool scope is profile; no client secret is needed for the supported public-client flow.
List the tools and run
get_usage, which is free, before deliberately requesting an approved data page.
OAuth does not reveal, create or rotate the workspace key. Signup or consent does not grant data. See the current MCP connection guide for tested ChatGPT and Claude setup and namespace selection.
API-key hosts
A host that supports Streamable HTTP and custom headers can use the documented Bearer API-key configuration. Store the key in the host’s private secret configuration, never in a conversation, URL or tool argument.
Calls, limits and credits
Each tool makes at most one API attempt. There is no automatic retry, pagination or price polling. Usage/coverage reads are free; eligible data pages can consume credits. An output-size rejection may happen after a charged API response. Preserve returned missing reasons and timestamps.
To withdraw consent, disconnect the host and revoke its authorization. Previously issued tokens can remain valid until expiry; account membership and active-key revocation also govern subsequent calls.