AlgoriQ

ai.algoriqPublished by algoriq.aiOfficial publisherv1.0.0Updated Nov 5, 2026

Run AlgoriQ quant research from any MCP client: data, features, strategies, validation, portfolios.

VerifiedStreamable HTTPWeb executableFinance

Overview

AI-generated overview

AlgoriQ's remote MCP server lets an assistant run quantitative research workflows — data, features, strategies, validation and portfolios — from any MCP client.

What you can do
  • Run quantitative research workflows from an MCP client, covering market data and feature preparation.
  • Build and work with trading strategies.
  • Validate strategies and manage portfolios.
  • The manifest lists no individual tools, so the exact operations available are not documented here.
When to use it
Useful when you want an AI assistant to drive AlgoriQ's quant research pipeline — preparing data and features, developing strategies, validating them and handling portfolios — without leaving the chat client.
Requirements
A remote streamable HTTP endpoint at mcp.algoriq.ai; no local package or runtime is needed. An AlgoriQ account with OAuth sign-in is required. Network access to the endpoint.
Before you install
Access is granted through OAuth to your AlgoriQ account, so the assistant can act within that account's permissions. Research artifacts such as strategies and portfolios may be created or changed. No tool list is published, so review what the server can do before connecting.

Installation

In SourceWeft

  1. Open AlgoriQ in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/ai.algoriq%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "algoriq": {
      "type": "http",
      "url": "https://mcp.algoriq.ai/"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestNov 5, 2026

Score

56% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.