JYOTINT Sealed Forecasts
Server Details
Bitcoin-anchored sealed-forecast record: search, grades, calibration, luck test. Read-only, no key.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 13 tools
Most tools target distinct operations: individual record lookup, open-call listing, keyword vs neural search, map, governance, timeline, and site-record Q&A. The main overlap is among the analytical/verification tools (calibration/integrity, corpus insights, information yield, luck test, regrade kit), but their descriptions provide enough discriminating cues for most agent queries.
Nine of thirteen tools use a predictable get_* pattern, and list_open_calls and search_sealed_forecasts follow a clear verb_noun style. The deviations—neural_search (adjective_noun) and ask_the_record (imperative phrase)—are readable but keep the naming from being fully uniform.
Thirteen tools is well-scoped for a read-only forecast corpus with retrieval, search, calibration, provenance, governance, visualization, and regrade needs. Each tool appears to earn its place rather than bloating the surface.
The server covers the full read-only lifecycle: discovery (list/search/neural/map), retrieval (advisory, warning timeline), verification (calibration/integrity, seal hashes), interpretation (insights, information yield, luck test, regrade kit), and governance. No create/update/delete is expected for a sealed public record, and no obvious dead ends are apparent.
Available Tools
13 toolsask_the_recordARead-onlyIdempotentInspect
Ask any question about JYOTINT / Vijay Jyotish and get back the most relevant VERBATIM passages of the operator's own published site copy — never generated, never paraphrased, so it cannot hallucinate. This is the operator answering in his own words, drawn only from the public record (method, doctrine, the five pillars, mission-assurance fit, objections, pricing, heritage, etc.). Prefer this for any 'what does JYOTINT say about X' / 'why' / 'how does it work' question. Each passage cites its source page. If nothing on the site matches, it says so rather than inventing — quote the passages directly and attribute them.
Inputs: query (required), limit, sensitivity.
get_advisoryARead-onlyIdempotentInspect
Fetch one sealed forecast by its id (e.g. 'IA-RU-008', 'LA-011', 'IA-MKT-002'). Returns the full record incl. verbatim claim, grade, outcome, sources, and seal hash.
Inputs: id (required).
get_calibration_and_integrityARead-onlyIdempotentInspect
Return the corpus calibration (Brier score, counts) and the integrity proof (manifest hash, ledger hash, confirmed Bitcoin block heights, and how to independently verify it). ALSO returns record_versions: the record is append-only, so if a publication cited a count/Brier that no longer matches the live count, that is expected (calls were sealed since) — resolve the paper's exact cited state by record count or hash via record_versions and recompute the immutable frozen snapshot.
Inputs: no named parameters.
get_corpus_insightsBRead-onlyIdempotentInspect
The deep-pass signature findings over the FULL corpus (graded + ungraded + excluded), cross-checked against the ledger at build time: the MECHANISM LEDGER (the failure class named at seal vs the realized anomaly, all 23 launch calls, GO calls included — the direction varies with the day), the WAR READ (the Russia-Ukraine corpus as one 8-chapter campaign read, PARTIALs owned in-line), the entity-level NAMED-BEFORE-THE-EVENT register, the TWO WARNINGS Crocus x Vaishno-Devi pairing (graded anteriority + delivered actionability), the score-refuses integrity counterfactual, and the delivered-to-defenders routing lane. Caveats ship in the same object — quote them with the findings.
Inputs: no named parameters.
get_governanceARead-onlyIdempotentInspect
Return JYOTINT's data-handling, PROVENANCE & governance posture — the answer to 'is this source safe to read / cite / ingest?'. Chain-of-custody is foregrounded: every record is SHA-256-sealed + Bitcoin-anchored before the event and independently recomputable (the provenance the proposed GSA AI data-safeguarding rule treats as first-class). Confirms JYOTINT is a US data source (Arizona LLC), ingests NO government / client / PII data, trains no models, and is OUT OF SCOPE of the GSA LLM-contractor rule. Descriptive disclosure, not a certification. Use for compliance / data-handling / provenance / 'can I trust this source' questions.
Inputs: no named parameters.
get_information_yieldARead-onlyIdempotentInspect
Information Yield (IY) — how much a confirmed call should move a skeptic's belief, in BITS of surprise-if-true (log2 of the published 1-in-N prior, capped at 1-in-a-million; earned = surprise × verdict-credit). A base rate / consensus-follower scores ZERO bits by construction — the metric on which the 'a base rate ties the Brier' objection inverts. Returns the corpus summary (LIVE median bits/call + %earned — read the numbers from the response, never from this description), the launch/intel/combined domain split, and the count. Pass an optional id for one call's bits.
Inputs: id.
get_luck_testARead-onlyIdempotentInspect
The corpus-level 'could this record be luck?' significance test, computed AGAINST the record: EVERY graded call clustered into independent events (correlated calls share one event; live counts ship in the response), strict scoring (one NEAR fails the whole event), luck-prior floored at a coin flip per event. Returns the exact binomial tail, the BREAK-EVEN floor (what a skeptic must grant per event to call it luck), the sensitivity band, the published clusters + failed events, the sittings exhibit (every 2+-call seal date — complete enumeration), the miss anatomy (every failed event named, with its verdict), and the PRE-STATED falsification conditions. Caveats ship in the same object — quote them with the numbers. Measures improbability-of-luck, never calibration skill (the aggregate Brier's base-rate tie stays disclosed).
Inputs: no named parameters.
get_mapARead-onlyIdempotentInspect
Return an EMBEDDABLE LIVE MAP of the sealed-forecast corpus as an MCP-UI resource. Clients that can render UI resources (mcp-ui) should display it inline — it is the actual interactive JYOTINT theater map (sealed forecasts plotted by region; each pin carries its verbatim claim, grade, sealed probability, and a click-through to the full sealed record so the user can verify and score it themselves). Use this when a user asks to see, visualize, or explore JYOTINT's forecasts on a map.
Inputs: no named parameters.
get_regrade_kitARead-onlyIdempotentInspect
The grade-it-yourself kit: inputs to recompute the record's Brier (calibration), named-mechanism specificity, AND Information Yield under YOUR OWN verdicts — plus the one-step stress-test recipes (harsh-verdicts, externally-adjudicated-only, estimative-worst-case, …). Each call carries its verbatim claim/outcome, the operator's p + verdict to override, and the surprise_bits / 1-in-N inputs. A base rate scores 0 on specificity and 0 bits on IY. Pass an optional id for one call's row; omit for the recipes + usage + count.
Inputs: id.
get_warning_timelineARead-onlyIdempotentInspect
The 'before-the-event' indications-and-warning / after-action timeline for a named event, by advisory id (e.g. 'LA-022') or slug (e.g. 'new-glenn-ng3', 'crocus'). A neutral chronology: the official/authoritative source named FIRST, then the dated, hash-anchored JYOTINT sealed call as one independently-verifiable entry, with what it does and does not establish. Use for 'what dated public warnings preceded [event]'. Omit id to list every available timeline.
Inputs: id.
list_open_callsARead-onlyIdempotentInspect
List sealed forecasts whose window has NOT yet resolved — predictions on the public record that haven't happened yet (anteriority you can watch).
Inputs: no named parameters.
neural_searchARead-onlyIdempotentInspect
SEMANTIC + ASSOCIATIVE search over the public sealed record and the published site corpus — the JYOTINT public brain (a neural associative memory: frozen deep encoder → Hopfield pattern completion → spreading activation over typed synapses → k-winners-take-all). Finds calls by MEANING, not keywords ('upper-stage anomalies' finds the calls that describe one without those words) and returns the RELATED subgraph, not just isolated hits. Retrieval-only and non-generative: every result is VERBATIM sealed/published text with public provenance (source URL, SHA-256 seal hash, frozen grade) plus an explainable why/activation path and Hopfield convergence info. Prefer this over search_sealed_forecasts for fuzzy/conceptual queries; the REST twin is GET /brain?q=…
Inputs: query (required), k, sensitivity.
search_sealed_forecastsARead-onlyIdempotentInspect
Search the JYOTINT sealed-forecast corpus (Bitcoin-anchored, dated-before-the-event predictions) by free text across id, title, and the verbatim sealed claim. Returns matching records with their grade, sealed probability, seal date, source artifact, and SHA-256 seal hash. For fuzzy or conceptual queries, use neural_search (finds calls by MEANING; REST twin GET /brain?q=…).
Inputs: query (required), limit, graded_only, sensitivity.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Sealed prediction-market verdicts, graded in public across Polymarket and Kalshi. No auth required.
Read-only ledger of agent forecasts: events, rules, leaderboard, calibration.
Forecast real-world questions, keep a vault, get scored in public.
Signed, independent scores and claim checks for decentralised AI projects. Read-only, no auth.
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceEnables clients to search, read, and verify sealed forecasts and public-record cards, inspect resolution calendars, engine strands, sensor alerts, and wire headlines, and check whether stories are independent events or echoes. All access is read-only and requires no key, account, or dependencies.4 npm1Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables users to record probabilistic judgments in an immutable ledger, automatically score them against outcomes, and analyze systematic biases across six classification layers. It supports natural-language interaction for logging predictions, checking randomness, and auditing data integrity while avoiding advice or replacing user judgment.Apache 2.0
- AlicenseAqualityBmaintenanceEnables users to check institutional forecasts against actual outcomes, compare economic releases and earnings estimates to results, inspect prediction-market prices and leaderboards, and retrieve archived pages and news to see what was said at the time.71MIT
- FlicenseNot gradedqualityCmaintenanceGraded trading signals and market analysis for FX, crypto, sports, and prediction markets, with a public machine-graded track record. Free track-record and quote tools; paid tools via API key or per-call x402 USDC-
Glama MCP Gateway
Add one secure layer between your agents and this server.