OpenHeritage Public Search

io.github.OpenHeritageOnlinePublished by GitHub account OpenHeritageOnlinev2.11.3Updated Oct 24, 2026

Read-only OpenHeritage search for genealogy and cultural heritage records.

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingKnowledge & Memory

Overview

AI-generated overview

Anonymous, read-only remote MCP server for searching OpenHeritage's public Ukrainian genealogy and cultural-heritage records.

What you can do
  • Search public records across entity types, including memorials, cemeteries, sources, documents, repositories, authors and collections
  • Search transcribed document page text by keyword and meaning, with each hit linking to its page
  • Look up and autocomplete canonical places by text, prefix, type or nearby coordinates, optionally with historical context for a date
  • Read a canonical place by its stable ID
When to use it
Useful when an assistant needs to find Ukrainian memorial, grave, cemetery or archival document records, or to locate historical places, as discovery leads for genealogy and heritage research.
Requirements
A remote MCP endpoint over Streamable HTTP; no API key or account is needed for public search. Network access to the OpenHeritage service is required.
Before you install
Search results are discovery leads, not proof of identity or family relationship; respect record visibility and copyright, and avoid crawling or bulk-enumerating records. The MCP server never accepts a Personal API token, and tokens for the separate Personal API must not be sent to it.

Installation

In SourceWeft

  1. Open OpenHeritage Public Search in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.OpenHeritageOnline%2Fpublic-search/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "openheritage-public-search": {
      "type": "http",
      "url": "https://openheritage.online/mcp"
    }
  }
}

README

OpenHeritage agent tooling

Public, cross-agent integration files for OpenHeritage, a collaborative genealogy and cultural-heritage platform.

OpenHeritage brings together Ukraine's largest public collection of memorial, grave, and archival document data.

This repository connects compatible AI agents to OpenHeritage in three complementary ways:

  • a remote, anonymous, read-only MCP server for live public-record search;
  • seven portable Agent Skills with domain guidance, safe REST fallbacks, and canonical OpenHeritage links;
  • a documented Personal API for user-authorized contributions with scoped bearer tokens.

No API key is required for public search.

Ukrainian heritage data at scale

  • Memorials and graves: discover memorial profiles, grave sites, cemetery records, cemetery photographs, map locations, and transcriptions.
  • Archival documents: search repositories and sources, retrieve digitized documents by page or original file, and use XML, transcriptions, parsing, or OCR to answer questions with provenance.

These records are connected through canonical OpenHeritage pages, so agents can move from a discovery lead to the relevant cemetery, memorial, source, or document without treating search results as proof.

MCP endpoint

text
https://openheritage.online/mcp

The endpoint uses MCP Streamable HTTP and exposes:

  • search_records
  • search_memorials
  • search_cemeteries
  • search_sources
  • search_documents
  • search_repositories
  • search_places
  • search_authors
  • search_collections

The MCP server also exposes anonymous, read-only resources for selected public sources, documents and files, repositories, collections, canonical places, memorials, cemeteries, and Source classification tags. MCP never accepts a Personal API token.

Use the root .mcp.json with clients that support project or plugin MCP configuration.

Personal API and imports

Use the Personal API only for user-authorized contributions:

  • interactive reference: https://openheritage.online/api-docs;
  • OpenAPI 3 document: https://openheritage.online/api/openapi/v1.json.

Personal API tokens are bearer tokens and always include api:read. A generic catalog-only Source import uses api:sources; adding SourceDocuments, original files, page images, or PAGE XML also uses api:documents. A Source is valid without documents when no digital representation is available. The openheritage-source-import skill explains repository references, Authors, classification tags, coverage dates and places, and optional document ingestion.

A classified newspaper import additionally uses api:authors to create or update the canonical newspaper organization authority, api:sources to create issue Sources and configure the automated Collection, and api:documents to create the issue document and upload ordered page images and PAGE XML. Send the token only in the Authorization: Bearer ... header, never to MCP or in a URL.

The openheritage-newspaper-import skill contains the complete issue workflow. It resolves the environment-specific UUID for stable Source taxonomy code record-kind-newspaper, creates or reuses the newspaper organization Author, configures an Author-driven Collection grouped by publication year, records the holding repository and publication place when known, creates each issue as a publication, and uploads its ordered document pages and PAGE XML. Standalone newspaper clipping PhotoAssets remain part of openheritage-photos.

Add OpenHeritage to your agent / Додайте OpenHeritage до свого агента

English

Use the MCP connection for live, public OpenHeritage search. Add the skills as well when you want your agent to receive focused guidance for memorials, graves, archival documents, historical photos, and genealogy research.

Codex

bash
codex mcp add openheritage --url https://openheritage.online/mcpnpx skills add OpenHeritageOnline/agent-tooling

Gemini CLI

bash
gemini mcp add --scope user --transport http openheritage https://openheritage.online/mcpgemini skills install https://github.com/OpenHeritageOnline/agent-tooling

Claude Code — install the complete plugin, which includes both the MCP server and skills:

bash
claude plugin marketplace add OpenHeritageOnline/agent-toolingclaude plugin install agent-tooling@openheritage

If you only need live search in Claude Code, use this instead:

bash
claude mcp add --transport http --scope user openheritage https://openheritage.online/mcp

Start a new chat after installation. In an open Claude Code session, run /reload-plugins after installing the plugin. Do not install both the Claude plugin and its separate MCP entry unless you intentionally want duplicate configuration.

Українською

Підключіть MCP, щоб агент міг шукати публічні записи OpenHeritage у реальному часі. Додайте також навички, якщо хочете, щоб агент отримав спеціальні інструкції для роботи з меморіалами, могилами, архівними документами, історичними фотографіями та генеалогічними дослідженнями.

