Skip to content

ivive.app MCP server

app.ivive/iviveivive.appstreamable-httpv1.0.3Scanned

Human hepatic clearance from in-vitro CLint, with the error band measured on known drugs.

6 tools: 6 change things.

Tools: 0 delete, 0 irreversible, 6 write, 0 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

6 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the ivive.app MCP server can do

The ivive.app MCP server is published by ivive.app, a domain the MCP Registry verified. It has 6 tools. It can create or change data (6 tools: predict_inputs, calc_clhep, target_clint, input_sensitivity and 2 more), but cannot delete data. None of its tools only reads.

None of its tools reads private data, brings in text other people write, or sends data out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 10, 2026, version 1.0.3.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

6 tools

Changes things 6Claude Code: ask
  • calc_clhepHepatic and plasma clearance from in-vitro CLint, fu,mic and fu,p (IVIVE), with the observed-CL band and applicability warnings.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • input_sensitivityHow far plasma CL moves as each input is varied over a range, e.g.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    How far plasma CL moves as each input is varied over a range, e.g. a predicted fu,p over its 50% range.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • predict_inputsPredict fu,p and fu,inc from a SMILES, with structure-only human CL and Vss as second opinions.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • scale_to_humanPredict human plasma CL from observed animal in-vivo CL (rat, dog, monkey), every applicable method with its measured error.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • similar_drugsNearest reference drugs to a SMILES (Tanimoto, Morgan radius 2), each with measured human plasma CL and the CL IVIVE predicted from its measured inputs.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • target_clintThe 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.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:29 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
6
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 6 tools that change things (6 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://api.ivive.app/mcp/: tools/list returned 6 tools to an anonymous client, including predict_inputs (write), calc_clhep (write), target_clint (write), input_sensitivity (write), similar_drugs (write) and 1 more

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools6 changed.~6 changedView diff

Install

Pinned to version 1.0.3. Values in angle brackets are yours to fill in.

claude mcp add --transport http ivive https://api.ivive.app/mcp/
claude mcp add --transport http ivive https://api.ivive.app/mcp/

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [],
    "ask": [
      "mcp__ivive__predict_inputs",
      "mcp__ivive__calc_clhep",
      "mcp__ivive__target_clint",
      "mcp__ivive__input_sensitivity",
      "mcp__ivive__similar_drugs",
      "mcp__ivive__scale_to_human"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as ivive. Review it before you use it.

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/app.ivive/ivive/verify?hash=61c0d8bcbf760afdb089bd90c1c479692cc84c3ac33c48d10d791e2f2a6a7373" | jq -e '.changed == false'

Pinned hash 61c0d8bcbf76, from Nov 10, 2026, 17:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/app.ivive/ivive/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for app.ivive/ivive
[![Anlyon Radar](https://radar.anlyon.com/badge/app.ivive/ivive.svg)](https://radar.anlyon.com/servers/app.ivive/ivive)

Source: MCP Registry. Synced Oct 29, 2026, 09:17 UTC.

ivive.app MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the ivive.app MCP server safe?

No scan can promise that. What its definitions show: 6 tools, 6 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the ivive.app MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the ivive.app MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the ivive.app MCP server have?

6 tools: 6 write. predict_inputs, calc_clhep, target_clint, input_sensitivity, similar_drugs and scale_to_human.

Does the ivive.app MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the ivive.app MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the ivive.app MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Oct 29, 2026. Every change is on this page and in its Atom feed.