# Dosidal: prescription medicine records for AI agents (remote · mcp.dosidal.ai)

Dosidal powers the agentic era of pharma. Prescription medicine records for AI agents and AI labs.

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

## Components

- remote · `mcp.dosidal.ai`: 64/100 (this document), [markdown](https://verifymcp.io/servers/dosidal-dosidal/mcp.md), [page](https://verifymcp.io/servers/dosidal-dosidal/mcp)

## Channel facts

- Endpoint: `https://mcp.dosidal.ai/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `2.6.0`

## 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**: 63/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 enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - 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**: 69/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 365 tokens (~121/item across 3 items; 3 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability check failed: schema churn in the 5 days we've observed: 7 tool removals, 0 breaking changes, 0 auth/transport breaks, 3 additions.
- **Tool Coverage**: 95/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 86% 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the Dosidal: prescription medicine records for AI agents MCP server?

Dosidal: prescription medicine records for AI agents is a hosted endpoint at https://mcp.dosidal.ai/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 dosidal-dosidal 'https://mcp.dosidal.ai/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "dosidal-dosidal": {
      "url": "https://mcp.dosidal.ai/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dosidal-dosidal": {
      "type": "http",
      "url": "https://mcp.dosidal.ai/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.dosidal-dosidal]
url = "https://mcp.dosidal.ai/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dosidal-dosidal": {
      "type": "remote",
      "url": "https://mcp.dosidal.ai/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dosidal-dosidal --url 'https://mcp.dosidal.ai/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  dosidal-dosidal:
    url: "https://mcp.dosidal.ai/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "dosidal-dosidal": {
      "Transport": "http",
      "Url": "https://mcp.dosidal.ai/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add dosidal-dosidal -t streamable-http -u 'https://mcp.dosidal.ai/mcp'
```

### Other

```json
{
  "mcpServers": {
    "dosidal-dosidal": {
      "type": "http",
      "url": "https://mcp.dosidal.ai/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-19 (score 64, 0)

- [functional] Server version: 2.6.0 → 2.6.3

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

- [security regression] Stability: 0.03 → fail
- [security regression] Tool “get_checkpoint” was removed
- [security regression] Tool “get_record” was removed
- [security regression] Tool “list_events_since” was removed
- [security regression] Tool “list_markets” was removed
- [security regression] Tool “lookup” was removed
- [security regression] Tool “related_records” was removed
- [security regression] Tool “verify_record” was removed
- [security] The server rewrote its instructions, which are the text every model session reads
- [functional regression] Schema quality: 90 → 121
- [functional regression] MCP protocol: pass → fail
- [functional improvement] Tool coverage: 53% → 86%
- [functional] Schema quality: fair → good
- [functional] MCP protocol version: 2025-11-25 → 2025-06-18
- [functional] Server version: 2.5.0 → 2.6.0
- [functional] Server version: 2.4.0 → 2.5.0
- [functional] New tool “changes”
- [functional] New tool “fetch”
- [functional] New tool “verify_card”

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

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “get_checkpoint” rewrote its description, which is the text the model reads
- [security] Tool “get_record” rewrote its description, which is the text the model reads
- [security] Tool “list_events_since” rewrote its description, which is the text the model reads
- [security] Tool “list_markets” rewrote its description, which is the text the model reads
- [security] Tool “lookup” rewrote its description, which is the text the model reads
- [security] Tool “related_records” rewrote its description, which is the text the model reads
- [security] Tool “verify_record” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 80 → 90
- [functional improvement] Stability: unverified → 0.03
- [functional] Server version: 2.2.1 → 2.4.0
- [functional] Server version: 2.1.0 → 2.2.1

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

First indexed and scored.

## MCP tools (3)

### `fetch` (~110 tokens)

Fetch a medicine's card. Give the card's address or any one of three codes: the barcode on the pack (Global Trade Item Number, GTIN), the national pack code, or the authorisation number. Returns the signed card with its stamp; or a list of cards where several share the code; or an empty list. Each fetch leaves a signed receipt.

Input parameters:

- `code` (string, required): a card's address, or a pack barcode (GTIN), a national pack code or an authorisation number

### `verify_card` (~31 tokens)

Check a card's signature against Dosidal's public keys.

Input parameters:

- `card` (object, required): the card as fetched

### `changes` (~91 tokens)

List the real changes to a country's cards since a date.

Input parameters:

- `after` (integer): read on from this entry (the value of next)
- `limit` (integer)
- `market` (string, required): market code, e.g. FR, US, JP
- `reissues` (boolean): also list reissues, each marked reissued
- `since` (string, required): a date, YYYY-MM-DD

## Diagnostics

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

## Score history

- 2026-11-21: 64
- 2026-11-20: 64
- 2026-11-19: 64
- 2026-11-18: 64
- 2026-11-17: 63
- 2026-11-16: 63

## Common questions

### What is the Dosidal: prescription medicine records for AI agents MCP server?

Dosidal: prescription medicine records for AI agents is an MCP server listed in the public MCP registry as io.github.Dosidal/dosidal. Dosidal powers the agentic era of pharma. Prescription medicine records for AI agents and AI labs. This page covers its hosted endpoint (https://mcp.dosidal.ai/mcp).

### Is the Dosidal: prescription medicine records for AI agents MCP server safe to use?

Dosidal: prescription medicine records for AI agents scores 64 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 Dosidal: prescription medicine records for AI agents MCP server expose?

Dosidal: prescription medicine records for AI agents exposes 3 tools: fetch, verify_card, changes. Their descriptions and schemas cost roughly 232 tokens of context every time the server is loaded.

### Does the Dosidal: prescription medicine records for AI agents MCP server require authentication?

No. We connected to Dosidal: prescription medicine records for AI agents without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Dosidal: prescription medicine records for AI agents MCP server still maintained?

Dosidal: prescription medicine records for AI agents 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 Dosidal: prescription medicine records for AI agents MCP server?

VerifyMCP ran 12 checks on Dosidal: prescription medicine records for AI agents, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Dosidal: prescription medicine records for AI agents: HTTPS. 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://mcp.dosidal.ai/mcp
- Repository: https://github.com/Dosidal/dose-10060
- Website: https://dosidal.ai/
- Changelog RSS feed: https://verifymcp.io/servers/dosidal-dosidal/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/dosidal-dosidal/mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/dosidal-dosidal/mcp.json
- HTML version of this page: https://verifymcp.io/servers/dosidal-dosidal/mcp