Codex

bash
codex mcp add openheritage --url https://openheritage.online/mcpnpx skills add OpenHeritageOnline/agent-tooling

Gemini CLI

bash
gemini mcp add --scope user --transport http openheritage https://openheritage.online/mcpgemini skills install https://github.com/OpenHeritageOnline/agent-tooling

Claude Code — встановіть повний плагін: він містить і MCP-сервер, і навички.

bash
claude plugin marketplace add OpenHeritageOnline/agent-toolingclaude plugin install agent-tooling@openheritage

Якщо в Claude Code потрібен лише пошук, використайте натомість:

bash
claude mcp add --transport http --scope user openheritage https://openheritage.online/mcp

Після встановлення почніть новий чат. Якщо ви встановили плагін у вже відкритій сесії Claude Code, виконайте /reload-plugins. Не встановлюйте одночасно плагін Claude та окремий запис MCP, якщо навмисно не хочете дублювати конфігурацію.

Claude Code

Add the public OpenHeritage marketplace, then install the complete plugin:

bash
claude plugin marketplace add OpenHeritageOnline/agent-toolingclaude plugin install agent-tooling@openheritage

Connect only the MCP server:

bash
claude mcp add --transport http --scope user openheritage https://openheritage.online/mcp

To load the complete plugin from a checkout:

bash
claude --plugin-dir /path/to/agent-tooling

The repository includes a Claude Code manifest at .claude-plugin/plugin.json.

Codex and other Agent Skills clients

Install the portable skills from GitHub with a compatible Agent Skills installer:

bash
npx skills add OpenHeritageOnline/agent-tooling

The repository also includes a Codex manifest at .codex-plugin/plugin.json. Plugin-aware hosts can load the repository checkout directly and use its bundled .mcp.json.

Every Agent Skills-compatible host can also discover the seven published skills from the OpenHeritage Agent Skills index. For an MCP host without plugin support, add the openheritage entry from .mcp.json to its user or project MCP configuration.

Skills

SkillBest for
openheritageBroad searches across all public OpenHeritage domains
openheritage-archivesSources, documents, repositories, collections, pages, files, entries, and exports
openheritage-source-importCatalog-only Sources and optional SourceDocument ingestion with repository, Author, tag, date, and place provenance
openheritage-newspaper-importComplete newspaper issue preparation, organization Authors, automated year Collections, repository and publication-place provenance, ordered page uploads, PAGE XML, verification, and repair
openheritage-photosHistorical photos, media variants, photo maps, corrections, and people on photos
openheritage-memorialsMemorials, cemeteries, cemetery photos, maps, statistics, and exports
openheritage-researchesPublic genealogy research projects, questions, hypotheses, places, and evidence

The same versioned skill documents are also published from the OpenHeritage website:

MCP Registry

server.json publishes the remote server as io.github.OpenHeritageOnline/public-search in the official MCP Registry. The GitHub Actions workflow publishes it when an mcp-v* tag is pushed:

bash
git tag mcp-v2.11.3git push origin mcp-v2.11.3

The workflow uses GitHub OIDC, so it requires no stored token or domain-verification private key. Registry versions are immutable: bump server.json before creating a later tag.

Publishing is restricted to protected release refs and the mcp-registry-production GitHub Environment. The publisher is downloaded from an exact release, verified by SHA256 and Sigstore identity, and checked for the expected version and source commit before the OIDC-capable job can run. See the required repository controls before creating a release tag.

Safety

  • Treat search results as discovery leads, not proof of identity or family relationship.
  • Respect record visibility and copyright restrictions.
  • Do not crawl, bulk-enumerate, or collect profile/contact data.
  • Prefer canonical OpenHeritage pages when sharing results with a user.
  • Use authenticated or mutating REST workflows only when the user explicitly requests them.
  • Never print, persist, or forward a Personal API token; request only the scopes needed for the authorized operation.

Source of truth

The production skill documents are maintained in the main OpenHeritage application repository under sources/FrontendServer/AgentSkills/. Keep the copies in skills/ byte-for-byte synchronized when releasing a new version.

Source: README.md at commit c9f6ed4

Tools

13

search_collections

Search public OpenHeritage collections by text.

Parametersqueryrequired

search_memorials

Search public memorial records by text.

Parametersqueryrequired

find_places_nearby

Find active canonical places near coordinates, optionally resolving historical context for a date.

ParametersdatetakelatituderequiredradiusKmtypeCodelongituderequired

search_sources

Search public sources by text.

Parametersqueryrequired

search_records

Search public OpenHeritage records across supported entity types.

ParametersqueryrequiredentityTypes

search_documents

Search public source documents by text.

Parametersqueryrequired

get_place

Read a canonical place by stable ID, optionally resolving its historical context for a date.

ParametersdateplaceIdrequired

search_cemeteries

Search public cemeteries by text.

Parametersqueryrequired

search_authors

Search public person and organization author authority records by text.

Parametersqueryrequired

search_repositories

Search public source repositories by text.

Parametersqueryrequired

search_places

Search active canonical places by text and optional geographic or type filters.

ParametersdatequeryrequiredlatituderadiusKmtypeCodelongitudehasCoordinates

autocomplete_places

Autocomplete active canonical places by prefix, optionally resolving historical context for a date.

ParametersdatetakequeryrequiredtypeCode

search_page_text

Search the transcribed text of public document pages, by keyword and meaning; each hit links to its page.

ParametersqueryrequiredsemanticsourceIddocumentId

Version history

1
  1. v2.11.3LatestSep 16, 2026

Score

90% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.