Skills/PyPI/tna-discovery-mcp

tna-discovery-mcp@0.1.0

VERIFIED· not started

Publisher claims: "MCP server for Discovery, the catalogue of the UK National Archives: search record descriptions, read one with its place in the hierarchy, browse a series or piece, and find a Chelsea pensioner's discharge papers (WO 97) by name, regiment, birthplace and dates. For genealogy and history." Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry PyPI (MCP server)Publisher ianderso · publishing for 52 daysInstalls 111Last detonated 2 h ago
$claude mcp add tna-discovery-mcp -- uvx tna-discovery-mcp
WatchReport an issue

Coverage

Not started: dependency install failed; the server itself was not observed.
Tested
the dependency install step · every file read, file written and host contacted by what ran
Not tested
server startup · the tool list · tool behavior

What this means for the label: Verified here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.

Before you give it your token

It will ask for
no credential variables read in the code
Where it talks to
no vendor host named in the codeAlso nationalarchives.gov.uk — not the publisher's domain; check what for before connecting.
What we saw when it ran
no credential files read · no network
What we could not test
server startup · the tool list · tool behavior

Connect it under the guard. Not started: dependency install failed; the server itself was not observed. The code names no credential variable; the guard pins the network to what the honeypot saw and logs every call.

$vet-skills run --net declared -- uvx tna-discovery-mcp

Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.

Is [email protected] safe to install?

KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; not started: dependency install failed; the server itself was not observed) on 2026-11-19 and scored it 87/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.

Behavior trace

Honeypot run · 1 s · 2 scenarios · 0 deviations
t+CategoryObserved action
0.0sprocessno install scripts in bundle
0.4sprocessdependency install exit 1 ·
0.4sclaimednot started: dependency install failed (exit 1); the server itself was not observed
0.4sprocessscript backend runs setup only
0.4sprocessno install scripts to re-run

Static findings

HIGH
Access to sensitive file pathssrc/tna_discovery_mcp/config.py:18 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesNone is required: Discovery's API needs no key and no account. A ``.env``Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathssrc/tna_discovery_mcp/config.py:82 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesA ``.env`` file in the working directory is read if present; realFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
MEDIUM
Access to sensitive file pathstests/test_config.py:80 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files(tmp_path / ".env").write_text("TNA_DISCOVERY_TIMEOUT=7\n")Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathssrc/tna_discovery_mcp/config.py:96 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesload_dotenv(Path.cwd() / ".env")Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
MEDIUM
Access to sensitive file pathstests/test_config.py:1 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files"""Settings from the environment and from ``.env`` in the working directory."""Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
MEDIUM
Access to sensitive file pathstests/test_config.py:85 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files(tmp_path / ".env").write_text("TNA_DISCOVERY_TIMEOUT=7\n")Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
LOW
URL to a private-network addresstests/test_security.py:253 · URL to a private-network address — a LAN or development targetmonkeypatch.setenv("HTTPS_PROXY", "http://10.0.0.1:3128")Fix: Replace encoded or assembled strings with plain literals and remove undeclared network calls.
AST07
MEDIUM
Access to sensitive file pathstests/test_security.py:117 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files"../../../etc/passwd",Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05

Cost to the agent

Instructions loaded
≈111 tok
1 file · 51 in bundle
Tool list per prompt
≈0 tok
0 tools · 0 per tool
Handshake
no reply
launch to tools/list, stdio
Undocumented tools
0
description under 20 chars · avg 0

Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.

Known vulnerabilities

No advisories in OSV for tna-discovery-mcp@0.1.0 as of 2 h ago. This is the package itself, not its dependencies.

tna-discovery-mcp@0.1.0 safety verdict: Verified (not started) — KillerSkills