AHG Archives
REMOTE · MCP.THEAHG.CO.ZA · 2 COMPONENTS
Search and read AtoM archival catalogues with citable links; staff propose changes for review.
Available components
Last scanned (22 hours ago)
Scores higher than 55% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Education and Research
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability58
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 2565 tokens (~160/item across 16 items; 16 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management30
- Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 16 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 17 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 +7
- Authorization: unverified → partial ▲ security
- 27 Oct 26 0
- Tool “get_record_text” rewrote its description, which is the text the model reads security
- Tool “get_record_image” rewrote its description, which is the text the model reads security
- Schema quality: 142 → 160 ▼ functional
- Stability: unverified → 0.03 ▲ functional
- 26 Oct 26 59
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Probed https://mcp.theahg.co.za/public/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.theahg.co.za | CN=YE1,O=Let's Encrypt,C=US | 21 Oct 2026 | 19 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 5879518fa99f2370c3969a09317d0f82cb0 |
| SANs: mcp.theahg.co.za | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.theahg.co.za. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| za. | present | 45749 | 8 | Verified |
| co.za. | present | 41369 | 8 | Verified |
| theahg.co.za. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.theahg.co.za/public/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.theahg.co.za/public/mcp | HTTPS enforced | 301 | https://mcp.theahg.co.za/public/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_authority ~39
Read an authority record (a person, family or organisation) by its slug.
| Name | Type | Req | Description |
|---|---|---|---|
| catalogue | string | – | – |
| slug | string | yes | – |
No output schema declared.
No examples provided.
get_children ~52
List the descriptions directly below one record (for example the series in a fonds).
| Name | Type | Req | Description |
|---|---|---|---|
| catalogue | string | – | – |
| limit | integer | – | – |
| skip | integer | – | – |
| slug | string | yes | – |
No output schema declared.
No examples provided.
get_iiif_manifest ~45
Return the IIIF manifest URL for a record's images, for viewing in a IIIF viewer.
| Name | Type | Req | Description |
|---|---|---|---|
| catalogue | string | – | – |
| slug | string | yes | – |
No output schema declared.
No examples provided.
get_record ~91
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).
| Name | Type | Req | Description |
|---|---|---|---|
| catalogue | string | – | – |
| slug | string | yes | – |
No output schema declared.
No examples provided.
get_record_image ~253
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 cannot read clearly as uncertain. Where the catalogue states rights (OpenRiC Workspace, AtoM with the AHG Extensions, Heratio), each result carries rights: RightsStatements.org statements, Creative Commons licences, what may be done (PREMIS acts: allow, disallow, conditional) and Local Contexts labels. Follow them when you quote or reuse anything, and say what they are. A file whose labels ask for no reuse (TK Secret/Sacred, Community Use Only, Women or Men Restricted), or that may not be shown, is withheld: it is not given to you, and you should not try to describe or obtain it another way.
| Name | Type | Req | Description |
|---|---|---|---|
| catalogue | string | – | – |
| slug | string | yes | – |
No output schema declared.
No examples provided.
get_record_text ~269
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 propose changes. Where the catalogue states rights (OpenRiC Workspace, AtoM with the AHG Extensions, Heratio), each result carries rights: RightsStatements.org statements, Creative Commons licences, what may be done (PREMIS acts: allow, disallow, conditional) and Local Contexts labels. Follow them when you quote or reuse anything, and say what they are. A file whose labels ask for no reuse (TK Secret/Sacred, Community Use Only, Women or Men Restricted), or that may not be shown, is withheld: it is not given to you, and you should not try to describe or obtain it another way.
| Name | Type | Req | Description |
|---|---|---|---|
| catalogue | string | – | – |
| limit | integer | – | – |
| offset | integer | – | – |
| slug | string | yes | – |
No output schema declared.
No examples provided.
list_catalogues ~28
The catalogues this service can search and read. Proposals go to the home catalogue only.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_my_proposals ~126
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 archivist's own staff key.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| skip | integer | – | – |
| status | – | – | – |
No output schema declared.
No examples provided.
propose_access_points_and_dates ~239
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 new authority record if the archivist creates one. Look names and places up with search_authorities first; when one is already in the catalogue, give its id as existing_id and why in link_reason, and the archivist sees it as the first candidate to link. Nothing on the record changes: an archivist reviews every proposal. On AtoM with the AHG extensions they are queued in AI > NER review; on stock AtoM they are returned for the archivist to apply. Needs the archivist's own staff key.
| Name | Type | Req | Description |
|---|---|---|---|
| proposals | array | yes | – |
| slug | string | yes | – |
No output schema declared.
No examples provided.
propose_description_change ~191
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 the AHG extensions the proposal is queued in AI > Suggest review, where the archivist can edit it before approving; on stock AtoM it is returned for the archivist to apply. Needs the archivist's own staff key.
| Name | Type | Req | Description |
|---|---|---|---|
| evidence | string | – | – |
| field | string | yes | – |
| slug | string | yes | – |
| sources | – | – | – |
| text | string | yes | – |
No output schema declared.
No examples provided.
propose_relationships ~134
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 evidence. An archivist reviews them in AI > Relationship review; approved ones show on both authority records. Needs the archivist's own staff key.
| Name | Type | Req | Description |
|---|---|---|---|
| relationships | array | yes | – |
| slug | string | yes | – |
No output schema declared.
No examples provided.
propose_transcription ~187
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 several. At most 65,000 bytes: propose a long document page by page. An archivist compares it with the page image in AI > Suggest review; once approved it is the file's text and is searchable. Needs the archivist's own staff key.
| Name | Type | Req | Description |
|---|---|---|---|
| digital_object_id | – | – | – |
| evidence | string | – | – |
| slug | string | yes | – |
| text | string | yes | – |
No output schema declared.
No examples provided.
propose_translation ~155
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 approved the record shows it in that language. Needs the archivist's own staff key.
| Name | Type | Req | Description |
|---|---|---|---|
| evidence | string | – | – |
| field | string | yes | – |
| language | string | yes | – |
| slug | string | yes | – |
| text | string | yes | – |
No output schema declared.
No examples provided.
search_authorities ~142
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 links the existing record instead of creating a new one.
| Name | Type | Req | Description |
|---|---|---|---|
| catalogue | string | – | – |
| kind | string | – | – |
| limit | integer | – | – |
| name | string | yes | – |
No output schema declared.
No examples provided.
search_records ~137
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 same catalogue; read a result with the catalogue it came from.
| Name | Type | Req | Description |
|---|---|---|---|
| catalogue | string | – | – |
| limit | integer | – | – |
| query | string | yes | – |
| skip | integer | – | – |
No output schema declared.
No examples provided.
work_through_series ~197
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). For each child: read it (get_record, and get_record_text or get_record_image when its text is thin), skip it when your proposals there are still pending, propose, then move on. Call again with skip=next_skip until it is null. When get_record shows a child has children of its own, work through it the same way.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| skip | integer | – | – |
| slug | string | yes | – |
No output schema declared.
No examples provided.
How do I install the AHG Archives MCP server?
AHG Archives is a hosted endpoint at https://mcp.theahg.co.za/public/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.theahg.co.za
claude mcp add --transport http za-co-theahg-ahg-archives 'https://mcp.theahg.co.za/public/mcp'
What is the AHG Archives MCP server?
AHG Archives is an MCP server listed in the public MCP registry as za.co.theahg/ahg-archives. Search and read AtoM archival catalogues with citable links; staff propose changes for review. This page covers its hosted endpoint (https://mcp.theahg.co.za/public/mcp).
Is the AHG Archives MCP server safe to use?
AHG Archives scores 70 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the AHG Archives MCP server expose?
AHG Archives exposes 16 tools: search_records, list_catalogues, get_record, get_children, work_through_series, and 11 more. Their descriptions and schemas cost roughly 2,285 tokens of context every time the server is loaded.
Does the AHG Archives MCP server require authentication?
No. We connected to AHG Archives without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the AHG Archives MCP server still maintained?
AHG Archives is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.