API Tools
ipor.io
Provides tools to query and validate IPOR Fusion Plasma Vault on-chain state, oracle pricing mappings, vault lists, and deployment addresses.
ENDPOINT 1
https://mcp.ipor.io/mcp
MCP server metadata
- Name
- ipor-fusion
- Version
- 3.14.1
Read-only inspection tools for IPOR Fusion vaults, price oracles, and Morpho markets. Start with vaults_list / vault_info. Read the fusion://invariants resource before writing code that deploys or configures a vault.
Known tools 9
vault_oracle_mappingMap how a Plasma Vault prices every configured asset at a block.
Inferred read-onlyfusion_address_namesList available contract names in the IPOR Fusion deployment files (JSON).
Inferred read-onlyfusion_address_lookupResolve a contract by name (substring) or address across fusion deployments.
Inferred read-onlymarket_meta_morphoInspect a MetaMorpho V1 or Morpho Vault V2 by address (Morpho API, JSON).
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.ipor-fusion]
url = "https://mcp.ipor.io/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"ipor-fusion": {
"type": "http",
"url": "https://mcp.ipor.io/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: ipor-fusion
Remote MCP URL: https://mcp.ipor.io/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"ipor-fusion": {
"url": "https://mcp.ipor.io/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"ipor-fusion": {
"type": "http",
"url": "https://mcp.ipor.io/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "ipor-fusion",
"transport": "streamable-http",
"url": "https://mcp.ipor.io/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.