ivive.app MCP

An official MCP server provided by ivive.app that allows AI agents to perform in-vitro-in-vivo extrapolation (IVIVE) calculations for human hepatic clearance. It computes plasma clearance, extraction ratios, and prediction error bands based on in-vitro data (CLint, fu,mic, fu,p) or SMILES structures, supporting species scaling and target clearance analysis without requiring an API key for single compounds.

Endpoint and access

No sign-in: your client connects and lists tools immediately, with no account or key.

No sign-inEndpoint checked 2026-10-18Operated by ivive.app

MCP endpoint (Streamable HTTP)

https://api.ivive.app/mcp/

Vendor documentation

What you can do with it

Calculate human hepatic clearance from in-vitro CLint and unbound fractions
Predict plasma clearance and extraction ratio with calibrated error bands
Scale clearance data from animal species to humans
Determine required CLint to achieve a target clearance level

Tools advertised by the last live check:

predict_inputs
calc_clhep
target_clint
input_sensitivity
similar_drugs
scale_to_human

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers a Streamable HTTP server. Use --scope project to write .mcp.json for the repo.

Claude Code configuration

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

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).

Codex configuration

codex mcp add ivive-app-mcp --url https://api.ivive.app/mcp/

Cursor

Merge this server into .cursor/mcp.json in your project, then enable ivive-app-mcp in your MCP settings.

Cursor configuration

{
  "mcpServers": {
    "ivive-app-mcp": {
      "url": "https://api.ivive.app/mcp/"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure). The type must be streamableHttp for a remote HTTP server.

Cline configuration

{
  "mcpServers": {
    "ivive-app-mcp": {
      "type": "streamableHttp",
      "url": "https://api.ivive.app/mcp/",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start ivive-app-mcp and inspect its tools.

VS Code configuration

{
  "servers": {
    "ivive-app-mcp": {
      "type": "http",
      "url": "https://api.ivive.app/mcp/"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.

Gemini CLI configuration

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

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.

Claude Desktop configuration

{
  "mcpServers": {
    "ivive-app-mcp": {
      "url": "https://api.ivive.app/mcp/"
    }
  }
}

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.

Windsurf configuration

{
  "mcpServers": {
    "ivive-app-mcp": {
      "serverUrl": "https://api.ivive.app/mcp/"
    }
  }
}

See all 1,015

Do you run ivive.app MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing