
Georgia Archives MCP server
online · 100% uptimeNational Archives of Georgia MCP — the three catalogues the archives publish.
not scanned yet
0 stars
Reviews
Write oneNobody has reviewed Georgia Archives yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Georgia Archives tools
Tool list not cached yet. `describe` through the gateway fetches it live.
How Georgia Archives compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 77/100
- higher than 50% of 48,255 servers
- Uptime
- 100%
- of our recent checks; the typical remote server answers 100%
- Response time
- 36 ms
- faster than 94% of 30,031 servers
Release history: 6 versions in the registry since 2026-09-14, latest 2026-11-02, typically one every 4 days.
Install Georgia Archives in Claude Code, Cursor or VS Code
claude mcp add --transport http georgia-archives https://gateway.pipeworx.io/georgia-archives/mcp
What the publisher says
From the Georgia Archives repository's README, as published. We do not edit it. Read it on GitHub
@pipeworx/georgia-archives
The three public catalogues of the National Archives of Georgia — the scientific reference library (Koha), the national fonds register, and the Georgian national film catalogue.
Part of Pipeworx — an MCP gateway connecting AI agents to 1576+ live data sources.
Tools
by keyword / title / author / subject. Returns a true total (not a page count) plus 20 records, each with its permanent biblionumber and catalogue URL.
- archiveslibrarysearch(query, index?, offset?) — search the reference library
field/subfield structure plus a flattened summary (title, authors, imprint, ISBN, languages, subjects).
- archiveslibraryrecord(biblionumber) — one record as parsed MARC: the full
pages of 25. Each row carries the holding regional archive, the fond number, the fond name, the historical names it held with their date ranges, and the inclusive dates of its administrative and personnel records.
- archivesfondsbrowse(page?) — walk the fonds register: ~14,650 fonds over 586
newsreels, documentaries and features, with directors and camera operators as {id, name} objects carrying the catalogue's own person ids.
- archivesfilmsearch(name?, page?, locale?) — the film catalogue's 652
Auth
Keyless. Every endpoint answers without a credential.
Data sources
— Koha OpenSearch RSS. is an honest total and &offset=N is honoured, so pagination has a real cursor.
/api/v1/ itself is a keyless Swagger 2.0 spec, 129 paths, 13 of them public.
- — Koha public REST.
catalogue, an Inertia/Laravel app that returns JSON when asked.
- — the fonds register.
- — the film
Things the next person would otherwise rediscover the hard way
Koha's biblio route rejects Accept: application/json with a 400. It requires a MARC media type — application/marc-in-json or application/marcxml+xml. Test it with default headers and you will file a working endpoint as dead.
The fonds register's trailing slash is load-bearing. /fonds?page=2 301s to /fonds/ and drops the query, so you get page 1 back with a 200. Its search is POST-only behind a token CSRF field, and the same parameter names sent over GET are silently ignored* — page 1 again, which reads as a clean zero-result. There is no JSON surface here at all (main.js greps out to jQuery internals, zero endpoints). Browse-and-index is the only honest shape; do not build a search proxy on it.
The film catalogue ignores unknown parameters instead of rejecting them. search=, keyword= and title= all return the unfiltered 652 with a 200. Only name filters. That is why this pack accepts exactly one filter and nothing else — an accepted-but-ignored argument would hand the caller the whole catalogue dressed as a search result.
X-Inertia-Version is a deploy fingerprint, not a constant. Hard-code it and you get a 409 the next time they deploy. currentInertiaVersion() reads it out of the page's data-page attribute on every call, which costs one extra request and cannot go stale.
OAI-PMH is not enabled on the Koha instance (/cgi-bin/koha/oai.pl?verb=Identify → 404), so there is no bulk path; the REST + OpenSearch pair is the whole surface.
Quick Start
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"georgia-archives": {
"url": "https://gateway.pipeworx.io/georgia-archives/mcp"
}
}
}What this endpoint actually serves
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Grade history
- 2026-10-03downgradeA → Bscore 77: Write-action tools reachable without authentication; Unusually long tool description (over 2,000 characters)
- 2026-09-19restoreB → Ascore 87
Georgia Archives: common questions
- Is Georgia Archives MCP server safe?
- Mostly: it is graded B (77/100). Read the Georgia Archives safety report
- How do I install Georgia Archives?
- It runs remotely at gateway.pipeworx.io. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
- Does Georgia Archives need an API key?
- Yes. The registry entry asks for
PIPEWORX_API_KEY. - Is Georgia Archives maintained?
- The last commit was 39 days ago (2026-09-26). The latest release is v0.3.1.
- Is Georgia Archives up?
- 100% of our last 28 checks got an answer. We check remote servers about four times a day.
- How does Georgia Archives compare with other MCP servers?
- safety score 77/100 (higher than 50% of 48,255 servers); uptime 100% (of our recent checks; the typical remote server answers 100%); response time 36 ms (faster than 94% of 30,031 servers). Full comparison.