Ivive MCP server

• Registry nameapp.ivive/iviveverified in the MCP registry

The registry name sits under ivive.app. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

• Stateanswerschecked 2026-10-28
• Tools6
• Server calls itselfivive
• Server version1.0.2
• Protocol version2025-06-18

On 2026-10-28 the server answered initialize and tools/list without a sign-in. First answer in 522 ms.

• Its tools do every use case we checked: convert microsome clearance into predicted human plasma clearance; set clearance targets for the next compound to make.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

• INITE MCP score100 of 100answers 100 · does the job 100 · definitions 100 · context 100 · connects 100
• What an agent can do with it2 of 2 use cases
• Answered100% of days8 of 8 daily checks
• Median first answer532 ms
• Space in an agent's context≈ 2,507 tokensthe definitions of all its tools (6), which an agent carries on every turn
• Tool definitionsA · 100 of 100
• Typed results0 of 6 toolsdeclared outputSchema: results come typed, read once

• Every tool passes all six checks.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

• predict_inputs

  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.

• calc_clhep

  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.

• target_clint

  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…

• input_sensitivity

  How far plasma CL moves as each input is varied over a range, e.g. a predicted fu,p over its 50% range.

• similar_drugs

  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…

• scale_to_human

  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.