Local Markdown library of the papers an evidence review cites: metadata, abstract and full text
Its author marked it deprecated in the MCP Registry
Nothing to run from here
AHG Archives is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
93/100
tool-list score
16
tools declared
remote
at its publisher
—
calls last 7d
What it does
Search and read AtoM archival catalogues with citable links; staff propose changes for review.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http ahg-archives-mcp https://mcp.theahg.co.za/public/mcp
# 2 — ask your agent for something these tools do
# search_records, list_catalogues, get_record and 13 more
AHG Archives costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
THAll 1 server
theahg1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http ahg-archives-mcp https://mcp.theahg.co.za/public/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
16 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Search archival descriptions (fonds, series, files, items) by keyword. Returns title, level of description and the citable URL of each match. Use get_record on a result for the full description. catalogue: leave empty for the home catalogue, give a name from list_catalogues, or "all" to search every catalogue at once (results grouped by catalogue). Every read tool takes the sa
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | — |
| limit | integer | no | — |
| skip | integer | no | — |
| catalogue | string | no | — |
The catalogues this service can search and read. Proposals go to the home catalogue only.
No parameter schema on file.
Read one archival description in full, by its slug (the last part of its URL). Includes dates, names, subjects, places, notes and, where the catalogue provides them, its place in the hierarchy, its number of children, images, and its provenance chain (owners, dates, transfers, certainty, gaps).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | — |
| catalogue | string | no | — |
List the descriptions directly below one record (for example the series in a fonds).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | — |
| limit | integer | no | — |
| skip | integer | no | — |
| catalogue | string | no | — |
Work through every record below a parent (for example each page of a family Bible), a batch at a time, with a running summary of what you proposed where. Returns a batch of the parent's children, each with your proposals on it so far by status, the totals for the whole batch, how many proposals you may still make this hour, and next_skip for the next batch (null when done). Fo
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | — |
| limit | integer | no | — |
| skip | integer | no | — |
Read an authority record (a person, family or organisation) by its slug.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | — |
| catalogue | string | no | — |
Find existing authority records (people, organisations, families) or places by name. Every word must appear in the name, in any order, so "Hendrik Engelbrecht" also finds "Engelbrecht, Hendrik". Use it before proposing a name or place: when one of the results is the same person, organisation or place, pass its id as existing_id in propose_access_points_and_dates, so the archivist
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | — |
| kind | string | no | — |
| limit | integer | no | — |
| catalogue | string | no | — |
Return the IIIF manifest URL for a record's images, for viewing in a IIIF viewer.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | — |
| catalogue | string | no | — |
Read the text held for a record's files: text extracted from a PDF or by OCR, and transcriptions of audio or video. Use it for documents, where reading the text beats looking at a small image. Long text comes in pages: if a result says more=true, call again with offset set to offset + the length you received. Personal information may be masked. Quote what you rely on when you
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | — |
| offset | integer | no | — |
| limit | integer | no | — |
| catalogue | string | no | — |
Look at a record's image: returns the reference image itself, so you can describe what it shows, read inscriptions or labels, or judge its condition. Use it before proposing a description for a record whose own text is thin. Only images the caller may view are returned (the reference copy, never the master). Say what you saw and what you inferred, and treat inscriptions you ca
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | — |
| catalogue | string | no | — |
List the proposals you made and what became of them, newest first. Each shows the record, the name, place, date or field text proposed, and its status: pending, approved, edited, linked (to an authority record), rejected, new_record_created or parked, with who reviewed it and when. Check it before proposing for a record, and do not propose again what was rejected. Needs the ar
| Parameter | Type | Required | Notes |
|---|---|---|---|
| status | no | — | |
| limit | integer | no | — |
| skip | integer | no | — |
Propose access points (people, organisations, places) and dates for one record. Read the record with get_record first. Propose only what its text, or a reliable source you name, supports; give the evidence and source URLs for each. For a person or organisation, also give dates_of_existence, a short history and places when the record or a source states them: they pre-fill the n
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | — |
| proposals | array | yes | — |
Propose relationships between people or organisations that a record states, such as a marriage or parent and child in a family register. Each side must be an existing authority record (give its id from search_authorities) or a person or organisation you have already proposed for this record with propose_access_points_and_dates. Give the line that states each relationship as ev
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | — |
| relationships | array | yes | — |
Propose new text for one field of a record, for an archivist to review. text is the complete proposed text for the field, not a fragment: read the record with get_record first and keep what is right in the current text. For a title, propose the title only (at most 1,024 characters). Give the evidence and the URLs of any web sources. Nothing on the record changes: on AtoM with
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | — |
| field | string | yes | — |
| text | string | yes | — |
| evidence | string | no | — |
| sources | no | — |
Propose a transcription of a record's file, such as a scanned page with no text. Look at the page with get_record_image first and transcribe what is written, line by line, in its own language and spelling; mark what you cannot read as [illegible] rather than guessing. Use get_record_text to see whether the file already has text. digital_object_id picks the file when a record has s
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | — |
| text | string | yes | — |
| digital_object_id | no | — | |
| evidence | string | no | — |
Propose a translation of one field of a record into another language. language is the target language code, e.g. "en", "af" or "nl". Translate the record's current text for that field faithfully (read it with get_record); keep names, dates and reference codes as they are. An archivist reviews it in AI > Suggest review next to any text already held in that language; once approv
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | — |
| field | string | yes | — |
| language | string | yes | — |
| text | string | yes | — |
| evidence | string | no | — |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install AHG Archives or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 93 / 100
Release 0.8.2 · scanned 28 Oct 2026
Graded from the tools this server lists, not from its source code.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score93
Findings0 threat · 0 capability
Capabilitymoderate
Coveragemanifest
Verificationnot in this report
Surface digest9978db03e5d3670ef5be13c640a0a004fa407b4953a60ae67726afd48aebbd51
Score vectorthreat 100 → client 93
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| search_records | no tags | |
| list_catalogues | no tags | |
| get_record | no tags | |
| get_children | no tags | |
| work_through_series | no tags | |
| get_authority | no tags | |
| search_authorities | no tags | |
| get_iiif_manifest | no tags | |
| get_record_text | no tags | |
| get_record_image | no tags | |
| list_my_proposals | no tags | |
| propose_access_points_and_dates | state-write | state-write: declares readOnlyHint: false |
| propose_relationships | state-write | state-write: declares readOnlyHint: false |
| propose_description_change | state-write | state-write: declares readOnlyHint: false |
| propose_transcription | state-write | state-write: declares readOnlyHint: false |
| propose_translation | state-write | state-write: declares readOnlyHint: false |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digest9978db03e5d3670e
Scanned2026-10-28
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 0.8.2.
0.8.2
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish AHG Archives can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.