Tideline

com.jbpscapital.tidelinePublished by tideline.jbpscapital.comOfficial publisherv1.3.0Updated Oct 29, 2026

Published end-of-day state of a rules-based SPY/QQQ index model. Read-only. Free tier: 90-day delay.

VerifiedStreamable HTTPWeb executableFinanceData & Analytics

Overview

AI-generated overview

Read-only remote MCP server that relays Tideline's published end-of-day states for a rules-based SPY/QQQ index model, delayed 90 days without a key.

What you can do
  • Read the published end-of-day model states and allocation changes, delayed 90 days on the free tier
  • Look up fixed definitions of published fields such as market regime, allocation states, extension and signals, plus the publication schedule
  • Retrieve the latest public ledger fingerprint with its RFC 3161 and OpenTimestamps receipts and verification steps
  • Check how current-state access works for Tideline Core members, since the current state is not returned without a key
When to use it
Useful when you want an assistant to relay or explain Tideline's published model record, its field vocabulary and its timestamped ledger proofs, for example when reviewing the delayed public record or checking how the record can be verified independently. It is not a source of live signals or account-level guidance.
Requirements
A remote streamable HTTP endpoint; no local package or runtime. An optional Authorization header carrying a Bearer Tideline Core key from the member portal unlocks the current published state; without it the server returns the public record delayed 90 days. Network access to the endpoint is required.
Before you install
The Authorization header carries a secret Tideline Core key; keep it private. Output is a delayed, impersonal publication of a hypothetical model, not individualized investment advice or an instruction to trade, and any use is the user's own decision. The server is read-only and holds no account information, so it cannot place or manage orders. Always report the as_of dates and the delay when relaying data.

Installation

In SourceWeft

  1. Open Tideline in the dashboard and add it to a workspace.
  2. 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/com.jbpscapital.tideline%2Ftideline/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.

{
  "mcpServers": {
    "tideline": {
      "type": "http",
      "url": "https://tideline.jbpscapital.com/mcp"
    }
  }
}

Tools

4

get_public_record

Public record (90-day delay)

Tideline's published end-of-day model states and allocation changes, shown with a 90-day delay (the data of tideline.jbpscapital.com/record). Read-only; published states only, nothing re-computed.

Parametersdays

get_definitions

Vocabulary and publication schedule

Fixed definitions of every published field (market regime, allocation states, extension, distance to next signal, signals) and the publication schedule.

Takes no parameters.

get_verification

Ledger fingerprints and timestamps

Latest public ledger fingerprint with its RFC 3161 and OpenTimestamps receipts, and how to verify the record independently.

Takes no parameters.

get_current_state

Current published model state (Core)

The 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.

Takes no parameters.

Version history

3
  1. v1.3.0LatestOct 29, 2026
  2. v1.2.0Sep 29, 2026
  3. v1.1.0Sep 24, 2026

Score

83% 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 listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • 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.