tideline

Tideline, a publication of JBPS Capital LLC, publishes the end-of-day state of a rules-based US equity index model (SPY/QQQ) after the US close on trading days.

Community: Submitted by a user or imported; check the owner before granting accessOnlineNo sign-inGlobalFreeCan modify data

What it can do

  • Get Public Record: Tideline's published end-of-day model states and allocation changes, shown with a 30-day delay (the data of tideline.jbpscapital.com/record). Read-only; published states only, nothi
  • Get Definitions: Fixed definitions of every published field (market regime, allocation states and leverage targets, extension, distance to next signal, signals) and the publication schedule.
  • Get Verification: Latest public ledger fingerprint with its RFC 3161 and OpenTimestamps receipts, and how to verify the record independently.

What data it sees

Do you need an account

No: the server works without sign-in

Tideline, a publication of JBPS Capital LLC, publishes the end-of-day state of a rules-based US equity index model (SPY/QQQ) after the US close on trading days. This read-only MCP server lets an AI agent read what Tideline has published. Without a key it provides the public record, shown with a 30-day delay, the fixed vocabulary, and independently timestamped ledger fingerprints (RFC 3161 and OpenTimestamps). With a Tideline Core key, it provides the current published state the evening it is published, including the no-margin line. The server cannot place, route or manage orders and holds no account data. Tideline is an impersonal publication, identical for every subscriber; it is not individualized investment advice.

How to connect

How to connect tideline to Claude

The server address to paste into Claude settings:

https://tideline--info-ybxt.run.tools

  1. Open Claude (claude.ai or the desktop app).
  2. Go to Settings → Connectors.
  3. Click Add custom connector.
  4. Paste the server address copied below into Remote MCP server URL and click Add.
  5. In a chat, click + → Connectors and switch the new connector on.

Custom connectors are available on Free, Pro, Max, Team and Enterprise plans (Free is limited to one). On Team and Enterprise an organization Owner adds the connector first under Organization settings → Connectors.

Authorization

After you click Add, a sign-in window for the service opens. Sign in with your own account and approve access. Claude never sees your password.

How to connect tideline to ChatGPT

The server address to paste into ChatGPT settings:

https://tideline--info-ybxt.run.tools

  1. Open ChatGPT in a browser (chatgpt.com). A Plus, Pro, Business, Enterprise or Edu plan is required.
  2. Turn on developer mode once: Settings → Apps → Advanced settings → Developer mode.
  3. Open Settings → Connectors and click Create.
  4. Fill in the form: Name (anything), Description (one line about what the service does), MCP server URL (copy it below).
  5. Under Authentication choose OAuth if the service requires sign-in, otherwise None. Click Create.
  6. In a new chat open + → Apps/Connectors and enable the connector.

OpenAI has renamed this section before (Connectors → Apps/Plugins). If the label differs, search settings for "developer mode". On Business/Enterprise workspaces an admin must allow custom connectors first.

Authorization

On first use ChatGPT opens the service's sign-in window. Sign in and approve access.

How to connect tideline to Cursor

The server address to paste into Cursor settings:

https://tideline--info-ybxt.run.tools

Fastest: click Open in Cursor below and confirm the prompt.

Manually:

  1. In Cursor open Settings → Cursor Settings → MCP and click Add new global MCP server.
  2. Paste the JSON copied below into ~/.cursor/mcp.json (per project: .cursor/mcp.json in the repo root).
  3. Save the file. The server appears in the MCP list; authorize it there if asked.

Authorization

If the service needs sign-in, an authorize button appears next to the server in the MCP list.

Server tool list (4)

Raw names from tools/list. Only developers need these.

get_public_recordTideline's published end-of-day model states and allocation changes, shown with a 30-day delay (the data of tideline.jbpscapital.com/record). Read-only; published states only, nothing re-computed.
get_definitionsFixed definitions of every published field (market regime, allocation states and leverage targets, extension, distance to next signal, signals) and the publication schedule.
get_verificationLatest public ledger fingerprint with its RFC 3161 and OpenTimestamps receipts, and how to verify the record independently.
get_current_stateThe current published state is delivered to Tideline Core members the evening it is published. Without a Tideline key this returns how Core access works and where the delayed public record is.