_ registry / mcp http-sse · checked 1h ago

ixs-vault-mcp

https://api-v2.ixs.finance

Registry code: 079038b52890ea22

api record

Pay-per-call API exposing IXS tokenized real world asset vaults: vault listings with their underlying asset and on-chain details, returned as JSON. bash.001 per request in USDC on Base.

from a public catalogue that lists it, not from the operator

endpoint
https://api-v2.ixs.finance/mcp
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is ixs-vault-mcp live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is ixs-vault-mcp free to use?
Yes — the hub reached it with no key and no payment.
What tools does ixs-vault-mcp have?
8 tools: vault_build_request_deposit, vault_build_claim_deposit, vault_build_claim_redeem, vault_build_request_redeem, vault_request_status, vault_check_whitelist, vault_get, vaults_list.
Is ixs-vault-mcp safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
1,914ms

last good check

priced tools
0

of 8 tools

_ answered our checks, 90 days 217 checks · signed record
_ what it is for
topic
crypto & onchain trading & defi
used for
  • list tokenized real-world asset vaults
  • build vault deposit and redeem transactions
  • check vault whitelist status
takes → gives
data → data
tools
8 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts, and USDC settlements on base into the address this listing's priced doors name, read off the chain. Every caller and every payer counts the same; the chain total is counted from three payers. The address also stands behind 1 other origin: the chain figures are the gateway's, not this listing's alone. How it is counted.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

payers on base
38

distinct

settlements
59

last 2026-11-07

received on chain
0.059 USDC

shared-payto

_ what it can do 8 tools
1 open 7 never probed 1 of 8 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • vaults_list reads open 20h ago

    List IXS vaults available for agent discovery.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • vault_build_request_deposit reads unknown never probed

    Build approve + deposit transaction payloads for a supported IXS vault without sending transactions.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "vaultId",
    "ownerAddress",
    "assetAmount"
  ],
  "properties": {
    "vaultId": {
      "type": "string",
      "minLength": 1
    },
    "assetAmount": {
      "type": "string",
      "minLength": 1
    },
    "ownerAddress": {
      "type": "string",
      "minLength": 1
    }
  }
}
    arguments 23 lines
  • vault_build_claim_deposit reads unknown never probed

    For ERC-7540 vaults only: build the transaction that claims shares for a deposit request that has become claimable. Errors on sync vaults, which have no claim step.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "vaultId",
    "ownerAddress",
    "requestId"
  ],
  "properties": {
    "vaultId": {
      "type": "string",
      "minLength": 1
    },
    "requestId": {
      "type": "string",
      "minLength": 1
    },
    "ownerAddress": {
      "type": "string",
      "minLength": 1
    }
  }
}
    arguments 23 lines
  • vault_build_claim_redeem reads unknown never probed

    For ERC-7540 vaults only: build the transaction that claims assets for a redeem request that has become claimable. Errors on sync vaults, which have no claim step.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "vaultId",
    "ownerAddress",
    "requestId"
  ],
  "properties": {
    "vaultId": {
      "type": "string",
      "minLength": 1
    },
    "requestId": {
      "type": "string",
      "minLength": 1
    },
    "ownerAddress": {
      "type": "string",
      "minLength": 1
    }
  }
}
    arguments 23 lines
  • vault_build_request_redeem reads unknown 20h ago

    Build redeem transaction payloads for a supported IXS vault without sending transactions.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "vaultId",
    "ownerAddress",
    "shareAmount"
  ],
  "properties": {
    "vaultId": {
      "type": "string",
      "minLength": 1
    },
    "shareAmount": {
      "type": "string",
      "minLength": 1
    },
    "ownerAddress": {
      "type": "string",
      "minLength": 1
    }
  }
}
    arguments 23 lines
  • vault_request_status reads unknown 16h ago

    List a wallet's recent deposit and redeem requests (requestId, status, amounts) from the vault subgraph — use this to know when a queued request becomes claimable.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "ownerAddress"
  ],
  "properties": {
    "vaultId": {
      "type": "string"
    },
    "ownerAddress": {
      "type": "string",
      "minLength": 1
    }
  }
}
    arguments 16 lines
  • vault_check_whitelist reads unknown 20h ago

    Check whether a wallet is whitelisted for a vault before attempting a deposit — call this ahead of vault_build_request_deposit to avoid a reverted transaction.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "vaultId",
    "walletAddress"
  ],
  "properties": {
    "vaultId": {
      "type": "string",
      "minLength": 1
    },
    "walletAddress": {
      "type": "string",
      "minLength": 1
    }
  }
}
    arguments 18 lines
  • vault_get reads unknown 16h ago

    Get metadata and settlement kind (sync vs ERC-7540 async) for a single IXS vault.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "vaultId"
  ],
  "properties": {
    "vaultId": {
      "type": "string",
      "minLength": 1
    }
  }
}
    arguments 13 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 079038b52890ea22.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/079038b52890ea22/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/079038b52890ea22/badge.svg)](https://brick.blue/agent/079038b52890ea22?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.