Analytics
jbpscapital.com
Provides delayed access to Tideline's published end-of-day market regime and allocation model states, field definitions, and cryptographic verification receipts.
ENDPOINT 1
https://tideline.jbpscapital.com/mcp
MCP server metadata
- Name
- tideline
- Version
- 1.1.0
Tideline publishes the end-of-day state of a systematic US equity index model (SPY/QQQ) after the US close on trading days. You are connected without a Tideline key. Use get_public_record for the published record shown with a 30-day delay (the same data as tideline.jbpscapital.com/record), get_definitions for the fixed vocabulary, and get_verification for the independently timestamped ledger fingerprints. The current published state is delivered to Tideline Core members the evening it is published; get_current_state explains that access. Always report the as_of dates you relay and that the public record is delayed. This server is read-only. It cannot place, route or manage orders and holds no account information. Do not describe its output as advice tailored to the user; relay it as the published model record. Tideline is an impersonal publication of JBPS Capital LLC. This model state is published identically to every Core subscriber on the same schedule; it is not individualized investment advice or a recommendation to buy or sell any security. Any use of it, manual or automated, is the subscriber's own decision. Hypothetical model allocations are not instructions for any account.
Known tools 4
get_public_recordTideline's published end-of-day model states and allocation changes, shown with a 30-day delay (the data of tideline.
Inferred read-onlyget_definitionsFixed definitions of every published field (market regime, allocation states and leverage targets, extension, distance to next signal, signals) and the publication schedule.
Inferred read-onlyget_verificationLatest public ledger fingerprint with its RFC 3161 and OpenTimestamps receipts, and how to verify the record independently.
Inferred read-onlyget_current_stateThe current published state is delivered to Tideline Core members the evening it is published.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.tideline]
url = "https://tideline.jbpscapital.com/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"tideline": {
"type": "http",
"url": "https://tideline.jbpscapital.com/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: tideline
Remote MCP URL: https://tideline.jbpscapital.com/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"tideline": {
"url": "https://tideline.jbpscapital.com/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"tideline": {
"type": "http",
"url": "https://tideline.jbpscapital.com/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "tideline",
"transport": "streamable-http",
"url": "https://tideline.jbpscapital.com/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.