ivive.app
REMOTE · API.IVIVE.APP
Human hepatic clearance from in-vitro CLint, with the error band measured on known drugs.
Available components
Last scanned (21 hours ago)
Scores higher than 79% of remote servers
Reachable. Last reached 4 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. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. 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 Usability57
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1512 tokens (~252/item across 6 items; 6 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 Management60
- Stability observed for 18 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 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
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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +8
- Authorization: unverified → partial ▲ security
- Tool coverage: 89% → 100% ▲ functional
- Server version: 1.0.2 → 1.0.3 functional
- “input_sensitivity” reworded the description of “clint_range” cosmetic
- “input_sensitivity” reworded the description of “fu_mic_range” cosmetic
- “predict_inputs” reworded the description of “assay_type” cosmetic
- “scale_to_human” reworded the description of “animals” cosmetic
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Oct 26 +5
- HSTS header: fail → pass ▲ security
- Tool “similar_drugs” rewrote its description, which is the text the model reads security
- Tool “target_clint” rewrote its description, which is the text the model reads security
- Schema quality: 200 → 235 ▼ functional
- Tool coverage: 63% → 89% ▲ functional
- Server version: 1.0.1 → 1.0.2 functional
- “predict_inputs” reworded the description of “smiles” cosmetic
- “similar_drugs” reworded the description of “n” cosmetic
- “similar_drugs” reworded the description of “smiles” cosmetic
- “target_clint” reworded the description of “assay_type” cosmetic
- “target_clint” reworded the description of “fu_mic” cosmetic
- “target_clint” reworded the description of “fu_p” cosmetic
- “target_clint” reworded the description of “model” cosmetic
- “target_clint” reworded the description of “rb” cosmetic
- “target_clint” reworded the description of “species” cosmetic
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 4 Nov 2026 · Probed https://api.ivive.app/mcp/
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=api.ivive.app | CN=YE1,O=Let's Encrypt,C=US | 16 Oct 2026 | 14 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 540b97981487d96a6d987f7f5b6489aff40 |
| SANs: api.ivive.app | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.ivive.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| ivive.app. | 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.ivive.app/mcp/ | Verified | 200 | |
| http (plaintext) | http://api.ivive.app/mcp/ | HTTPS enforced | 308 | https://api.ivive.app/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 →
calc_clhep ~401
Hepatic and plasma clearance from in-vitro CLint, fu,mic and fu,p (IVIVE), with the observed-CL band and applicability warnings. If fu,p or fu,mic came from predict_inputs, tell the user the result rests on predicted inputs.
| Name | Type | Req | Description |
|---|---|---|---|
| assay_type | string | – | Assay type for CLint scaling. microsomes: uses MPPGL (mg/g) × 1e-3; hepatocytes: uses HPGL (×10⁶ cells/g) × 1e-3. |
| clint | number | yes | Intrinsic clearance (µL/min/mg microsomal protein). Use ge=0: zero clearance is physiologically valid. |
| clint_censored | boolean | – | Set when the assay reported CLint below its limit of quantification and `clint` is that limit rather than a measurement. CLint then lies in [0, clint), so every clearance output is an upper bound: `u… |
| correction_id | – | – | Saved lab correction (/api/correction-equations) to apply. Must match species and assay_type. Corrects predicted plasma CL and replaces the reference band with one from the lab's compounds. |
| fu_mic | number | yes | Unbound fraction in microsomes (0–1). Corrects for non-specific microsomal binding. |
| fu_p | number | yes | Unbound fraction in plasma (0–1). Plasma protein binding correction. |
| model | string | – | IVIVE model. well-stirred (venous equilibrium) or parallel-tube (sinusoidal perfusion). |
| rb | number | – | Blood-to-plasma concentration ratio. fu_b = fu_p / Rb. Output is blood clearance. |
| species | string | yes | Species for physiological parameters (Qh, MPPGL, liver weight). |
No output schema declared.
No examples provided.
input_sensitivity ~465
How far plasma CL moves as each input is varied over a range, e.g. a predicted fu,p over its 50% range.
| Name | Type | Req | Description |
|---|---|---|---|
| assay_type | string | – | Assay type for CLint scaling. microsomes: uses MPPGL (mg/g) × 1e-3; hepatocytes: uses HPGL (×10⁶ cells/g) × 1e-3. |
| clint | number | yes | Intrinsic clearance (µL/min/mg microsomal protein). Use ge=0: zero clearance is physiologically valid. |
| clint_censored | boolean | – | Set when the assay reported CLint below its limit of quantification and `clint` is that limit rather than a measurement. CLint then lies in [0, clint), so every clearance output is an upper bound: `u… |
| clint_range | – | – | CLint range in the assay's units, e.g. {"low": 10, "high": 40}. |
| correction_id | – | – | Saved lab correction (/api/correction-equations) to apply. Must match species and assay_type. Corrects predicted plasma CL and replaces the reference band with one from the lab's compounds. |
| fu_mic | number | yes | Unbound fraction in microsomes (0–1). Corrects for non-specific microsomal binding. |
| fu_mic_range | – | – | fu,mic range (0–1), e.g. {"low": 0.5, "high": 0.9}. |
| fu_p | number | yes | Unbound fraction in plasma (0–1). Plasma protein binding correction. |
| fu_p_range | – | – | A predicted fu,p carries its 50% range; pass it to see what it costs. |
| model | string | – | IVIVE model. well-stirred (venous equilibrium) or parallel-tube (sinusoidal perfusion). |
| rb | number | – | Blood-to-plasma concentration ratio. fu_b = fu_p / Rb. Output is blood clearance. |
| species | string | yes | Species for physiological parameters (Qh, MPPGL, liver weight). |
No output schema declared.
No examples provided.
predict_inputs ~104
Predict fu,p and fu,inc from a SMILES, with structure-only human CL and Vss as second opinions. Predictions, not measurements; check the applicability verdict.
| Name | Type | Req | Description |
|---|---|---|---|
| assay_type | string | – | Incubation fu,inc is predicted for: microsomes or hepatocytes. |
| concentration | number | – | Incubation concentration: mg microsomal protein/mL, or 10⁶ hepatocytes/mL. |
| smiles | string | yes | Structure as SMILES. |
No output schema declared.
No examples provided.
scale_to_human ~105
Predict human plasma CL from observed animal in-vivo CL (rat, dog, monkey), every applicable method with its measured error. Observed animal CL only, never predicted.
| Name | Type | Req | Description |
|---|---|---|---|
| animals | array | yes | One entry per species, e.g. [{"species": "rat", "cl": 40}, {"species": "dog", "cl": 12}]. |
| fu_p_human | – | – | Human unbound fraction, needed by the fu-corrected methods |
No output schema declared.
No examples provided.
similar_drugs ~112
Nearest reference drugs to a SMILES (Tanimoto, Morgan radius 2), each with measured human plasma CL and the CL IVIVE predicted from its measured inputs. Use it to judge how far to trust calc_clhep for this chemotype: if IVIVE missed on the neighbours, expect it to miss here. Returns neighbours only, not a prediction for the query.
| Name | Type | Req | Description |
|---|---|---|---|
| n | integer | – | How many reference drugs to return, nearest first. |
| smiles | string | yes | Structure as SMILES. |
No output schema declared.
No examples provided.
target_clint ~252
The in-vitro CLint an assay must read for a compound to reach a target plasma clearance (mL/min/kg): calc_clhep run backwards, e.g. to set a CLint cut-off for a screening cascade. Needs fu,mic and fu,p; refuses a target at or above the liver blood flow ceiling and returns that ceiling. Uncorrected IVIVE, so no error band.
| Name | Type | Req | Description |
|---|---|---|---|
| assay_type | string | – | Assay the CLint is for; sets its units (µL/min/mg protein or µL/min/10⁶ cells). |
| fu_mic | number | yes | Unbound fraction in the incubation (0–1) the CLint would be measured at. |
| fu_p | number | yes | Unbound fraction in plasma (0–1). |
| model | string | – | IVIVE liver model to invert. |
| rb | number | – | Blood-to-plasma concentration ratio; raises the plasma CL ceiling (Qh × Rb). |
| species | string | yes | Species whose liver blood flow and scaling factors apply. |
| target_clp | number | yes | Plasma clearance to aim for (mL/min/kg). Must be below hepatic blood flow × Rb. |
No output schema declared.
No examples provided.
How do I install the ivive.app MCP server?
ivive.app is a hosted endpoint at https://api.ivive.app/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.ivive.app
claude mcp add --transport http app-ivive-ivive 'https://api.ivive.app/mcp/'
What is the ivive.app MCP server?
ivive.app is an MCP server listed in the public MCP registry as app.ivive/ivive. Human hepatic clearance from in-vitro CLint, with the error band measured on known drugs. This page covers its hosted endpoint (https://api.ivive.app/mcp/).
Is the ivive.app MCP server safe to use?
ivive.app scores 79 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 ivive.app MCP server expose?
ivive.app exposes 6 tools: predict_inputs, calc_clhep, target_clint, input_sensitivity, similar_drugs, scale_to_human. Their descriptions and schemas cost roughly 1,439 tokens of context every time the server is loaded.
Does the ivive.app MCP server require authentication?
No. We connected to ivive.app without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the ivive.app MCP server still maintained?
ivive.app is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.