# AlphaCitation reference lookup (remote · alphacitation.com)

Is a medicine approved in a market? US, EU/EEA regulators; others not settled. Not medical advice.

- Trust score: 75/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `alphacitation.com`: 75/100 (this document), [markdown](https://verifymcp.io/servers/com-alphacitation-reference/api-v1-reference-mcp.md), [page](https://verifymcp.io/servers/com-alphacitation-reference/api-v1-reference-mcp)

## Channel facts

- Endpoint: `https://alphacitation.com/api/v1/reference/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.4`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 70/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 6347 tokens (~1586/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 17/100
  - Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (75% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 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 AlphaCitation reference lookup MCP server?

AlphaCitation reference lookup is a hosted endpoint at https://alphacitation.com/api/v1/reference/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.

### Claude

```bash
claude mcp add --transport http com-alphacitation-reference 'https://alphacitation.com/api/v1/reference/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-alphacitation-reference": {
      "url": "https://alphacitation.com/api/v1/reference/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-alphacitation-reference": {
      "type": "http",
      "url": "https://alphacitation.com/api/v1/reference/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-alphacitation-reference]
url = "https://alphacitation.com/api/v1/reference/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-alphacitation-reference": {
      "type": "remote",
      "url": "https://alphacitation.com/api/v1/reference/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-alphacitation-reference --url 'https://alphacitation.com/api/v1/reference/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-alphacitation-reference:
    url: "https://alphacitation.com/api/v1/reference/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-alphacitation-reference": {
      "Transport": "http",
      "Url": "https://alphacitation.com/api/v1/reference/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-alphacitation-reference -t streamable-http -u 'https://alphacitation.com/api/v1/reference/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-alphacitation-reference": {
      "type": "http",
      "url": "https://alphacitation.com/api/v1/reference/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## 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-11-21 (score 75, +1)

- [functional regression] Schema quality: 1432 → 1586
- [cosmetic] “check_drug_approval_fda_eu” reworded the description of “indication”
- [cosmetic] “lookup_medicine_evidence” reworded the description of “indication”

### 2026-11-20 (score 74, +3)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “lookup_medicine_evidence” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 458 → 1432
- [functional improvement] Tool coverage: 50% → 75%
- [functional] The server now declares the “prompts” capability
- [functional] First check of Schema quality: 100
- [functional] Schema quality: good → excellent
- [functional] New prompt “check_approval_on_date”
- [functional] New prompt “is_drug_fda_approved”
- [functional] New prompt “is_medicine_approved”
- [functional] Server version: 1.0.1 → 1.0.4
- [functional] New tool “check_drug_approval_fda_eu”
- [functional] New tool “read_drug_label_fda_eu”
- [cosmetic] “check_drug_approval_fda_eu” reworded the description of “indication”
- [cosmetic] “lookup_medicine_evidence” reworded the description of “indication”

### 2026-11-19 (score 71, 0)

- [security] Tool “lookup_medicine_evidence” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 414 → 458

### 2026-11-18 (score 71, +1)

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

### 2026-11-17 (score 70, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “lookup_medicine_evidence” rewrote its description, which is the text the model reads
- [security] Tool “lookup_precedent_ruling” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 352 → 414
- [functional regression] Schema quality: 352 → 410
- [functional improvement] Stability: unverified → 0.03
- [functional] Server version: 1.0.0 → 1.0.1
- [cosmetic] Tool “lookup_medicine_evidence” changed its title: Which source settles a claim about a medicine → Is a medicine approved in a market?

### 2026-11-16 (score 70)

First indexed and scored.

## MCP tools (4)

### `check_drug_approval_fda_eu` (~2445 tokens)

Is a drug FDA or EU approved?

Answers whether a drug or medicine is approved, authorised, licensed or registered in a country or in the EU (for example, whether it is FDA approved in the US), or approved there for a condition, today or on a past date, and which official record settles that. Records are held for the US (the FDA's approval record on Drugs@FDA for whether a medicine is approved, and the prescribing information on DailyMed, as submitted to the FDA, for what it is approved for) and, for centrally authorised medicines, for the EU and EEA (the European Commission's product information), and each answer resting on one carries its pointer URL. For any other market, the answer names that market's competent authority and where its registration record is published, each where it is identified, and says which is not; the claim is unresolved there, or supported, never settled, by the authorisation holder's own label. For one medicine, one market and one date, the answer gives which source settles whether the medicine is registered (P1) or authorised for an indication (P2), what that source says about the claim where its content has been checked, where this market's label differs from the US and EU labels, and what is unresolved. supported_attested means the authorisation holder's own approved label, read under the attestation conditions, states the claim; it never settles it. Where that label does not state the indication, or its content has not been checked, the answer is unresolved. An unresolved answer means AlphaCitation cannot currently verify the claim from a held record; it is not evidence about the medicine's status. Every answer that does not settle carries abstention, one reason code (insufficient_evidence, authority_inaccessible, conflicting_records, stale_evidence, unsupported_claim_type, snapshot_only) with its meaning.

Input parameters:

- `date` (string): The date the claim is about, YYYY-MM-DD. Defaults to today (UTC).
- `indication` (string): Required for P2: one indication from the published list. allergic_fungal_rhinosinusitis: allergic fungal rhinosinusitis; alopecia_areata: alopecia areata; ankylosing_spondylitis: ankylosing spondylit…
- `market` (string, required): The market: an ISO 3166-1 alpha-2 code (US, AE, SA, DE) or EU.
- `medicine` (string, required): The brand or active substance name, exactly (for example Mounjaro or tirzepatide).
- `populationMinAgeYears` (integer): Optional for P2: the youngest age the claim says the indication covers.
- `proposition` (string, required): P1: registered or authorised in the market. P2: authorised for an indication.

Output parameters:

- `abstention` (object|null): Null when settled. Otherwise one reason code: insufficient_evidence (route search_further): No held record settles the claim for this market and date. authority_inaccessible (route retry_later): The…
- `comparison` (array)
- `competentAuthorities` (array)
- `indicationScope` (object|null): Where the regulator recorded that a use is not a separate indication, though its benefit is stated in the product information and the use is covered by an existing indication: the three apart, with t…
- `inspection` (object)
- `notes` (array)
- `records` (array)
- `relation` (string)
- `scope` (object)
- `status` (string)
- `summary` (string)
- `unresolved` (array)

### `lookup_medicine_evidence` (~2441 tokens)

Is a medicine approved in a market?

Answers whether a drug or medicine is approved, authorised, licensed or registered in a country or in the EU (for example, whether it is FDA approved in the US), or approved there for a condition, today or on a past date, and which official record settles that. Records are held for the US (the FDA's approval record on Drugs@FDA for whether a medicine is approved, and the prescribing information on DailyMed, as submitted to the FDA, for what it is approved for) and, for centrally authorised medicines, for the EU and EEA (the European Commission's product information), and each answer resting on one carries its pointer URL. For any other market, the answer names that market's competent authority and where its registration record is published, each where it is identified, and says which is not; the claim is unresolved there, or supported, never settled, by the authorisation holder's own label. For one medicine, one market and one date, the answer gives which source settles whether the medicine is registered (P1) or authorised for an indication (P2), what that source says about the claim where its content has been checked, where this market's label differs from the US and EU labels, and what is unresolved. supported_attested means the authorisation holder's own approved label, read under the attestation conditions, states the claim; it never settles it. Where that label does not state the indication, or its content has not been checked, the answer is unresolved. An unresolved answer means AlphaCitation cannot currently verify the claim from a held record; it is not evidence about the medicine's status. Every answer that does not settle carries abstention, one reason code (insufficient_evidence, authority_inaccessible, conflicting_records, stale_evidence, unsupported_claim_type, snapshot_only) with its meaning.

Input parameters:

- `date` (string): The date the claim is about, YYYY-MM-DD. Defaults to today (UTC).
- `indication` (string): Required for P2: one indication from the published list. allergic_fungal_rhinosinusitis: allergic fungal rhinosinusitis; alopecia_areata: alopecia areata; ankylosing_spondylitis: ankylosing spondylit…
- `market` (string, required): The market: an ISO 3166-1 alpha-2 code (US, AE, SA, DE) or EU.
- `medicine` (string, required): The brand or active substance name, exactly (for example Mounjaro or tirzepatide).
- `populationMinAgeYears` (integer): Optional for P2: the youngest age the claim says the indication covers.
- `proposition` (string, required): P1: registered or authorised in the market. P2: authorised for an indication.

Output parameters:

- `abstention` (object|null): Null when settled. Otherwise one reason code: insufficient_evidence (route search_further): No held record settles the claim for this market and date. authority_inaccessible (route retry_later): The…
- `comparison` (array)
- `competentAuthorities` (array)
- `indicationScope` (object|null): Where the regulator recorded that a use is not a separate indication, though its benefit is stated in the product information and the use is covered by an existing indication: the three apart, with t…
- `inspection` (object)
- `notes` (array)
- `records` (array)
- `relation` (string)
- `scope` (object)
- `status` (string)
- `summary` (string)
- `unresolved` (array)

### `read_drug_label_fda_eu` (~1015 tokens)

What does a drug's FDA or EU label say?

Answers what a drug's or medicine's official FDA label (the US prescribing information) or EU summary of product characteristics (SmPC) says, and its FDA approval or EU authorisation facts, today or on a past date: what it is approved or authorised for and in whom, dosage, contraindications, the boxed warning, warnings and precautions, use in pregnancy, breastfeeding, children and older people, adverse reactions, interactions, overdose, pharmacology, storage, and the label's version history. For the US it reads the application holder's label as published on DailyMed and the FDA's approval record on Drugs@FDA; for the EU it reads each SmPC in the European Commission's product information as published by the EMA, and the EMA's medicines data. Each answer gives the record's own words for the section asked, with the section number, the document's version, its effective date, the SHA-256 of the exact document read and its address, and the source to acknowledge. Where a product information holds several SmPCs (strengths or forms), each is given apart. The indications text is the record's statement; whether a particular use falls within it is not decided, except for an indication from the published list, where the reference lookup's own answer is given beside it. Where the record cannot be read, matched or confirmed for the date, no text is given: the answer is unresolved, with one reason code (insufficient_evidence, authority_inaccessible, conflicting_records, stale_evidence, unsupported_claim_type, snapshot_only) and its meaning.

Input parameters:

- `application` (string): Optional: the exact application, a US NDA, ANDA or BLA number (for example ANDA078071) or an EMA product number (for example EMEA/H/C/002677), so a generic or a duplicate authorisation is answered fo…
- `date` (string): The date the question is about, YYYY-MM-DD. Defaults to today (UTC).
- `indication` (string): Optional, with topic indications: an indication from the published list, to add the reference lookup's own answer for it.
- `market` (string, required): US (FDA) or EU (centrally authorised medicines).
- `medicine` (string, required): The brand or active substance name, exactly (for example Jardiance or empagliflozin).
- `product` (string): Optional: a strength or form as the label names it (for example 395 mg, or solution for injection), to choose among several SmPCs or labels.
- `section` (string): Optional, with topic history and since: the section whose change is shown.
- `since` (string): Optional, with topic history and section: show what changed in the section between the version published on this date (YYYY-MM-DD) and the current one.
- `topic` (string, required): What to read. approval: whether and since when it is approved or authorised, its current status, application or product number and holder; indications: what it is approved or authorised for, and in w…

Output parameters:

- `abstention` (object|null)
- `attribution` (array)
- `decidesUse` (boolean)
- `records` (array)
- `status` (string)
- `summary` (string)
- `unresolved` (array)
- `verdict` (object|null)

### `lookup_precedent_ruling` (~185 tokens)

A numbered AlphaCitation ruling on an evidence conflict

For one ruling identifier (ACPREC-YYYY-NNNN): what was decided about an evidence conflict, why, on which records, its status now (settled, unresolved or superseded) and its RFC 3161 timestamp where one has been issued, together with a fresh lookup of the current governing record for the ruling's medicine, market and date where the ruling names one. A ruling is not evidence and decides no claim today; the current governing record does, and the ruling records only how the earlier conflict was decided. Where no current record is held, the answer names the competent authority and where its own record is published.

Input parameters:

- `date` (string): The date to resolve the current record for, YYYY-MM-DD. Defaults to today (UTC).
- `id` (string, required): The ruling identifier, for example ACPREC-2026-0001.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-alphacitation-reference/api-v1-reference-mcp#diagnostics

## Score history

- 2026-11-21: 75
- 2026-11-20: 74
- 2026-11-19: 71
- 2026-11-18: 71
- 2026-11-17: 70
- 2026-11-16: 70

## Common questions

### What is the AlphaCitation reference lookup MCP server?

AlphaCitation reference lookup is an MCP server listed in the public MCP registry as com.alphacitation/reference. Is a medicine approved in a market? US, EU/EEA regulators; others not settled. Not medical advice. This page covers its hosted endpoint (https://alphacitation.com/api/v1/reference/mcp).

### Is the AlphaCitation reference lookup MCP server safe to use?

AlphaCitation reference lookup scores 75 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 AlphaCitation reference lookup MCP server expose?

AlphaCitation reference lookup exposes 4 tools: check_drug_approval_fda_eu, lookup_medicine_evidence, read_drug_label_fda_eu, lookup_precedent_ruling. Their descriptions and schemas cost roughly 6,086 tokens of context every time the server is loaded.

### Does the AlphaCitation reference lookup MCP server require authentication?

No. We connected to AlphaCitation reference lookup without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the AlphaCitation reference lookup MCP server still maintained?

AlphaCitation reference lookup 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 AlphaCitation reference lookup MCP server?

VerifyMCP ran 13 checks on AlphaCitation reference lookup, 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.

## Links

- Remote endpoint: https://alphacitation.com/api/v1/reference/mcp
- Repository: https://github.com/alphacitation/alphacitation-reference
- Website: https://alphacitation.com/reference
- Changelog RSS feed: https://verifymcp.io/servers/com-alphacitation-reference/api-v1-reference-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-alphacitation-reference/api-v1-reference-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-alphacitation-reference/api-v1-reference-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-alphacitation-reference/api-v1-reference-mcp
