# Verify API (pypi · verify-api-mcp)

Evidence-backed verification for citations, packages, repos, cases, filings, drugs, x402 sellers.

- Trust score: 73/100 (medium)
- Change this week: +18
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- pypi · `verify-api-mcp`: 73/100 (this document), [markdown](https://verifymcp.io/servers/mgdsn-verify-api-mcp/verify-api-mcp.md), [page](https://verifymcp.io/servers/mgdsn-verify-api-mcp/verify-api-mcp)

## Channel facts

- Registry: `pypi`
- Package: `verify-api-mcp`
- Version: `0.6.0`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it.
  - 1 of 32 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 32/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - License check failed: no license is declared.
  - Actively maintained (last published 16 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 66/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 747 tokens (~93/item across 8 items; 8 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 70/100
  - Stability observed for 21 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 67/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the Verify API MCP server?

Verify API runs locally as a PyPI package, launched with uvx verify-api-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add mgdsn-verify-api-mcp -- uvx verify-api-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "mgdsn-verify-api-mcp": {
      "command": "uvx",
      "args": [
        "verify-api-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "mgdsn-verify-api-mcp": {
      "command": "uvx",
      "args": [
        "verify-api-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add mgdsn-verify-api-mcp -- uvx verify-api-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "mgdsn-verify-api-mcp": {
      "type": "local",
      "command": [
        "uvx",
        "verify-api-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add mgdsn-verify-api-mcp --command uvx --arg verify-api-mcp
```

### Hermes

```yaml
mcp_servers:
  mgdsn-verify-api-mcp:
    command: "uvx"
    args: ["verify-api-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "mgdsn-verify-api-mcp": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "verify-api-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add mgdsn-verify-api-mcp -t stdio -c uvx -a verify-api-mcp
```

### Other

```json
{
  "mcpServers": {
    "mgdsn-verify-api-mcp": {
      "command": "uvx",
      "args": [
        "verify-api-mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-19 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-18 (score 72, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-09-16 (score 57, +1)

No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-15 (score 56, −15)

- [security regression] Malware scan: pass → unverified

### 2026-09-14 (score 71, +16)

- [security improvement] Malware scan: unverified → pass

### 2026-09-12 (score 55, +1)

No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-10 (score 54, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-08 (score 53, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (8)

### `verify_citation` (~93 tokens)

Verify a citation: does it exist, is it retracted, and do the given title/authors/year/journal match the canonical record? Checked against Crossref (includes Retraction Watch data) with OpenAlex as a fallback when no DOI is given. Provide a doi and/or a title.

Input parameters:

- `authors`
- `doi`
- `journal`
- `title`
- `year`

### `verify_url` (~74 tokens)

Verify a URL: does it resolve, what's the final status and redirect chain, is it archived on the Wayback Machine, and (optionally) does expected text appear on the page. Checked via direct fetch and the Internet Archive.

Input parameters:

- `expected_content`
- `expected_date`
- `url` (string, required)

### `verify_package` (~95 tokens)

Verify a package: does it exist, is it deprecated or yanked, and does it have known vulnerabilities? Checked against the npm/PyPI/crates.io registry plus OSV.dev advisories. Catches an agent installing a hallucinated or squatted package name. ecosystem must be one of: npm, pypi, crates.

Input parameters:

- `ecosystem` (string, required)
- `name` (string, required)
- `version`

### `verify_repo` (~66 tokens)

Verify a GitHub repo: does it exist, is it archived or disabled? Catches an agent recommending or depending on a repo that's been renamed, taken down, or abandoned. Checked against the GitHub REST API.

Input parameters:

- `owner` (string, required)
- `repo` (string, required)

### `verify_case` (~78 tokens)

Verify a legal case citation: does it exist, and does the given case name match the canonical record? Catches a fabricated case citation, including a real-looking citation number paired with an invented case name. Checked against CourtListener. Does not check whether a case is still good law.

Input parameters:

- `case_name`
- `citation` (string, required)

### `verify_filing` (~107 tokens)

Verify an SEC filing: given a filer's CIK and a claimed accession number, does that filing actually exist, and does its form type/filing date match what's claimed? Checked against SEC EDGAR's submissions API. Catches a fabricated or misattributed filing citation, including a real-looking accession number paired with an invented form type or date.

Input parameters:

- `accession_number` (string, required)
- `cik` (string, required)
- `filed_date`
- `form_type`

### `verify_drug` (~105 tokens)

Verify an FDA drug record: given a claim_type ('approval', 'ndc', or 'recall') and its identifier, does that record actually exist, and does the given name match the canonical record? Checked against openFDA. Catches a fabricated or misattributed drug approval, NDC listing, or recall citation. Existence/status only, not medical advice.

Input parameters:

- `claim_type` (string, required)
- `expected_name`
- `identifier` (string, required)

### `verify_seller` (~129 tokens)

Verify an x402 seller before paying it: does it exist and respond with a well-formed 402 challenge, is its own declared input/output schema internally consistent, and is its payout address sanctioned? Checked live against the seller itself plus a sanctions oracle and on-chain wallet history (Base payTo addresses only). Confirms the checkable things about a seller check out -- not a guarantee of trustworthiness, which no free source can promise. method defaults to POST; set it to GET if that's what triggers the seller's 402.

Input parameters:

- `method`
- `resource_url` (string, required)

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/mgdsn-verify-api-mcp/verify-api-mcp#diagnostics

## Score history

- 2026-09-20: 73
- 2026-09-19: 73
- 2026-09-18: 72
- 2026-09-17: 57
- 2026-09-16: 57
- 2026-09-15: 56
- 2026-09-14: 71
- 2026-09-13: 55
- 2026-09-12: 55
- 2026-09-11: 54
- 2026-09-10: 54
- 2026-09-09: 53
- 2026-09-08: 53
- 2026-09-07: 52
- 2026-09-06: 52
- 2026-09-05: 51
- 2026-09-04: 51
- 2026-09-03: 51
- 2026-09-02: 51
- 2026-09-01: 50
- 2026-08-31: 50
- 2026-08-30: 49

## Common questions

### What is the Verify API MCP server?

Verify API is an MCP server listed in the public MCP registry as io.github.mgdsn/verify-api-mcp. Evidence-backed verification for citations, packages, repos, cases, filings, drugs, x402 sellers. This page covers its PyPI package (verify-api-mcp).

### Is the Verify API MCP server safe to use?

Verify API scores 73 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. 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 Verify API MCP server expose?

Verify API exposes 8 tools: verify_citation, verify_url, verify_package, verify_repo, verify_case, and 3 more. Their descriptions and schemas cost roughly 747 tokens of context every time the server is loaded.

### Is the Verify API MCP server still maintained?

Verify API is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- PyPI project: https://pypi.org/project/verify-api-mcp/
- Socket report: https://socket.dev/pypi/package/verify-api-mcp
- Repository: https://github.com/mgdsn/verify-api-mcp
- Changelog RSS feed: https://verifymcp.io/servers/mgdsn-verify-api-mcp/verify-api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/mgdsn-verify-api-mcp/verify-api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/mgdsn-verify-api-mcp/verify-api-mcp