Riksarkivet MCP Server
Related Servers
Alternatives to Riksarkivet MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseAqualityCmaintenanceEnables searching and retrieving historical Swedish portraits, biographies, and printed source references from Svenskt Porträttarkiv, including direct image links and genealogical citations.3-
- FlicenseNot gradedqualityDmaintenanceProvides access to Sweden's National Library (Kungliga biblioteket) open APIs, enabling search and retrieval of 20M+ bibliographic records, 10M+ cultural heritage objects, 2M+ research publications, and linked data through 52 tools across 10 endpoints.2-
- FlicenseNot gradedqualityBmaintenanceEnables querying genealogical records, archive statistics, historical weather, and full-text transcriptions from Open Archives via natural language.7 npm4-
- AlicenseNot gradedqualityAmaintenanceEnables full-text search and retrieval of Kansallisarkisto's machine-transcribed archival corpora, including medieval charters from Diplomatarium Fennicum, with filters and stemming support.Apache 2.0
- AlicenseAqualityBmaintenanceProvides AI assistants with programmatic access to the National Library of Sweden's digitized historical newspapers, enabling full-text search, filtering, timelines, and image retrieval across over 2.2 million pages.51MIT
- AlicenseAqualityAmaintenanceEnables AI agents to search and retrieve consolidated Swedish statutes (SFS) from the Riksdagen open data API, with verifiable citations and persistent identifiers.441 PyPIApache 2.0
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: 'search_transcribed' is for discovering documents via keyword searches, while 'browse_document' is for retrieving full transcriptions of specific pages. There is no overlap or ambiguity between them; each serves a different stage in the document exploration workflow.
Both tools follow a consistent verb_noun naming pattern ('search_transcribed' and 'browse_document'), using snake_case throughout. The verbs 'search' and 'browse' accurately reflect their distinct functions, and the pattern is uniform across the tool set.
With only two tools, the server feels under-scoped for its domain of historical document exploration. While the tools cover search and viewing, there are likely missing operations such as filtering by metadata, listing document collections, or handling user sessions. A typical server in this domain would benefit from 5-10 tools for a more complete surface.
The server provides core search and browse functionality, but there are notable gaps. It lacks tools for document metadata retrieval, collection browsing, or advanced filtering beyond keyword search. Agents can work around this by using the existing tools iteratively, but the surface is incomplete for comprehensive historical research workflows.