Video History Project MCP server
org.videohistoryproject/researchvideohistoryproject.orgstreamable-httpv1.0.0Scanned
Search experimental video history, read public records, follow sources and export citations.
6 tools: 1 change things and 5 only read.
- Reads private data · 0
- Reads text others write · 1
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here changes things. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Video History Project MCP server can do
The Video History Project MCP server is published by videohistoryproject.org, a domain the MCP Registry verified. It has 6 tools. It can create or change data (1 tool: export_citations), but cannot delete data. 5 tools only read.
1 tool brings in text other people can write (get_record).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 19, 2026, version 1.0.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
6 tools
Changes things 1Claude Code: ask
export_citationsExport citations for 1–25 VHP IDs or URLs.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Export citations for 1–25 VHP IDs or URLs. format is text or ris; target is publication (the cataloged work) or page (the VHP web page). Missing publication metadata returns a per-item error; choose page to cite a biography or history page.
Annotations the server declares
- destructiveHint: false
- openWorldHint: false
- readOnlyHint: true
Only reads 5Show 5 read-only tools
describe_collectionDescribe the Video History Project collection, searchable text, filters, citation practices and response limits.No findings
Why it is in this group
- The name "describe_collection" says "describe": a word for reading.
Description, as the server wrote it Describe the Video History Project collection, searchable text, filters, citation practices and response limits. Useful when beginning research.
Annotations the server declares
- destructiveHint: false
- openWorldHint: false
- readOnlyHint: true
get_recordRead a public VHP record by ID or VHP URL, resolving old addresses locally.Reads text others writeNo findings
Why it is in this group
- The name "get_record" says "get": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "read" and "url": it reads web pages, which anyone can write.
Description, as the server wrote it Read a public VHP record by ID or VHP URL, resolving old addresses locally. Returns metadata, source links, citations and a section of existing text. Default section is body; choose other section names from sections. Follow content.nextOffset with the same section and version for complete text. Linked scans are not read.
Annotations the server declares
- destructiveHint: false
- openWorldHint: false
- readOnlyHint: true
list_termsFind catalog author or subject filter keys by part of a name.No findings
Why it is in this group
- The name "list_terms" says "list": a word for reading.
Description, as the server wrote it Find catalog author or subject filter keys by part of a name. Returns exact keys, display labels and counts of discoverable records. field is author or subject. Follow nextPage; use a returned key in search_records.
Annotations the server declares
- destructiveHint: false
- openWorldHint: false
- readOnlyHint: true
search_recordsSearch public VHP records by words or quoted phrases.No findings
Why it is in this group
- The name "search_records" says "search": a word for reading.
Description, as the server wrote it Search public VHP records by words or quoted phrases. Empty query browses. Combine exact author/subject keys from list_terms, recorded years and a type from describe_collection. Follow nextPage. Excerpts label their source; read get_record before quoting.
Annotations the server declares
- destructiveHint: false
- openWorldHint: false
- readOnlyHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write1
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:17 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 1
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://www.videohistoryproject.org/mcp: tools/list returned 6 tools to an anonymous client, including export_citations (write)
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http research https://www.videohistoryproject.org/mcpclaude mcp add --transport http research https://www.videohistoryproject.org/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__research__get_record",
"mcp__research__list_terms",
"mcp__research__search_records",
"mcp__research__get_related_records",
"mcp__research__describe_collection"
],
"ask": [
"mcp__research__export_citations"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as research. Review it before you use it.
Capability tags behind 1 rule
- mcp__research__get_record untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/org.videohistoryproject/research/verify?hash=85f478ed1ee9425395c91a867067ba8474ebfa1828414bd04c1bf5553c77d5a3" | jq -e '.changed == false'Pinned hash 85f478ed1ee9, from Nov 19, 2026, 01:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/org.videohistoryproject/research/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/org.videohistoryproject/research)Source: MCP Registry. Synced Oct 21, 2026, 18:54 UTC.
Video History Project MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Video History Project MCP server safe?
- No scan can promise that. What its definitions show: 6 tools, 1 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Video History Project MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Video History Project MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Video History Project MCP server have?
- 6 tools: 1 write, 5 read. export_citations, get_record, list_terms, search_records, get_related_records and describe_collection.
Does the Video History Project MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Video History Project MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Video History Project MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 19, 2026.