General Tools
historiai.health
Provides search and lookup tools for public domain records, episodes, figures, events, and works.
ENDPOINT 1
https://historiai.health/api/mcp
MCP server metadata
- Name
- historiai-public-record
- Version
- 1.0.0
Read-only public-domain historical record. Carry source_ids and receipt_url or curation_receipt_url where filed; missing receipts, faults, and empty matches are never evidence of historical absence. Historiai stops before starting any later database statement after a deadline, but Cloudflare D1 exposes no portable cancellation handle for a statement already dispatched.
Known tools 13
figure_lookupFind curated people, legendary figures, or deities named in the record.
Inferred read-onlyevent_searchFind curated events by label, with the record's honest date and disambiguation fields, source provenance, and a nullable curation_receipt_url where filed.
Inferred read-onlywork_lookupReturn one served work's bibliographic card and a bounded first page of stable episode addresses; it does not reproduce the whole work.
Inferred read-onlyreceipt_lookupReturn one public receipt with its full checksum, sources, evidence, and explicit what-this-does-not-prove clauses.
Inferred read-onlyepisode_lookupReturn one exact live episode with a bounded verbatim excerpt, canonical work/ref address, source id, and separately labeled episode/work receipt URLs where filed.
Inferred read-onlywork_contentsReturn deterministic cursor pagination over every live episode address in one work; totals, next cursor, truncation, and separate episode/work receipts are explicit.
Inferred read-onlytimeline_lookupReturn curated chronology rungs and deeds in an explicit bounded year range.
Inferred read-onlyperson_lookupReturn one exact curated person identity and its bounded grounded claims, distinct from generic figure/name drawers and source-author labels.
Inferred read-onlywitness_lookupReturn one exact curated source-profile with bounded grounded claims, served works, witnessed deeds, sources, and filed receipts.
Inferred read-onlyhistoriai_reception_ofOpen the curated reception store for one handle — a witness slug, entry slug, or bounded label.
Inferred read-onlyhistoriai_compare_accountsResolve one curated deed (slug or bounded label; several matches return the candidate set with disambiguation notes, never a guess) and serve its curated witness index: every account with role, span, verified verbatim anchor quotes, and per-witness divergence notes, divergence leading.
Inferred read-onlyhistoriai_who_isSearch the curated person register (a pilot slice whose exact size the response states, not antiquity) for the identities under one name.
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.historiai-public-record]
url = "https://historiai.health/api/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"historiai-public-record": {
"type": "http",
"url": "https://historiai.health/api/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: historiai-public-record
Remote MCP URL: https://historiai.health/api/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": {
"historiai-public-record": {
"url": "https://historiai.health/api/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"historiai-public-record": {
"type": "http",
"url": "https://historiai.health/api/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "historiai-public-record",
"transport": "streamable-http",
"url": "https://historiai.health/api/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Trust Data Available
BuiltWith Trust API v2 evidence for historiai.health was fetched 2026-08-03T15:41:30.441Z and is being refreshed.
historiai.health is assessed as Neutral: No suspicious signals found, but no strong positive signal either
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.