Pairsync

io.github.pairsyncPublished by GitHub account pairsyncv1.0.0Updated Nov 4, 2026

Read-only MCP access to nightly pairs trading cointegration statistics for compatible AI clients.

VerifiedStreamable HTTPWeb executableFinanceData & Analytics

Overview

AI-generated overview

Remote read-only MCP server serving nightly pairs-trading cointegration statistics across six markets, letting an assistant screen pairs and read methodology.

What you can do
  • Screen and rank pairs from the latest nightly refit across US equities, US ETFs, EU, India, Australia and crypto
  • Read a pair's locked parameters, spread z-scores, calibration records and backtest-tracked spread states
  • Freeze parameter recipes and check a frozen list against the latest refit output
  • Generate ready-to-paste chart and code templates for a pair
  • Read the plain-English methodology library and fetch a strategy-builder scaffold with owner-decision slots
When to use it
Useful when you want an assistant to explore pairs-trading statistics, compare candidate pairs, or draft chart and code templates from a maintained nightly dataset, without any execution or order handling.
Requirements
A remote Streamable HTTP endpoint; no local package. Requires a PairSync account and an API key minted on the account page, supplied either through OAuth sign-in or the X-Api-Key header. Rate limit is 300 tool calls per hour per key.
Before you install
You must supply a PairSync API key, which is a credential; keep it in an environment variable rather than in shared config. The statistics are educational and derived from historical market data, not financial advice, and the server has no order path, custody or execution, so any trading decisions and execution remain on your side.

Installation

In SourceWeft

  1. Open Pairsync 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/io.github.pairsync%2Fpairsync/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": {
    "pairsync": {
      "type": "http",
      "url": "https://mcp.pair-sync.com/mcp"
    }
  }
}

README

[PairSync logo]

PairSync

Pairs trading statistics

[Install PairSync in Cursor]

What it does

PairSync refits cointegration statistics every night across six markets (US equities, US ETFs, EU, India, Australia, crypto) and serves the output as ranked pair statistics: spread z-scores, locked parameters, calibration records, and backtest-tracked spread states. Your AI can screen pairs, read a pair's locked parameters, freeze a parameter recipe, generate ready-to-paste chart and code templates, check a frozen list against the latest refit output, read the plain-English methodology library, and fetch a strategy-builder scaffold whose every decision is an owner-decision slot your AI fills by asking you.

  • Server: https://mcp.pair-sync.com/mcp (remote MCP, Streamable HTTP)
  • Tools: 18, all read-only (statistics, templates, methodology library, strategy-builder scaffold, charts)
  • Markets / cadence: US, US ETFs, EU, IN, AU, crypto — one refit per market per night
  • Rate limit: 300 tool calls/hour per key
  • Documentation: https://terminal.pair-sync.com/api

Read-only by design

Every tool is read-only statistics and templates. PairSync has no order path, no custody, no execution, and never manages money — prices, decisions, and execution stay entirely on your side. Anything you choose to freeze or persist is stored on your side; the server keeps nothing.

Get an API key

  1. Sign in (or sign up) at https://terminal.pair-sync.com
  2. Open Settings → API Access
  3. Mint an API key and copy it — you'll paste it into Cursor below

Your credentials stay private: you authenticate with a single PairSync API key minted on your own account page. OAuth tokens are sealed, short-lived envelopes of that key — the server stores no tokens, no sessions, and no personal data.

Connect from Cursor

One-click install (OAuth)

Click the Install in Cursor badge above. Cursor walks you through PairSync's OAuth sign-in — you paste the API key you minted once during authorization, and you're connected.

PairSync's OAuth is standard OAuth 2.1 (RFC 9728 discovery, dynamic client registration, PKCE), so the same zero-config entry works in any OAuth-capable MCP client:

json
{  "mcpServers": {    "pairsync": {      "url": "https://mcp.pair-sync.com/mcp"    }  }}

Manual mcp.json (API-key header)

Prefer a header instead of OAuth? Add this to ~/.cursor/mcp.json (or your project's .cursor/mcp.json) and set the PAIRSYNC_API_KEY environment variable to your key:

json
{  "mcpServers": {    "pairsync": {      "url": "https://mcp.pair-sync.com/mcp",      "headers": {        "X-Api-Key": "${env:PAIRSYNC_API_KEY}"      }    }  }}

Example prompts

  • Show me tonight's leaders in US equities.
  • Screen crypto pairs from the latest refit and explain the top one.
  • Explain the PairSync methodology — where do I start?
  • Check my frozen recipes against last night's refit output.
  • Build me a connector template for this pair with the locked parameters.

What's in this repo

This repository contains only the plugin manifest, MCP configuration, icons, and documentation for the hosted PairSync MCP server — no server source code.

FilePurpose
plugin.jsonAgent Plugins (Open Plugins) manifest
mcp.jsonAgent Plugins MCP configuration (OAuth)
.mcp.jsonCursor/Claude-style MCP configuration (OAuth)
.cursor-plugin/plugin.jsonCursor Marketplace manifest
icons/Logo (dark + light, SVG + 512/256/128 PNG)

Disclaimer

PairSync provides educational statistics derived from historical market data. It is not financial advice and makes no performance claims. Nothing here directs trades or executes anything on your behalf.

Support & policies

License

MIT

Source: README.md at commit bebf535

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 4, 2026

Score

85% 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
  • Documentation15 pts
  • License10 pts