Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Video History Project

REMOTE · WWW.VIDEOHISTORYPROJECT.ORG

Search experimental video history, read public records, follow sources and export citations.

0 this week 88 Trust /100

Last scanned (17 hours ago)

Scores higher than 95% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Education and Research

Trust breakdown (7 categories)

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 Security83
  • 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. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
Schema Quality & AI Usability84
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 562 tokens (~80/item across 7 items; 6 tools + 1 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage71
  • 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
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 11 Nov 26 0
    • Stability: 0.97 → pass security
  • 10 Nov 26 0
    • Stability: pass → 0.97 functional
  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 18 Oct 26 0
    • Stability: 0.97 → pass security
  • 9 Oct 26 0
    • DNSSEC: fail → pass ▲ security
  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 19 Sept 26 0
    • Stability: unverified → 0.03 ▲ functional
Diagnostics

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 21 Nov 2026 · Probed https://www.videohistoryproject.org/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=videohistoryproject.org CN=WE1,O=Google Trust Services,C=US 18 Nov 2026 16 Feb 2027 ECDSA 256 ECDSA-SHA256 de3b5b39aabb85d6136cd5190f4cb8f3
SANs: videohistoryproject.org, *.videohistoryproject.org
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC secure

Validation of www.videohistoryproject.org. — Secure

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
org. DS published 725 8 Verified
videohistoryproject.org. DS published 2371 13 Verified
www.videohistoryproject.org. Verified address RRset verified with the apex keys
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
Header Value
strict-transport-security max-age=2592000
content-security-policy default-src 'self'; img-src 'self' https:; style-src 'self'; script-src 'self' https://challenges.cloudflare.com; frame-src https://challenges.cloudflare.com https://archive.org; connect-src 'self' https://challenges.cloudflare.com; frame-ancestors 'none'; base-uri 'none'; form-action 'self'
x-content-type-options nosniff
referrer-policy no-referrer

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://www.videohistoryproject.org/mcp Verified 200
http (plaintext) http://www.videohistoryproject.org/mcp HTTPS enforced 308 https://www.videohistoryproject.org/mcp
MCP tools · 6 exposed · ~487 tokens

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 →

Tool Tokens
describe_collection ~31

Describe the Video History Project collection, searchable text, filters, citation practices and response limits. Useful when beginning research.

Input schema present but exposes no named parameters.

NameTypeReqDescription
defaultLimitinteger––
guidestringyes–
guideUrlstringyes–
maximumLimitinteger––
maximumTextCharactersinteger––
namestringyes–
recordsintegeryes–
typesarrayyes–
websitestringyes–

No examples provided.

export_citations ~86

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.

NameTypeReqDescription
formatstring––
idsarrayyes–
targetstring––
NameTypeReqDescription
formatstringyes–
resultsarrayyes–
targetstringyes–

No examples provided.

get_record ~108

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.

NameTypeReqDescription
idstringyes–
limitinteger––
offsetinteger––
sectionstring––
versionstring|null––
NameTypeReqDescription
authorKeysarrayyes–
citationsobjectyes–
contentobjectyes–
creditsarrayyes–
idintegeryes–
kindstring|nullyes–
linksarrayyes–
metadataarrayyes–
modifiedstring|nullyes–
rightsUrlstringyes–
sectionsarrayyes–
subjectsarrayyes–
titlestringyes–
urlstringyes–
versionstringyes–

No examples provided.

get_related_records ~62

Get the site's existing similarity suggestions for a public record. These are research leads, not evidence of a historical relationship. May return no suggestions when the index has none or the editor has disabled them.

NameTypeReqDescription
idstringyes–
limitinteger––
NameTypeReqDescription
idintegeryes–
methodstringyes–
notestringyes–
resultsarrayyes–

No examples provided.

list_terms ~80

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.

NameTypeReqDescription
fieldstringyes–
limitinteger––
pageinteger––
querystring––
NameTypeReqDescription
fieldstringyes–
nextPageinteger|nullyes–
pageintegeryes–
resultsarrayyes–
totalintegeryes–

No examples provided.

search_records ~120

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.

NameTypeReqDescription
authorstring|null––
frominteger|null––
limitinteger––
pageinteger––
querystring––
subjectstring|null––
tointeger|null––
typestring|null––
NameTypeReqDescription
filtersobjectyes–
limitintegeryes–
nextPageinteger|nullyes–
pageintegeryes–
resultsarrayyes–
searchUrlstringyes–
totalintegeryes–

No examples provided.

Install

How do I install the Video History Project MCP server?

Video History Project is a hosted endpoint at https://www.videohistoryproject.org/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 · www.videohistoryproject.org

# add to Claude Code
claude mcp add --transport http org-videohistoryproject-research 'https://www.videohistoryproject.org/mcp'
Common questions

What is the Video History Project MCP server?

Video History Project is an MCP server listed in the public MCP registry as org.videohistoryproject/research. Search experimental video history, read public records, follow sources and export citations. This page covers its hosted endpoint (https://www.videohistoryproject.org/mcp).

Is the Video History Project MCP server safe to use?

Video History Project scores 88 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 Video History Project MCP server expose?

Video History Project exposes 6 tools: export_citations, get_record, list_terms, search_records, get_related_records, describe_collection. Their descriptions and schemas cost roughly 487 tokens of context every time the server is loaded.

Does the Video History Project MCP server require authentication?

No. We connected to Video History Project without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Video History Project MCP server still maintained?

Video History Project is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Video History Project MCP server?

VerifyMCP ran 13 checks on Video History Project, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.