Connect your AI

Your first conversation #

After connecting, say Hi Ultron or let’s use Ultron. Ultron opens a connection form inside an MCP Apps-compatible AI client. Enter each key once. Connect saves it and checks supported market/wallet providers using the approved read budget, then continues the AI automatically where the host supports messages. Failed saves retain the field for retry; failed verification does not require re-entering a saved key. X/Apify paid research still requires its separate approval. If external setup is necessary, the secure setup handoff uses the existing connection without another wallet login; finishing signals the original open AI panel to resume. Provider signup pages still open externally. Unsupported clients keep a secure website fallback.

Start with Blockscout for ranked token holders and top-holder supply concentration. Create a free key at dev.blockscout.com, save it with an approved daily read budget, then test access. Holder analysis includes contracts and burn addresses and uses total supply, not circulating supply. Trader setup also offers CoinGecko for market history, Alchemy for wallet history, Apify for clips and X for recent conversation data. Base prices and explicit wallet balance reads need no extra key. Save optional keys in the secure form; approve the Alchemy daily read limit or each paid social request. Builder setup offers relevant infrastructure guidance.

With your agreement and setup-management permission, save_ultron_setup remembers your choices in your account. Read-only clients can use the current conversation without claiming persistent changes. Use Claude Cowork scheduled tasks and its phone notifications. In ChatGPT Work or another AI, use the equivalent native scheduling and notification features when available. Keep setup and interactions inside your AI. Ultron does not offer separate phone pairing, a notification app, Telegram or Discord.

One MCP endpoint #

Ultron exposes Streamable HTTP MCP at the endpoint below. A compatible host can discover its tools, authenticated builder resources and trading playbook. Connection support depends on your client, plan, workspace settings and administrator policy.

https://ultrontrading.app/mcp

Connect with OAuth #

In your AI client's connector or remote-MCP settings, add the endpoint. Where OAuth is supported, follow the browser authorization step, sign in with MetaMask, Phantom or another compatible installed EVM wallet and review the scopes. Use your normal wallet-enabled browser for sign-in. If an embedded browser cannot load the wallet, Ultron prepares a fresh visible handoff link with Open and Copy actions. Keep the original AI login attempt open so it can receive the callback. A website cannot force a host app to open external links in a particular browser; the copyable link remains available. Computer-use access is not required for the user to approve sign-in. Return to your AI client once authorization completes.

Read access enables research. Account-operation access enables intentional watches and preferences. Provider-key management is a separate connections:write permission for the embedded form. Existing connectors must reconnect once and approve that permission to edit keys inside the AI. It does not grant wallet spending or paid-social approval. A separate research:approve scope enables explicit reviewed paid requests in the workspace.

Use a scoped access key #

For clients supporting authorization headers, create a Ultron access key in your workspace and use it as the Bearer credential. Store it in your client's secret configuration, not a chat message or a committed repository. The key is shown once and can be revoked.

Do not put a key in the endpoint URL. The example is a generic HTTP-client configuration; consult your client's current documentation for the exact settings format.

{
  "url": "https://ultrontrading.app/mcp",
  "headers": { "Authorization": "Bearer <ULTRON_ACCESS_KEY>" }
}

Check the connection #

Ask your agent to call assistant_capabilities and network_status. You should see Robinhood Chain ID 4663 and the current coverage. For building, start with get_builder_capabilities. A saved endpoint alone does not prove that authentication or tool execution succeeded.

Claude and ChatGPT use the tools through their own compatible connector features.

Choose your AI #

Claude and ChatGPT support custom remote MCP connections on supported plans and settings. Cursor and Codex support remote MCP. Kimi connects through Kimi Code; this is not a claim that every Kimi chat interface accepts connectors.

DeepSeek can power an MCP-capable agent such as Cline. Gemini connects through Gemini CLI. These are client/protocol compatibility routes, not claims that every provider client has been end-to-end certified with Ultron.

Connect from Chrome, Safari or an embedded AI browser #

A browser with MetaMask, Phantom or another compatible EVM wallet can sign in directly. If no wallet is detected, open the wallet sign-in link in your normal wallet-enabled browser. Keep this original AI sign-in window open.

Copy the generated approval link into a browser with MetaMask or Phantom, or scan the QR code on the HTTPS site to approve in Phantom on your phone. The external browser only approves your wallet and access request; it does not open the client callback.

After approval, Ultron completes the OAuth return in the original AI browser. The handoff expires after five minutes and can be cancelled. If the AI client itself has cancelled or timed out its login, start a fresh connection there.

No trade or spending permission is granted. You may alternatively create a scoped access key and store it in the client’s credential settings.

Does Ultron need my computer password? #

No. Ultron signs you in using wallet ownership and never needs your Mac login, Keychain or wallet-unlock password. Native client or OS prompts are separate and must be handled by you, never pasted into chat.

Agents should use the client’s existing authenticated MCP connection. They must not run the macOS security command, scrape credential stores or extract saved OAuth tokens to test Ultron. If the native connector is unavailable, use its settings or reconnect normally. Ultron cannot suppress the host operating system’s legitimate credential prompts.

Keys inside your AI #

Ask Ultron to open its connection form. API keys are sent directly from the form to Ultron’s encrypted backend over HTTPS, not as chat messages or model-visible tool arguments. Claude receives connection status updates. The form session expires after 20 minutes and stops working if the original connector grant is revoked.

An older or read-only connector can view status but cannot edit keys. Reconnect with provider-key management permission, or use the secure website fallback. Do not paste secrets into ordinary chat. Paid X/Apify requests can be reviewed in the research workspace with research:approve permission; the website remains a fallback.