Skip to content

Supported AI apps and tested clients

Current support

Connect an AI app to https://mcp.argusfa.com/mcp. The website's Connect page has the steps for each app.

AI app or client How it connects Status
Claude (claude.ai, Claude Desktop, Claude mobile) Custom connector at the MCP address, signed in with OAuth. Claude is registered in advance. Tested end to end on production on 2026-11-12, release 1.1.30: a custom connector called all 20 consumer tools.
Other hosted AI apps, including ChatGPT, Claude Code, Cursor and Gemini CLI Not registered in advance. Sign-in is refused until Argus registers the app. Not verified end to end. Write to [email protected] and name the app.
Argus CLI with its Codex and Claude Code Skill The Argus CLI's own client, registered in advance, over REST Tested in isolated measurements; see the history below. The CLI reaches the registry tools, not the consumer tools.
Python MCP SDK The MCP address with the session of argus auth login --interface mcp; see MCP Tested in isolated measurements; see the history below.

Only Claude is registered in advance among hosted AI apps. Any other hosted app is refused at sign-in until Argus registers it; no setting on the user's side works around that. A user of a hosted app never handles a Client ID: the app uses the registration Argus made for it. The MCP resource can also accept a host that identifies itself by a client metadata document, but only from a list of reviewed hosts that is empty today (ADR 0015).

A connected app uses Memory and Holdings only after the owner allows them for that app in the Argus web app. A private tool that is refused for that reason answers with a link to the app's own switches on the account security page.

Personal signup does not register an OAuth client. A third-party client lacking verified session binding can be withdrawn only at its supported client/account boundary; a display label does not create stronger isolation. Background account authorization is independent of a short-lived login and ordinary logout; pause or delete the subscription or explicitly withdraw background authority to stop it.

Measurement history

This history describes measured clients, not a hosted-platform certification. The isolated baseline is dated 2026-10-23 and was reviewed on 2026-10-28. It was measured with package 1.1.26 and registry v19 (production now serves agent-tool-registry-v20), Python MCP SDK 1.30.0 and httpx 0.28.1. A later candidate repeated the documented CLI, REST and Python MCP examples and the ordinary-owner browser workflows, with a real AAPL daily-price replay, same-owner four-interface checks and browser checks for the twelve languages then shipped; the application now ships six of them (ADR 0008). These isolated checks retain captured source terms and require an explicit development validation grant for positive delivery; they do not establish production source rights or hosted support. Later production checks include selected CLI, REST and MCP fact, filing, bookmark and download paths; they do not establish that every ordinary-owner or hosted-client scenario passed.

These measurements predate requirements 3.0. The OAuth MCP endpoint now lists up to 20 consumer tools, depending on the connection's grants. Only the Claude row covers them: it records a check on production on 2026-11-12, not one of the isolated measurements.

Client / version or environment Access and measurement Read/write authority Revocation granularity
Argus CLI 1.1.26 + official Codex/Claude-code Skill, Python 3.12 / Windows Actual generated CLI command tree and HTTP against a disposable runtime; no claim that either external host was installed or approved OAuth API-resource session; signed fact/private scopes and current domain consent; identical JSON request file for personal tools Registered CLI installation/session; client or all authorizations via trusted account flow. Local logout only clears that device's credentials.
Python MCP SDK from the committed uv.lock, local companion on Python 3.12 / Windows ClientSession and Streamable HTTP initialize, discovery, actual calls and protected downloads Separate MCP audience; signed scopes and active domain consent; current grants rechecked on an open connection Registered companion session/client, per-domain withdrawal, or all authorizations. No physical-device or arbitrary hosted-session granularity claim.
httpx client from uv.lock, Python 3.12 / Windows Actual REST HTTP and OpenAPI-generated paths API audience, same core and private domain rules; no private rights from a legacy fact scope Registered session/client and domain consent; all revocation requires the trusted owner flow.
Independent personal application, Chromium / Windows Real self-registration and login, durable document acceptance and native owner forms; browser baseline in twelve languages then (six shipped since ADR 0008) and a renewed-acceptance regression Secure owner session, explicit grants; recent verification for sensitive actions Current web session, client, individual domain or all authorizations. Registered activity is not an online-device indicator.
Claude custom connector (hosted Claude), production release 1.1.30, 2026-11-12 A custom connector at the production MCP address signed in with OAuth as a registered client and called all 20 consumer tools. No one-click support claim or dynamic client registration Signed scopes and the owner's current domain consent; the connection lists only the consumer tools its grants allow Remove the connector in Claude and withdraw the client or the domain consent in the Argus account. No hosted session or device revocation was measured.
ChatGPT hosted connector, Codex hosted connector; version/environment not measured Not tested as hosted products; no one-click support claim or dynamic client registration No private permission implied by discoverability or a published Skill No unmeasured hosted session/device revocation promise. Use only an independently registered and verified client.

The concrete MCP client is the Python SDK local companion, not an anonymous protocol fixture advertised as a hosted product. The official Skills describe interface use; they do not certify a host's consent UX or secret storage.

The pinned SDK's recommended Streamable HTTP configuration uses 30-second connect/write/pool timeouts and a 300-second SSE read timeout. Supplying a custom generic HTTP client with a 30-second read timeout can terminate a large complete source response before delivery. Preserve the SDK's transport defaults and handle an explicit request deadline; do not treat an abandoned SSE read as a successful tool result. The measurements verify functional delivery of the complete captured ETF packages; they do not replace latency or load criteria.

Read the executable examples and the session protocol.