OpenHeritage Public Search

io.github.OpenHeritageOnline由 GitHub 账号 OpenHeritageOnline 发布v2.11.3更新于 Oct 24, 2026

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

已验证Streamable HTTP可网页运行网页搜索与抓取知识与记忆

概览

AI 生成的概览

匿名、只读的远程 MCP 服务器，用于检索 OpenHeritage 公开的乌克兰族谱与文化遗产记录。

可以做什么
  • 跨实体类型检索公开记录，包括纪念档案、墓地、来源、文献、资料库、作者与合集
  • 按关键词与语义检索文献页面的转录文本，每条结果链接到对应页面
  • 按文本、前缀、类型或附近坐标查找并自动补全规范地名，可选按日期解析历史背景
  • 按稳定 ID 读取单个规范地名
适用场景
适合助手需要查找乌克兰的纪念档案、墓穴、墓地或档案文献记录，或定位历史地名，作为族谱与文化遗产研究的线索来源。
运行要求
通过 Streamable HTTP 连接的远程 MCP 端点；公开检索无需 API 密钥或账号。需要能访问 OpenHeritage 服务的网络。
安装前请注意
检索结果只是线索，不能作为身份或亲属关系的证据；应尊重记录可见性与版权，避免爬取或批量枚举记录。该 MCP 服务器不接受 Personal API 令牌，也不应向其发送用于另一套 Personal API 的令牌。

安装

在 SourceWeft 中

  1. 打开 控制台中的 OpenHeritage Public Search，将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Web executable，通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。

交给智能体安装

把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体，或 SourceWeft 对话中。智能体会读取该服务器的安装指南，先向你展示发布者、端点和登录方式，经你同意后再把它添加到你的客户端。密钥不会写进任何命令。

阅读 https://sourceweft.com/mcp/io.github.OpenHeritageOnline%2Fpublic-search/install.md，并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前，先告诉我它的发布者、端点和登录方式，等我确认。不要把 API 密钥写进命令或我会提交的文件；问我密钥应从哪里获取。

查看智能体所依据的安装指南

其他 MCP 客户端

把它添加到你客户端的 mcpServers 配置中。

{
  "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.

来源：README.md，提交 c9f6ed4

工具

13

search_collections

Search public OpenHeritage collections by text.

输入参数query必填

search_memorials

Search public memorial records by text.

输入参数query必填

find_places_nearby

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

输入参数datetakelatitude必填radiusKmtypeCodelongitude必填

search_sources

Search public sources by text.

输入参数query必填

search_records

Search public OpenHeritage records across supported entity types.

输入参数query必填entityTypes

search_documents

Search public source documents by text.

输入参数query必填

get_place

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

输入参数dateplaceId必填

search_cemeteries

Search public cemeteries by text.

输入参数query必填

search_authors

Search public person and organization author authority records by text.

输入参数query必填

search_repositories

Search public source repositories by text.

输入参数query必填

search_places

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

输入参数datequery必填latituderadiusKmtypeCodelongitudehasCoordinates

autocomplete_places

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

输入参数datetakequery必填typeCode

search_page_text

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

输入参数query必填semanticsourceIddocumentId

版本历史

1
  1. v2.11.3最新Sep 16, 2026

评分

已满足适用检查项的 90%

该评分衡量此收录条目的完整程度，依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价，也不表示服务器安全或当前可用：可连通性是带日期的检查结果，评分也不包含安装量或用户评价。

  • 近 30 天内可连通必需25 分
  • 已声明认证方式必需10 分
  • 已列出工具必需15 分
  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分

    请在仓库或注册中心条目中声明许可证。