Tideline

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

Should I use this

Quality & Safety

B
Description quality
100%
Schema completeness
45%
Naming quality
100%
Poisoning risk
100%
Permission match
100%
Protocol compliance
100%

Based on automated analysis of tool definitions and protocol compliance.

Context Cost

~395Tokens (tool definitions)
~294 BTypical response size
Minimal attention impact (0.31% of 128k context)

This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.

Install

One-Click Install

Add this to your `claude_desktop_config.json` file:

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

Remote endpoints

https://tideline.jbpscapital.com/mcpstreamable-http

What it can do

Tool inventory

Tools (4)

🟢 Read-only🟡 Write🔴 Delete⚪ Unknown
🟢get_public_record(days)

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, nothing re-computed.

Input Schema

{
  "type": "object",
  "properties": {
    "days": {
      "type": "integer",
      "minimum": 1,
      "maximum": 260,
      "description": "Number of most recent sessions in the delayed record to return (default 30)."
    }
  },
  "additionalProperties": false
}
🟢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.

Input Schema

{
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
🟢get_verification

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

Input Schema

{
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
🟢get_current_state

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.

Input Schema

{
  "type": "object",
  "properties": {},
  "additionalProperties": false
}

Community

Rate this Server

Evidence

Recent observations

verifiedversion not recorded4 tools