AlphaCitation reference lookup
REMOTE · ALPHACITATION.COM
Is a medicine approved in a market? US, EU/EEA regulators; others not settled. Not medical advice.
Available components
Last scanned (21 hours ago)
Scores higher than 62% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Health and Science
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 Security80
- 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 check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability70
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
- Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (75% 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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
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 →
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.
- 21 Nov 26 +1
- Schema quality: 1432 → 1586 ▼ functional
- “check_drug_approval_fda_eu” reworded the description of “indication” cosmetic
- “lookup_medicine_evidence” reworded the description of “indication” cosmetic
- 20 Nov 26 +3
- 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
- Schema quality: 458 → 1432 ▼ functional
- 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” functional
- “check_drug_approval_fda_eu” reworded the description of “indication” cosmetic
- “lookup_medicine_evidence” reworded the description of “indication” cosmetic
- 19 Nov 26 0
- Tool “lookup_medicine_evidence” rewrote its description, which is the text the model reads security
- Schema quality: 414 → 458 ▼ functional
- 18 Nov 26 +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.
- 17 Nov 26 0
- 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 security
- Schema quality: 352 → 414 ▼ functional
- Schema quality: 352 → 410 ▼ functional
- Stability: unverified → 0.03 ▲ functional
- Server version: 1.0.0 → 1.0.1 functional
- Tool “lookup_medicine_evidence” changed its title: Which source settles a claim about a medicine → Is a medicine approved in a market? cosmetic
- 16 Nov 26 70
First indexed and scored.
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://alphacitation.com/api/v1/reference/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.alphacitation.com | CN=YR1,O=Let's Encrypt,C=US | 6 Nov 2026 | 4 Feb 2027 | RSA 2048 | SHA256-RSA | 51c64ca925e4ea2cecfcfc87eecc0c19904 |
| SANs: *.alphacitation.com, alphacitation.com | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of alphacitation.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| alphacitation.com. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
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=63072000; includeSubDomains; preload |
| content-security-policy | base-uri 'self'; object-src 'none'; frame-ancestors 'none'; form-action 'self' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), payment=(), usb=(), browsing-topics=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://alphacitation.com/api/v1/reference/mcp | Verified | 200 | |
| http (plaintext) | http://alphacitation.com/api/v1/reference/mcp | HTTPS enforced | 308 | https://alphacitation.com/api/v1/reference/mcp |
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 →
check_drug_approval_fda_eu Is a drug FDA or EU approved? ~2,445
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | The market: an ISO 3166-1 alpha-2 code (US, AE, SA, DE) or EU. |
| medicine | string | yes | 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 | yes | P1: registered or authorised in the market. P2: authorised for an indication. |
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | – |
| relation | string | yes | – |
| scope | object | yes | – |
| status | string | yes | – |
| summary | string | yes | – |
| unresolved | array | yes | – |
No examples provided.
lookup_medicine_evidence Is a medicine approved in a market? ~2,441
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | The market: an ISO 3166-1 alpha-2 code (US, AE, SA, DE) or EU. |
| medicine | string | yes | 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 | yes | P1: registered or authorised in the market. P2: authorised for an indication. |
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | – |
| relation | string | yes | – |
| scope | object | yes | – |
| status | string | yes | – |
| summary | string | yes | – |
| unresolved | array | yes | – |
No examples provided.
lookup_precedent_ruling A numbered AlphaCitation ruling on an evidence conflict ~185
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.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | – | The date to resolve the current record for, YYYY-MM-DD. Defaults to today (UTC). |
| id | string | yes | The ruling identifier, for example ACPREC-2026-0001. |
No output schema declared.
No examples provided.
read_drug_label_fda_eu What does a drug's FDA or EU label say? ~1,015
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | US (FDA) or EU (centrally authorised medicines). |
| medicine | string | yes | 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 | yes | 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… |
| Name | Type | Req | Description |
|---|---|---|---|
| abstention | object|null | – | – |
| attribution | array | yes | – |
| decidesUse | boolean | – | – |
| records | array | yes | – |
| status | string | yes | – |
| summary | string | yes | – |
| unresolved | array | yes | – |
| verdict | object|null | – | – |
No examples provided.
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.
remote · alphacitation.com
claude mcp add --transport http com-alphacitation-reference 'https://alphacitation.com/api/v1/reference/mcp'
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.