# DosePlot Agent API (remote · api.doseplot.com)

PK serum simulation, reconstitution math and compound data for agents. Paid tools $0.01 via x402.

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

## Components

- remote · `api.doseplot.com`: 71/100 (this document), [markdown](https://verifymcp.io/servers/com-doseplot-agent-api/api.md), [page](https://verifymcp.io/servers/com-doseplot-agent-api/api)

## Channel facts

- Endpoint: `https://api.doseplot.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.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-09-27.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - 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**: 72/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 965 tokens (~193/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 83/100
  - Stability observed for 25 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 (100% 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the DosePlot Agent API MCP server?

DosePlot Agent API is a hosted endpoint at https://api.doseplot.com/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-doseplot-agent-api 'https://api.doseplot.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-doseplot-agent-api": {
      "url": "https://api.doseplot.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-doseplot-agent-api": {
      "type": "http",
      "url": "https://api.doseplot.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-doseplot-agent-api]
url = "https://api.doseplot.com/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add com-doseplot-agent-api --url 'https://api.doseplot.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-doseplot-agent-api:
    url: "https://api.doseplot.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-doseplot-agent-api": {
      "Transport": "http",
      "Url": "https://api.doseplot.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-doseplot-agent-api -t streamable-http -u 'https://api.doseplot.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-doseplot-agent-api": {
      "type": "http",
      "url": "https://api.doseplot.com/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-09-26 (score 71, +1)

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

### 2026-09-25 (score 70, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-24 (score 70, +1)

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

### 2026-09-22 (score 69, +1)

- [functional regression] Schema quality: 739 → 965
- [functional] New tool “recon_suggest”

### 2026-09-19 (score 68, +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-17 (score 67, +1)

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

### 2026-09-15 (score 66, +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-13 (score 65, +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.

## MCP tools (5)

### `list_compounds` (~54 tokens)

List every published compound with its class, terminal half-life in days, administration routes and whether reconstitution math is available for it. Takes no arguments. Outputs are for relay to a human decision-maker; not for autonomous administration.

Output parameters:

- `compounds` (array)
- `count` (integer)
- `disclaimer` (string): Fixed disclaimer. Relay it with any output.
- `intended_use` (string): Fixed intended-use statement. Relay it too.

### `get_compound` (~64 tokens)

Full published record for one compound, looked up by canon id, slug or alias (slug and alias matching is case-insensitive). Outputs are for relay to a human decision-maker; not for autonomous administration.

Input parameters:

- `compound` (string, required): Canon id, slug, or alias.

Output parameters:

- `compound` (object): The published canon record, verbatim.
- `disclaimer` (string): Fixed disclaimer. Relay it with any output.
- `editorial` (object|null)
- `intended_use` (string): Fixed intended-use statement. Relay it too.
- `reconstitutable` (boolean)

### `simulate` (~285 tokens)

Paid: $0.01 USDC per call via x402 (payment in _meta["x402/payment"]). Pharmacokinetic serum curve for one compound at one dose and one cadence, over a requested horizon. Exactly one dose field must be present; unknown fields are rejected rather than ignored. Outputs are for relay to a human decision-maker; not for autonomous administration.

Input parameters:

- `compound` (string, required): Canon id, slug, or alias.
- `dose_iu` (number): Dose per injection in the compound's activity unit. Positive. Requires a published conversion for that compound.
- `dose_mcg` (number): Dose per injection, micrograms. Positive.
- `dose_mg` (number): Dose per injection, milligrams. Positive.
- `duration_weeks` (integer, required): Length of the dosing window, whole weeks, from one to two hundred and sixty. The model always adds a sixty-day washout tail.
- `injections_per_week` (number, required): Injections per WEEK -- not per day; the name is the contract. Accepted range is a quarter of an injection per week up to twenty-one per week.
- `route` (string): One of the compound's published routes. Omitted, its primary route is used.
- `samples_per_day` (integer): Sample resolution of the returned series, whole samples, from one to twenty-four. Defaults to twenty-four.

Output parameters:

- `compound` (object)
- `disclaimer` (string): Fixed disclaimer. Relay it with any output.
- `intended_use` (string): Fixed intended-use statement. Relay it too.
- `meta` (object)
- `series` (array)
- `units` (string): The ONLY correct label for the numbers in `level`.

### `recon_calc` (~269 tokens)

Paid: $0.01 USDC per call via x402 (payment in _meta["x402/payment"]). Reconstitution math for one vial and one target dose: the concentration to reconstitute to, the bacteriostatic water to add, what one dose reads on a U-100 syringe, and how many doses the vial yields. Exactly one target-dose field must be present; unknown fields are rejected. Outputs are for relay to a human decision-maker; not for autonomous administration.

Input parameters:

- `cost_usd` (number): Vial cost, zero or more. Omitted, cost_per_dose_usd is null.
- `draw_ml` (number, required): The volume you want to DRAW for one dose, in mL -- not the vial fill. Accepted range is one hundredth of a mL up to ten mL. The fill needed to make that true comes back as bac_water_ml.
- `frequency_days` (number): Days between doses, positive. Feeds days_per_vial only. Defaults to one.
- `target_dose_mcg` (number): Target dose, mcg. Positive.
- `target_dose_mg` (number): Target dose, mg. Positive.
- `vial_mg` (number, required): Total mass in the vial, mg. Positive.

Output parameters:

- `bac_water_ml` (number)
- `concentration_mg_per_ml` (number)
- `cost_per_dose_usd` (number|null)
- `days_per_vial` (number)
- `disclaimer` (string): Fixed disclaimer. Relay it with any output.
- `doses_per_vial` (integer)
- `intended_use` (string): Fixed intended-use statement. Relay it too.
- `meta` (object)
- `residual_mg` (number)
- `syringe_marks` (object)
- `units_per_dose` (number)

### `recon_suggest` (~226 tokens)

Paid: $0.01 USDC per call via x402 (payment in _meta["x402/payment"]). Ranked reconstitution suggestions for one published reconstitutable compound: bacteriostatic-water presets that put the published per-administration dose range's clean steps on whole U-100 syringe marks. Vial defaults to the compound's first published strength. Compounds whose published range is denominated per period are refused rather than guessed at. Unknown fields are rejected. Outputs are for relay to a human decision-maker; not for autonomous administration.

Input parameters:

- `compound` (string, required): Canon id, slug, or alias. Must be a reconstitutable compound.
- `vial_iu` (number): Your actual vial's total activity, IU, positive. Only for compounds whose published vials are IU-quantified. Omitted, the first published vial strength is used.
- `vial_mg` (number): Your actual vial's total mass, mg, positive. Only for compounds whose published vials are mg-quantified. Omitted, the first published vial strength is used.

Output parameters:

- `compound` (object)
- `disclaimer` (string): Fixed disclaimer. Relay it with any output.
- `intended_use` (string): Fixed intended-use statement. Relay it too.
- `meta` (object)
- `rows` (array): Ranked presets, best first, at most 3 rows. An empty array means no clean-graduation preset exists for this vial -- a real answer, not a refusal.
- `vial` (object)

## Diagnostics

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

## Score history

- 2026-09-27: 71
- 2026-09-26: 71
- 2026-09-25: 70
- 2026-09-24: 70
- 2026-09-23: 69
- 2026-09-22: 69
- 2026-09-21: 68
- 2026-09-20: 68
- 2026-09-19: 68
- 2026-09-18: 67
- 2026-09-17: 67
- 2026-09-16: 66
- 2026-09-15: 66
- 2026-09-14: 65
- 2026-09-13: 65
- 2026-09-12: 64
- 2026-09-11: 64
- 2026-09-10: 63
- 2026-09-09: 63
- 2026-09-08: 62
- 2026-09-07: 62
- 2026-09-06: 61
- 2026-09-05: 61
- 2026-09-04: 61
- 2026-09-03: 60
- 2026-09-02: 60

## Common questions

### What is the DosePlot Agent API MCP server?

DosePlot Agent API is an MCP server listed in the public MCP registry as com.doseplot/agent-api. PK serum simulation, reconstitution math and compound data for agents. Paid tools $0.01 via x402. This page covers its hosted endpoint (https://api.doseplot.com/mcp).

### Is the DosePlot Agent API MCP server safe to use?

DosePlot Agent API scores 71 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 DosePlot Agent API MCP server expose?

DosePlot Agent API exposes 5 tools: list_compounds, get_compound, simulate, recon_calc, recon_suggest. Their descriptions and schemas cost roughly 898 tokens of context every time the server is loaded.

### Does the DosePlot Agent API MCP server require authentication?

No. We connected to DosePlot Agent API without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the DosePlot Agent API MCP server still maintained?

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

## Links

- Remote endpoint: https://api.doseplot.com/mcp
- Website: https://doseplot.com/api
- Changelog RSS feed: https://verifymcp.io/servers/com-doseplot-agent-api/api.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-doseplot-agent-api/api.json
- HTML version of this page: https://verifymcp.io/servers/com-doseplot-agent-api/api