DosePlot Agent API
REMOTE · API.DOSEPLOT.COM · SCANNED SEP 27
PK serum simulation, reconstitution math and compound data for agents. Paid tools $0.01 via x402.
Available components
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 Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 Usability72
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management83
- Stability observed for 25 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 (100% 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
remote · api.doseplot.com
claude mcp add --transport http com-doseplot-agent-api 'https://api.doseplot.com/mcp'
{
"mcpServers": {
"com-doseplot-agent-api": {
"url": "https://api.doseplot.com/mcp"
}
}
} {
"servers": {
"com-doseplot-agent-api": {
"type": "http",
"url": "https://api.doseplot.com/mcp"
}
}
} [mcp_servers.com-doseplot-agent-api] url = "https://api.doseplot.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-doseplot-agent-api": {
"type": "remote",
"url": "https://api.doseplot.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-doseplot-agent-api --url 'https://api.doseplot.com/mcp' --transport streamable-http
mcp_servers:
com-doseplot-agent-api:
url: "https://api.doseplot.com/mcp" {
"McpServers": {
"com-doseplot-agent-api": {
"Transport": "http",
"Url": "https://api.doseplot.com/mcp"
}
}
} assistant mcp add com-doseplot-agent-api -t streamable-http -u 'https://api.doseplot.com/mcp'
{
"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.
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.
- 26 Sept 26 +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.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 +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.
- 22 Sept 26 +1
- Schema quality: 739 → 965 ▼ functional
- New tool “recon_suggest” functional
- 19 Sept 26 +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.
- 17 Sept 26 +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.
- 15 Sept 26 +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.
- 13 Sept 26 +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.
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 27 Sept 2026 · Probed https://api.doseplot.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=doseplot.com | CN=WE1,O=Google Trust Services,C=US | 21 Aug 2026 | 19 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | b9f0959c64d9eaa30ef1af3193d0e302 |
| SANs: doseplot.com, api.doseplot.com, *.api.doseplot.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.doseplot.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| doseplot.com. | absent | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.doseplot.com/mcp | Verified | 200 | |
| http (plaintext) | http://api.doseplot.com/mcp | Inconclusive | 405 |
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 →
get_compound ~64
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.
| Name | Type | Req | Description |
|---|---|---|---|
| compound | string | yes | Canon id, slug, or alias. |
| Name | Type | Req | Description |
|---|---|---|---|
| compound | object | yes | The published canon record, verbatim. |
| disclaimer | string | yes | Fixed disclaimer. Relay it with any output. |
| editorial | object|null | yes | – |
| intended_use | string | yes | Fixed intended-use statement. Relay it too. |
| reconstitutable | boolean | yes | – |
No examples provided.
list_compounds ~54
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| compounds | array | yes | – |
| count | integer | yes | – |
| disclaimer | string | yes | Fixed disclaimer. Relay it with any output. |
| intended_use | string | yes | Fixed intended-use statement. Relay it too. |
No examples provided.
recon_calc ~269
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.
| Name | Type | Req | Description |
|---|---|---|---|
| cost_usd | number | – | Vial cost, zero or more. Omitted, cost_per_dose_usd is null. |
| draw_ml | number | yes | 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 | yes | Total mass in the vial, mg. Positive. |
| Name | Type | Req | Description |
|---|---|---|---|
| bac_water_ml | number | yes | – |
| concentration_mg_per_ml | number | yes | – |
| cost_per_dose_usd | number|null | yes | – |
| days_per_vial | number | yes | – |
| disclaimer | string | yes | Fixed disclaimer. Relay it with any output. |
| doses_per_vial | integer | yes | – |
| intended_use | string | yes | Fixed intended-use statement. Relay it too. |
| meta | object | yes | – |
| residual_mg | number | yes | – |
| syringe_marks | object | yes | – |
| units_per_dose | number | yes | – |
No examples provided.
recon_suggest ~226
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.
| Name | Type | Req | Description |
|---|---|---|---|
| compound | string | yes | 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| compound | object | yes | – |
| disclaimer | string | yes | Fixed disclaimer. Relay it with any output. |
| intended_use | string | yes | Fixed intended-use statement. Relay it too. |
| meta | object | yes | – |
| rows | array | yes | 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 | yes | – |
No examples provided.
simulate ~285
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.
| Name | Type | Req | Description |
|---|---|---|---|
| compound | string | yes | 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 | yes | 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 | yes | 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| compound | object | yes | – |
| disclaimer | string | yes | Fixed disclaimer. Relay it with any output. |
| intended_use | string | yes | Fixed intended-use statement. Relay it too. |
| meta | object | yes | – |
| series | array | yes | – |
| units | string | yes | The ONLY correct label for the numbers in `level`. |
No examples provided.
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.