# Polish Archives Indexes (pypi · polish-archives-mcp)

Search Geneteka, the Poznań Project and BaSIA for Polish vital records; fetch archive scans.

- Trust score: 64/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-18

## Components

- pypi · `polish-archives-mcp`: 64/100 (this document), [markdown](https://verifymcp.io/servers/ianderso-polish-archives-mcp/polish-archives-mcp.md), [page](https://verifymcp.io/servers/ianderso-polish-archives-mcp/polish-archives-mcp)

## Channel facts

- Registry: `pypi`
- Package: `polish-archives-mcp`
- Version: `0.1.1`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-18.

- **Supply Chain Security**: 50/100
  - Malware scan not yet available for this package.
  - No known CVEs affecting this package version or its production dependencies.
  - Runs hatchling.build at install time, a recognised build step with no custom scripting around it.
  - 1 of 32 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 100/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to ianderso/polish-archives-mcp).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 6 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 59/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1756 tokens (~250/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

**Unverified: 1 category.** A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

## Install

### How do I install the Polish Archives Indexes MCP server?

Polish Archives Indexes runs locally as a PyPI package, launched with uvx polish-archives-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add ianderso-polish-archives-mcp -- uvx polish-archives-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "ianderso-polish-archives-mcp": {
      "command": "uvx",
      "args": [
        "polish-archives-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ianderso-polish-archives-mcp": {
      "command": "uvx",
      "args": [
        "polish-archives-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add ianderso-polish-archives-mcp -- uvx polish-archives-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ianderso-polish-archives-mcp": {
      "type": "local",
      "command": [
        "uvx",
        "polish-archives-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ianderso-polish-archives-mcp --command uvx --arg polish-archives-mcp
```

### Hermes

```yaml
mcp_servers:
  ianderso-polish-archives-mcp:
    command: "uvx"
    args: ["polish-archives-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "ianderso-polish-archives-mcp": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "polish-archives-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add ianderso-polish-archives-mcp -t stdio -c uvx -a polish-archives-mcp
```

### Other

```json
{
  "mcpServers": {
    "ianderso-polish-archives-mcp": {
      "command": "uvx",
      "args": [
        "polish-archives-mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-18 (score 64, −15)

- [security regression] Malware scan: pass → unverified

### 2026-10-16 (score 79, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-10-15 (score 64, −15)

- [security regression] Malware scan: pass → unverified

### 2026-10-14 (score 79, +29)

- [security improvement] Injection markers: unverified → pass
- [security] First check of Judged manipulation: pass
- [security] Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window).
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] MCP protocol: unverified → pass
- [functional] First check of Schema quality: fail
- [functional] First check of Destructive annotations: pass
- [functional] First check of Schema quality: fail
- [functional] First check of Schema quality: good
- [functional] First check of Tool coverage: 100

### 2026-10-13 (score 50, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-10-12 (score 35)

First indexed and scored.

## MCP tools (7)

### `regions` (~75 tokens)

List Geneteka's region codes and names. Makes no network call.

Pass a code as `region` to geneteka_coverage or geneteka_search. Regions
are today's Polish voivodeships plus Warsaw, Ukraine, Belarus, Lithuania
and 'other'. Most of the Prussian Provinz Posen is 15wp.

### `geneteka_coverage` (~203 tokens)

List the registers Geneteka has indexed for a parish: record type, years, and rid.

Check this before trusting a zero from geneteka_search: a parish or year
not listed here was never searched. Years are exactly as Geneteka lists
them, gaps included ('1741-55,90,98' is 1741-1755, 1790, 1798). A
register is named by its parish, not by each village in it. Pass a rid
to geneteka_search to search one register.

Input parameters:

- `place` (string, required): Parish name, or part of it, e.g. 'Kraków' or 'Mariacki'.
- `refresh` (boolean): True re-reads the coverage list (kept a week).
- `region` (string): Keep one region, e.g. '06mp' (see regions).
- `year`: Mark whether each register lists this year as indexed.

### `geneteka_search` (~310 tokens)

Search Geneteka's index of one region, or of one register with rid.

Each row has the year and entry (act) number, the people, any indexer
notes (often a date or village), the custodian holding the book, and any
scan link (a Szukaj w Archiwach unit page opens in a browser). A zero
covers only the registers and years searched: check geneteka_coverage.
One page per call; ask for the next page rather than assuming the first
is all.

Input parameters:

- `exact` (boolean): Match the surname exactly.
- `given` (string): Given name.
- `given2` (string): The second person's given name.
- `page` (integer): Page of 50 rows, from 1.
- `record_type` (string, required): B births/baptisms, M marriages, D deaths/burials.
- `refresh` (boolean): True asks the site again instead of using the cached answer (kept a day).
- `region` (string): Region code (see regions). Not needed when rid is given.
- `rid`: One register's id, from geneteka_coverage.
- `surname` (string, required): Surname. Geneteka also finds close forms unless exact.
- `surname2` (string): A second person in the same entry: the other spouse, or a parent.
- `year_from`: First year, e.g. 1850.
- `year_to`: Last year.

### `poznan_search` (~304 tokens)

Search the Poznań Project's marriages, 1800-1899, Wielkopolska and Kujawy.

Each row has the parish, entry and year, groom and bride with ages and
parents, how closely each surname matched, and who holds the original
register. Given names are matched to the project's name groups (Joannes
/ Jan / Johann); a name in no group returns the groups. Too many matches
come back as too_many_results, never as a zero.

Input parameters:

- `any_surname` (string): Instead of the two surnames: a surname of either spouse.
- `bride_given` (string): Bride's given name, any language.
- `bride_surname` (string): Bride's surname (maiden or widow's).
- `confession` (string): Kind of register; civil is the Standesamt (USC).
- `groom_given` (string): Groom's given name, any language.
- `groom_surname` (string): Groom's surname.
- `page` (integer): Page of 50 rows, from 1.
- `refresh` (boolean): True asks the site again instead of using the cached answer (kept a day).
- `threshold` (integer): Least similarity, 50-100; 70 catches more spellings.
- `year_from` (integer): First year, 1800-1899.
- `year_to` (integer): Last year, 1800-1899.

### `basia_search` (~327 tokens)

Search BaSIA, the Wielkopolska archival index tied to call numbers and scans.

Every row carries the archive, the call number and scan as BaSIA gives
them, the unit's address on szukajwarchiwach.gov.pl (a person opens it
in a browser), BaSIA's id, and a warning: BaSIA's middle (series) number
can differ from the archive's, so cite the Sygnatura from the unit page.
BaSIA lists at most 250 entries per search. Its coverage is whatever its
volunteers have done: a zero is weak evidence.

Input parameters:

- `distance_km` (integer): Radius around place, in km.
- `given` (string): That person's given name.
- `page` (integer): Page of 50 rows, from 1.
- `persons`: Up to 4 more people in the same entry, each 'Given Surname' (a parent, spouse, godparent).
- `place` (string): A place (town or village) to search around.
- `record` (string): Kind of record.
- `refresh` (boolean): True asks the site again instead of using the cached answer (kept a day).
- `similarity` (integer): Least name similarity, 50-100.
- `surname` (string, required): Surname of a person in the entry.
- `unit` (string): Office: usc civil registry, kat Catholic parish, ewa Protestant parish.
- `year_from`: First year.
- `year_to`: Last year.

### `swa_scan` (~181 tokens)

Download one full-size scan (about 3500 px) from Szukaj w Archiwach's photo host.

The unit page itself is behind a bot check: a person opens it in a
browser, reads the Sygnatura, and takes each scan's hash from its image
address. The scan is written to `destination`, never returned inline: a
new .jpg or .jpeg, not hidden, not under ~/Library, and inside the
operator's download folder when one is set. Cite it by the Sygnatura and
scan number, not by this address.

Input parameters:

- `destination` (string, required): Absolute path of a new .jpg file. The directory must exist and the file must not: nothing is overwritten.
- `hash` (string, required): The scan's 64-character hex name, read from the unit page in a browser.

### `cache_status` (~26 tokens)

Report this session's requests, by site, and cache use. Makes no network call.

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/ianderso-polish-archives-mcp/polish-archives-mcp#diagnostics

## Score history

- 2026-10-18: 64
- 2026-10-17: 79
- 2026-10-16: 79
- 2026-10-15: 64
- 2026-10-14: 79
- 2026-10-13: 50
- 2026-10-12: 35

## Common questions

### What is the Polish Archives Indexes MCP server?

Polish Archives Indexes is an MCP server listed in the public MCP registry as io.github.ianderso/polish-archives-mcp. Search Geneteka, the Poznań Project and BaSIA for Polish vital records; fetch archive scans. This page covers its PyPI package (polish-archives-mcp).

### Is the Polish Archives Indexes MCP server safe to use?

Polish Archives Indexes scores 64 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 18 October 2026. Its build provenance is signed and verified. 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 Polish Archives Indexes MCP server expose?

Polish Archives Indexes exposes 7 tools: regions, geneteka_coverage, geneteka_search, poznan_search, basia_search, and 2 more. Their descriptions and schemas cost roughly 1,426 tokens of context every time the server is loaded.

### Is the Polish Archives Indexes MCP server still maintained?

Polish Archives Indexes is still listed as active in the MCP registry. We last reached this channel on 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the Polish Archives Indexes MCP server under?

Polish Archives Indexes declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- PyPI project: https://pypi.org/project/polish-archives-mcp/
- Socket report: https://socket.dev/pypi/package/polish-archives-mcp
- Repository: https://github.com/ianderso/polish-archives-mcp
- Changelog RSS feed: https://verifymcp.io/servers/ianderso-polish-archives-mcp/polish-archives-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/ianderso-polish-archives-mcp/polish-archives-mcp.json
- HTML version of this page: https://verifymcp.io/servers/ianderso-polish-archives-mcp/polish-archives-mcp