MCP server for the Open Archives genealogical search engine.
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"io-github-coret-openarchieven-mcp-server": {
"command": "<see-readme>",
"args": []
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
MCP server for the Open Archives genealogical search engine.
No automated test available for this server. Check the GitHub README for setup instructions.
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
No package registry to scan.
This server is missing a description. Tools and install config are also missing.If you've used it, help the community.
Add informationBe the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in search
Production ready MCP server with real-time search, extract, map & crawl.
Web and local search using Brave Search API
Multi-engine MCP server, CLI, and local daemon for agent web search and content retrieval — skill-guided workflows, no API keys.
mini cli search engine for your docs, knowledge bases, meeting notes, whatever. Tracking current sota approaches while being all local
MCP Security Weekly
Get CVE alerts and security updates for io.github.coret/openarchieven-mcp-server and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
Production-grade hybrid MCP + HTTP + SSE server generated from the Open Archives OpenAPI specification.
OpenAPI source used to generate tools:
../api/openapi.yaml (local)
https://api.openarchieven.nl/openapi.yaml (remote)
A schema-aware server that automatically converts the OpenAPI specification into callable tools and exposes them through multiple transports:
A hosted endpoint is available — no installation required.
In claude.ai or Claude Desktop:
https://mcp.openarchieven.nl/No authentication is required — Open Archives is a public dataset.
Once the connector is added you can ask Claude, for example:
Claude will call the matching tool (search_records, show_record,
get_marriages, get_historical_weather, get_census_data, …) and
return links to the corresponding record pages on
https://www.openarchieven.nl.
If you prefer running the server locally as a stdio MCP server:
npx -y @coret/openarchieven-mcp-server
Every API operation becomes a tool automatically via generate.ts.
All 17 operations:
| Tool Name | Description |
|---|---|
search_records | Search genealogical records |
show_record | Show a single genealogical record |
match_record | Match a person to birth and death records |
get_births_years_ago | List births from N years ago |
get_births | Find birth records |
get_deaths | Find death records |
get_marriages | Find marriage records |
get_archives | List all archives with statistics |
get_record_stats | Record count per archive |
get_source_type_stats | Record count per source type |
get_event_type_stats | Record count per event type |
get_comment_stats | Comment count statistics |
get_family_name_stats | Family name frequency |
get_first_name_stats | First name frequency |
get_profession_stats | Profession frequency |
get_historical_weather | Historical weather from KNMI |
get_census_data | Dutch census data 1795–1899 |
Note: The
callback(JSONP) parameter present in the upstream API is excluded from all tools — it is irrelevant in an MCP/JSON-RPC context.
Uses actual OpenAPI parameter schemas. Validates:
POST / ← canonical public endpoint (mcp.openarchieven.nl)
POST /mcp ← local / legac
... [View full README on GitHub](https://github.com/coret/openarchieven-mcp-server#readme)