Is the Vicp Registry MCP server down?

mcp-registry/org.vicp-registry/vicp-registry · v1.28.1

healthy
Last checked 2026-10-27 01:47 UTC · handshake 371ms

As of 2026-10-27 01:47 UTC, the Vicp Registry MCP server is up with a Glimind reliability score of 84/100 (grade B). Over the last 30 days it answered 99.8% of Glimind's liveness checks. It had 25 outages in 90 days, with a median recovery of 2 minutes.

uptime (30d checks)
99.8%
checks observed
5,011
outages (90d)
25
tools
10

Search 13,000+ US vaccine court (VICP) decisions: cases, court text, statistics, attorneys. Free.

Point your MCP client at this streamable-http endpoint: https://vicp-registry.org/mcp

Agent-readiness: C (71/100)

C (71/100): 0 error(s), 2 warning(s) across 10 tool(s); ~1,836 tokens of tool definitions.
Scores higher than 5% of 15,771 MCP servers Glimind has audited.
Its tool list costs an agent ~1,836 tokens per session — lighter than 55% of servers.
70 → 71 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions30
Safety hints30
Token cost100
Client compatibility70
Protocol100
Reliability100
Stability100

What to fix (3)

10 of 10 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →

Tools: fetch, get_attorney, get_case, get_case_text, get_filters and 5 more

36 parameter(s) across 9 tool(s) have no description.

Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →

Tools: fetch, get_attorney, get_case, get_case_text, get_special_master and 4 more

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →

Auto-fix: 10 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 9 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Forg.vicp-registry%2Fvicp-registry/fixes

fetch 1 change 
{
  "name": "fetch",
  "description": "Fetch the full record + source text of one case by its id (package_id).\n    (Deep-research companion to search.)",
  "inputSchema": {
    "type": "object",
    "title": "fetchArguments",
    "required": [
      "id"
    ],
    "properties": {
      "id": {
        "type": "string",
        "title": "Id"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}
get_attorney 1 change 
{
  "name": "get_attorney",
  "description": "Get one attorney's profile: bio (when available), aggregate outcomes,\n    and their most recent cases. Name is matched case-insensitively.",
  "inputSchema": {
    "type": "object",
    "title": "get_attorneyArguments",
    "required": [
      "name"
    ],
    "properties": {
      "name": {
        "type": "string",
        "title": "Name"
      },
      "limit": {
        "type": "integer",
        "title": "Limit",
        "default": 30
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}
get_case 1 change 
{
  "name": "get_case",
  "description": "Get the complete curated record for one case by package_id.\n\n    Includes the AI-assisted case summary, all extracted fields, attorney and\n    special master, plus links: canonical page, plain-text source bundle, and\n    per-document PDF links where available.\n    ",
  "inputSchema": {
    "type": "object",
    "title": "get_caseArguments",
    "required": [
      "package_id"
    ],
    "properties": {
      "package_id": {
        "type": "string",
        "title": "Package Id"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/org.vicp-registry/vicp-registry"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/org.vicp-registry/vicp-registry"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

Markdown 
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Forg.vicp-registry%2Fvicp-registry.svg)](https://glimind.com/server/mcp-registry%2Forg.vicp-registry%2Fvicp-registry?ref=badge)
HTML 
<a href="https://glimind.com/server/mcp-registry%2Forg.vicp-registry%2Fvicp-registry?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Forg.vicp-registry%2Fvicp-registry.svg" alt="MCP agent-readiness"></a>
reStructuredText 
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Forg.vicp-registry%2Fvicp-registry.svg
   :target: https://glimind.com/server/mcp-registry%2Forg.vicp-registry%2Fvicp-registry?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:2898cf98f50648b6…, first seen 2026-10-17, included at leaf 13488 of 76,680. Version history · verify what your client received.

Tools (10)

Compare: most reliable retrieval servers · most reliable knowledge servers · most reliable data servers · most reliable search servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Vicp Registry MCP server down right now?

As of 2026-10-27 01:47 UTC, the Vicp Registry MCP server is up with a Glimind reliability score of 84/100 (grade B). Over the last 30 days it answered 99.8% of Glimind's liveness checks. It had 25 outages in 90 days, with a median recovery of 2 minutes.

How many tools does Vicp Registry MCP server provide?

Vicp Registry MCP server advertises 10 tools, including fetch, get_attorney, get_case, get_case_text, get_filters.

How do I install Vicp Registry MCP server?

Point your MCP client at this streamable-http endpoint: https://vicp-registry.org/mcp

Is the Vicp Registry MCP server safe to connect to an AI agent?

Glimind scanned all 10 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Vicp Registry MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.

Feedback
Help us improve