Tideline

npx add-mcp 'https://tideline.jbpscapital.com/mcp'

Any MCP client can read Tideline's public record through a read-only MCP server; Core members connect with a key for the current published state.

In short

• Any AI agent can connect to Tideline through a read-only Model Context Protocol (MCP) server at https://tideline.jbpscapital.com/mcp. Without a key it returns the public record, delayed 30 days; with a Core key it returns the current published state.
• The agent reads the same published model state the member portal shows: market regime, extension, distance to next signal and the model allocation, plus the published history and the fixed vocabulary.
• The server cannot place, route or manage orders and holds no brokerage or account information. What an agent does with the published state is the member's own decision.

Without a key: the public record

Add https://tideline.jbpscapital.com/mcp to any MCP client with no key. Your agent can read the published record with the same 30-day delay as the record page, the fixed vocabulary and the verification feed. Nothing reaches an agent earlier than it reaches the public site.

Tool	Returns
get_public_record	Published daily states and allocation changes, shown with a 30-day delay.
get_definitions	The fixed vocabulary and the publication schedule.
get_verification	The latest ledger fingerprint with its RFC 3161 and OpenTimestamps receipts.
get_current_state	Without a key, explains that the current state is delivered to Core members the evening it is published.

Requests without a key are limited to 30 per minute. The server is listed in the official MCP registry as com.jbpscapital.tideline/tideline.

With a Core key: what your agent can ask

Tool	Returns
get_current_state	The latest published state, its session date and a freshness flag if tonight's publication is still pending. Includes the no-margin line (the same state at a maximum of 1.0× gross exposure).
get_state_history	Previously published daily states, newest first, and the allocation changes among them.
get_definitions	The fixed vocabulary: regime, allocation states and leverage targets, extension, distance to next signal, publication schedule.
get_verification	The latest ledger fingerprint with its RFC 3161 and OpenTimestamps receipts, as on the verify page.

Every Core member receives identical answers on the same schedule. The server adds a delivery channel for the publication; it does not tailor anything to a member's account, holdings or goals.

Connect in three steps

1. Sign in to the member portal and choose Create key under Connect your agent. The key is shown once; copy it.
2. Add Tideline to your client. Apps that take a connector URL (Claude, ChatGPT and similar) use https://tideline.jbpscapital.com/mcp/<your key>. Clients that send headers use https://tideline.jbpscapital.com/mcp with Authorization: Bearer <your key>. The key page shows ready-to-paste settings for Claude Code, Claude Desktop and Cursor.
3. Ask your agent something like "What is Tideline's current published state, and when was it published?"

Keys and security

• One live key per member. Replacing it in the portal disables the old one immediately; so does revoking it.
• Keys are stored only as a one-way hash. If a key is lost, create a new one.
• A key works only while the Core subscription is active. After a cancellation it stops working within a few hours.
• Requests are limited to 60 per minute per key. The state changes at most once per trading day, after the close.

Timing

The model is evaluated after the US close on trading days and the new state is published that evening, US Eastern time. Until then, get_current_state returns the previous session and says that the update is pending. A delayed update does not establish that the model stayed unchanged.

Using the state in automation

Some members wire the published state into their own tools or trading workflows. Tideline does not review, operate or support those workflows, and nothing the server returns is an instruction for any account. The allocation it reports is a hypothetical model allocation; leverage magnifies both gains and losses, and the model can suffer substantial losses and underperform buy-and-hold. Read the guide and the methodology before relying on any published state.