tideline
https://tideline.jbpscapital.com
Registry code: 2be49491c853390b
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 90-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…
- endpoint
- https://tideline.jbpscapital.com/mcp
- protocol
- streamable-http ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is tideline live?
- Yes — it answered the hub's last check (checked 1h ago). It answered 99% of checks over the last 30 days.
- Is tideline free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does tideline have?
- 4 tools: get_public_record, get_definitions, get_current_state, get_verification.
- Is tideline safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 98.6%· all time 98.6%
last good check
of 4 tools
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- degraded → live
- live → degraded· timeout after 20000ms
- used for
- read a systematic equity model record
- get model field definitions
- verify ledger fingerprints
- takes → gives
- text → data
- tools
- 4 reads
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
get_public_record reads open 16h ago
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.
{ "type": "object", "properties": { "days": { "type": "integer", "maximum": 260, "minimum": 1, "description": "Number of most recent sessions in the delayed record to return (default 30)." } }, "additionalProperties": false }arguments 12 linesget_definitions reads open 24h ago
Fixed definitions of every published field (market regime, allocation states, extension, distance to next signal, signals) and the publication schedule.
{ "type": "object", "properties": {}, "additionalProperties": false }arguments 5 linesget_current_state reads open 24h ago
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.
{ "type": "object", "properties": {}, "additionalProperties": false }arguments 5 linesget_verification reads open 24h ago
Latest public ledger fingerprint with its RFC 3161 and OpenTimestamps receipts, and how to verify the record independently.
{ "type": "object", "properties": {}, "additionalProperties": false }arguments 5 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id2be49491c853390b.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/2be49491c853390b/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/2be49491c853390b?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.