DOCUMENTATION / API & MCP
OAuth sign-in verified / test tools nextConnect an AI agent with MCP
Give an agent scoped report and price-watch tools.
- Runs on
- Our hosted service
- Before you start
- A compatible OAuth MCP client and your account consent
On this page
Add the remote MCP server
Add the hosted endpoint as an OAuth/HTTP MCP server. Leave API-key and bearer-token fields empty. Current Codex clients detect OAuth and start authorization; opening the URL in a browser alone does not connect a client.
https://10signals.xyz/mcpAuthorize your account
Sign in if needed, then approve the client's consent page. For an already-added Codex server, run codex mcp login 10signals --scopes reports:read. Keep it running and open its fresh authorization link if no browser opens. Codex 0.144.1 failed before consent; 0.157.1 starts OAuth on add, and the desktop 0.158.0-alpha.2.1 completed consent in our test. Website sign-in alone does not authorize MCP. No API key is needed.
Start read-only
Ask your agent to call account_status and reports_list, then report_get and report_matches_list for an owned report. Empty history is valid for a new account. These checks must not create reports or watches.
List my reports and show one report's comparison evidence. Do not create a report or enable any price watches.Control paid work explicitly
report_create_preview shows the current plan's comparison count and allowance impact; only report_create_confirm starts work. price_watch_preview shows product/rival scope, cadence and credits; only price_watch_confirm activates. Keep the same token for an uncertain retry. Disable the test watch with price_watch_disable. Tokens expire after five minutes; obtain a new preview if impact changes or the token expires.
Run the no-cost diagnostic
From the source candidate, this Node.js command checks public metadata and the unauthenticated 401 challenge. It does not log in, access your data or call paid tools. A successful check is not proof of client compatibility.
node scripts/check-mcp-connection.mjsYou should see discovery: available; authentication: required; clientLoginTested: false; toolsTested: false.
Revoke the test connection
Remove the OAuth connection from the hosted Account → Connected apps and verify access fails. API keys are separate and must be revoked separately.
Open hosted connected apps