JBPS Capital MCP server

• Registry namecom.jbpscapital.tideline/tidelineverified in the MCP registry

The registry name sits under jbpscapital.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

• Stateanswerschecked 2026-10-24
• Tools4
• Server calls itselftideline
• Server version1.2.0
• Protocol version2025-06-18

On 2026-10-24 the server answered initialize and tools/list without a sign-in. First answer in 73 ms.

• Its tools do none of the product's use cases we checked: test trading ideas with walk-forward validation; check hypothetical backtest results against a question list.
• Checked on 3 of the 7 days it takes to judge reliability.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

• INITE MCP scoreafter a weeka score needs 7 daily checks: 3 so far
• What an agent can do with it0 of 2 use cases
• Answeredmeasuring3 of the 7 daily checks it takes to print a share
• Median first answer96 ms
• Space in an agent's context≈ 331 tokensthe definitions of all its tools (4), which an agent carries on every turn
• Tool definitionsA · 100 of 100
• Typed results0 of 4 toolsdeclared outputSchema: results come typed, read once

• Every tool passes all six checks.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

• get_public_record

  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.

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

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