Data Collection

vicp-registry.org

Provides access to Vaccine Injury Compensation Program case data with search, retrieval, and statistics features.

1 endpoint10 known toolsFirst detected July 11, 2026Last detected August 29, 2026

ENDPOINT 1

https://vicp-registry.org/mcp

No auth detected

MCP server metadata

Name: VICP Registry
Version: 1.28.1

Capabilities

experimentalpromptsresourcestools

Server instructions

VICP Registry â€” U.S. Vaccine Injury Compensation Program case database. This server queries the same live SQLite database that powers https://vicp-registry.org: ~13,000 curated decisions of the U.S. Court of Federal Claims Office of Special Masters (1988-present), extracted from public court documents (GovInfo / CourtListener primary sources). Conventions: - Cases are identified by `package_id` (e.g. USCOURTS-cofc-1_03-vv-00654) and referred to by `petitioner_identifier` (often initials like "M.M." for minors). - `outcome` values: compensated, dismissed, denied, entitlement_granted_pending_damages, unclear, pending. - Case summaries are AI-assisted extractions from court documents and can contain mistakes; for legal or medical precision, always check the staged source text (get_case_text) or the linked PDFs. - Award-amount caveat: a small number of award_amount_usd values suffer a known extraction bug where cents were stored as dollars (values over $10,000,000 are suspect). Cross-check the case_summary or source text before citing any award over $10M. - Statistics describe this case-record dataset, NOT vaccine-safety rates in the general population. Most vaccinations never lead to a VICP claim. Typical workflow: get_filters() to see valid filter values -> search_cases() -> get_case() / get_case_text() for detail. Cite the canonical case URL (https://vicp-registry.org/case/<package_id>) when quoting a case.

Known tools 10

search_cases

Search VICP cases with structured filters.

Inferred read-only

get_case

Get the complete curated record for one case by package_id.

Inferred read-only

get_case_text

Get the staged plain text of a case's public court documents.

Inferred read-only

get_filters

List all valid filter values: canonical vaccine names (with case counts), condition categories, outcomes, special masters, and the dataset's date range.

Inferred read-only

get_statistics

Aggregate statistics over the case corpus, optionally filtered.

Inferred read-only

search_attorneys

Search petitioner attorneys and firms by name.

Inferred read-only

get_attorney

Get one attorney's profile: bio (when available), aggregate outcomes, and their most recent cases.

Inferred read-only

get_special_master

Decision patterns for one special master: outcome breakdown, top vaccines/conditions in their docket, and recent cases.

Inferred read-only

search

Search VICP vaccine-injury cases by free text.

Inferred read-only

fetch

Fetch the full record + source text of one case by its id (package_id).

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.vicp-registry]
url = "https://vicp-registry.org/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "vicp-registry": {
      "type": "http",
      "url": "https://vicp-registry.org/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: vicp-registry
Remote MCP URL: https://vicp-registry.org/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "vicp-registry": {
      "url": "https://vicp-registry.org/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "vicp-registry": {
      "type": "http",
      "url": "https://vicp-registry.org/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "vicp-registry",
  "transport": "streamable-http",
  "url": "https://vicp-registry.org/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Trust Data Available

BuiltWith Trust API v2 evidence for vicp-registry.org was fetched 2026-08-04T19:29:00.844Z and is being refreshed.

Trust status Neutral

vicp-registry.org is assessed as Neutral: No suspicious signals found, but no strong positive signal either

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.