# com.jyotishintelligence/sealed-forecasts

Bitcoin-anchored sealed-forecast record: search, grades, calibration, luck test. Read-only, no key.

- **Type:** MCP server
- **Trust:** 60/100 (B), scored on the content rubric
- **Verification:** community-indexed — nobody has claimed this listing
- **Version:** 1.1.0
- **Author:** com.jyotishintelligence
- **License:** Unknown
- **Endpoints:** streamable-http https://jyotishintelligence.com/mcp
- **Source:** https://jyotishintelligence.com/api
- **Endpoint health:** reachable (last checked 2026-09-12T11:15:48.330Z, 4 samples) — uptime is not a security property and is not part of the trust score
- **Compatible clients:** claude-code, cursor, copilot, chatgpt, gemini (basis: transport)

## Trust

60/100 (B), scored on the content rubric
- Publisher verified: no
- Install scripts: nothing suspicious found
- Prompt-injection scan: clean
- Obfuscation scan: clean
- Evidence age: 0 days

## Security scan

- **Status:** clean
- **Scanned:** 2026-09-12T11:15:48.330Z
- **Version scanned:** live
- **CVEs:** no coverage — this entry has no package coordinates to query OSV against, so "no known CVEs" is NOT asserted for it.

## Tools

13 declared. Observed from a live `tools/list` probe.
- `search_sealed_forecasts` — Search the JYOTINT sealed-forecast corpus (Bitcoin-anchored, dated-before-the-event predictions) by free text across id, title, and the verbatim sealed claim. R
- `get_advisory` — 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 
- `list_open_calls` — List sealed forecasts whose window has NOT yet resolved — predictions on the public record that haven't happened yet (anteriority you can watch).
- `get_calibration_and_integrity` — Return the corpus calibration (Brier score, counts) and the integrity proof (manifest hash, ledger hash, confirmed Bitcoin block heights, and how to independent
- `get_map` — 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 i
- `ask_the_record` — 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, nev
- `neural_search` — SEMANTIC + ASSOCIATIVE search over the public sealed record and the published site corpus — the JYOTINT public brain (a neural associative memory: frozen deep e
- `get_information_yield` — 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-
- `get_warning_timeline` — 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'
- `get_regrade_kit` — The grade-it-yourself kit: inputs to recompute the record's Brier (calibration), named-mechanism specificity, AND Information Yield under YOUR OWN verdicts — pl
- `get_luck_test` — The corpus-level 'could this record be luck?' significance test, computed AGAINST the record: EVERY graded call clustered into independent events (correlated ca
- `get_corpus_insights` — The deep-pass signature findings over the FULL corpus (graded + ungraded + excluded), cross-checked against the ledger at build time: the MECHANISM LEDGER (the 
- `get_governance` — Return JYOTINT's data-handling, PROVENANCE & governance posture — the answer to 'is this source safe to read / cite / ingest?'. Chain-of-custody is foregrounded

## Install

**Verdict: review** — Installable, but 2 things to check first: No CVE coverage: this entry has no npm/PyPI coordinates to query OSV against, so "no known vulnerabilities" is not a claim that can be made about it.
**Cautions** (coverage gaps and advisories — never blocking)
- No CVE coverage: this entry has no npm/PyPI coordinates to query OSV against, so "no known vulnerabilities" is not a claim that can be made about it.
- No publisher has proved control of this listing; it is indexed, not vouched for.
**Config** (claude-code):
```json
"{\n  \"mcpServers\": {\n    \"sealed-forecasts\": {\n      \"type\": \"http\",\n      \"url\": \"https://jyotishintelligence.com/mcp\"\n    }\n  }\n}"
```

## Blast radius

Contained to moderate — no credential declaration found, from the publisher, the upstream registry, or the README. Known so far: runs on someone else's infrastructure; read-only tool surface.
- Floor 9, ceiling 27 (tier: unknown)
- `unknown` means the floor and ceiling land in different bands — not measured enough to name one. It does not mean low.
- This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score.

## Machine-readable views of this entry

- Signed JSON: https://forgeregistry.com/api/v1/packages/com.jyotishintelligence%2Fsealed-forecasts
- Install plan: https://forgeregistry.com/api/v1/packages/com.jyotishintelligence%2Fsealed-forecasts/install-plan
- Alternatives: https://forgeregistry.com/api/v1/alternatives/com.jyotishintelligence%2Fsealed-forecasts
- HTML page: https://forgeregistry.com/registry/com.jyotishintelligence%2Fsealed-forecasts
- MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan`

## About this document

Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.