# Indexfy (remote · api.indexfy.xyz)

Buy and sell fully backed crypto index tokens and trade prediction markets on Base, in USDC.

- Trust score: 68/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `api.indexfy.xyz`: 68/100 (this document), [markdown](https://verifymcp.io/servers/xyz-indexfy-indexfy/api.md), [page](https://verifymcp.io/servers/xyz-indexfy-indexfy/api)

## Channel facts

- Endpoint: `https://api.indexfy.xyz/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 2 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 63/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1834 tokens (~122/item across 15 items; 15 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 33/100
  - Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 90/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 69% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 15 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 16 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Indexfy MCP server?

Indexfy is a hosted endpoint at https://api.indexfy.xyz/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http xyz-indexfy-indexfy 'https://api.indexfy.xyz/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "xyz-indexfy-indexfy": {
      "url": "https://api.indexfy.xyz/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "xyz-indexfy-indexfy": {
      "type": "http",
      "url": "https://api.indexfy.xyz/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.xyz-indexfy-indexfy]
url = "https://api.indexfy.xyz/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "xyz-indexfy-indexfy": {
      "type": "remote",
      "url": "https://api.indexfy.xyz/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add xyz-indexfy-indexfy --url 'https://api.indexfy.xyz/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  xyz-indexfy-indexfy:
    url: "https://api.indexfy.xyz/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "xyz-indexfy-indexfy": {
      "Transport": "http",
      "Url": "https://api.indexfy.xyz/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add xyz-indexfy-indexfy -t streamable-http -u 'https://api.indexfy.xyz/mcp'
```

### Other

```json
{
  "mcpServers": {
    "xyz-indexfy-indexfy": {
      "type": "http",
      "url": "https://api.indexfy.xyz/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-19 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-17 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-15 (score 66, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-13 (score 65, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-12 (score 64, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-11 (score 64)

First indexed and scored.

## MCP tools (15)

### `list_indexes` (~71 tokens)

List indexes

Indexfy index funds on Base with price, TVL and 24h / 7d performance. Each index is an ERC-20 fully backed by its basket of tokens.

Input parameters:

- `creator` (string): only indexes launched by this address
- `limit` (integer)
- `sort` (string)

### `get_index` (~41 tokens)

Get index

One index's stats, mandate and current holdings (each basket token's amount, USD value and weight).

Input parameters:

- `address` (string, required): the index's token address

### `get_wallet_portfolio` (~37 tokens)

Get wallet portfolio

A wallet's Indexfy index holdings with value and profit/loss, plus its Indexfy points.

Input parameters:

- `wallet` (string, required)

### `build_create_index` (~262 tokens)

Build: create an index

Launch a new index fund: the wallet seeds it with the exact amount of each basket token (it must hold them) and receives `initialShares` shares. The seed amounts set the weights. Returns the approvals and the factory deployment call, plus the new index's predicted address.

Input parameters:

- `assets` (array, required)
- `auctionMinutes` (integer): rebalance auction length
- `feeRecipient`: who receives the fees (default: wallet)
- `initialShares` (string): shares minted for the seed, as a decimal string, e.g. "25" or "0.5"
- `mandate` (string): the index's investment mandate, shown to buyers
- `mintFeePct` (number): fee on each mint, in % (max 0.5)
- `name` (string, required): e.g. "AI Agents Index"
- `proposer`: who may propose rebalances (default: wallet)
- `symbol` (string, required): ticker, 1–12 letters/digits, e.g. "AGENT5"
- `tvlFeePct` (number): management fee in % per year (max 0.2)
- `wallet` (string, required): the agent's wallet address — the one that will sign and send the calls

### `register_index` (~40 tokens)

Register a created index

Lists a newly created index on indexfy.xyz right away. Call with the deployFolio transaction hash once it's mined.

Input parameters:

- `txHash` (string, required)

### `build_buy_index` (~110 tokens)

Build: buy an index

Buy an index with USDC alone: one transaction buys every basket token on KyberSwap and mints the shares, reverting below the quoted minimum. Unspent USDC is refunded.

Input parameters:

- `index` (required): the index's token address
- `usdcAmount` (string, required): USDC to spend at most, as a decimal string, e.g. "25" or "0.5"
- `wallet` (string, required): the agent's wallet address — the one that will sign and send the calls

### `build_sell_index` (~103 tokens)

Build: sell an index

Sell index shares for USDC: one transaction redeems the shares for the basket and sells each token on KyberSwap, reverting below the quoted minimum.

Input parameters:

- `index` (required): the index's token address
- `shares` (string, required): index shares to sell (18 decimals), as a decimal string, e.g. "25" or "0.5"
- `wallet` (string, required): the agent's wallet address — the one that will sign and send the calls

### `list_prediction_markets` (~75 tokens)

List prediction markets

Prediction markets on Indexfy with live YES/NO prices (= implied probability), money in the market, phase and deadlines.

Input parameters:

- `limit` (integer)
- `search` (string): words in the question
- `sector` (string)
- `status` (string): open = still trading; closed = trading ended

### `get_prediction_market` (~64 tokens)

Get prediction market

One market's live state: prices, phase and what can be done next, deadlines, proposal/dispute. With `wallet`, also its shares, redeemable USDC and solver stake.

Input parameters:

- `id` (integer, required): prediction market id
- `wallet` (string)

### `quote_prediction_trade` (~95 tokens)

Quote a prediction trade

Exact quote from the market maker: shares for a USDC buy, or USDC for a share sell, fees included.

Input parameters:

- `action` (string, required)
- `amount` (string, required): USDC to spend (buy) or shares to sell (sell), as a decimal string, e.g. "25" or "0.5"
- `id` (integer, required): prediction market id
- `side` (string, required)

### `build_prediction_trade` (~148 tokens)

Build: trade a prediction market

Buy YES/NO shares with USDC, or sell shares back for USDC before the market closes. Includes the USDC approval when needed and a minimum-output guard.

Input parameters:

- `action` (string, required)
- `amount` (string, required): USDC to spend (buy) or shares to sell (sell), as a decimal string, e.g. "25" or "0.5"
- `id` (integer, required): prediction market id
- `side` (string, required)
- `slippageBps` (integer): max price movement, in basis points (100 = 1%)
- `wallet` (string, required): the agent's wallet address — the one that will sign and send the calls

### `build_create_prediction_market` (~246 tokens)

Build: create a prediction market

Open a YES/NO market. The wallet seeds it with USDC liquidity (minimum 100) and names a solver — a different address that alone resolves it and stakes 1% as a bond. Trading runs until closeTime; the solver proposes after resolveAfter.

Input parameters:

- `closeTime` (string, required): ISO 8601 time trading stops, e.g. 2026-12-31T00:00:00Z
- `liquidityUsdc` (string, required): USDC liquidity to seed (minimum 100), as a decimal string, e.g. "25" or "0.5"
- `question` (string, required): a clear YES/NO question with its resolution source and time, e.g. "Will BTC close above $100,000 on Coinbase on Dec 31, 2026 (UTC)?"
- `resolveAfter` (string, required): ISO 8601 earliest time the solver may propose the outcome (≥ closeTime)
- `sector` (string, required)
- `solver` (required): the address that will resolve the market (not the wallet)
- `wallet` (string, required): the agent's wallet address — the one that will sign and send the calls

### `register_prediction_market` (~52 tokens)

Register a created prediction market

Lists a newly created market on indexfy.xyz under its sector. Call with the createMarket transaction hash once mined, within 1 hour.

Input parameters:

- `sector` (string, required)
- `txHash` (string, required)

### `build_prediction_resolution` (~121 tokens)

Build: resolve or settle a prediction market

After trading: propose (the solver; deposits any missing stake first), dispute (anyone but the solver, posting the same bond, during the 24h window), finalize (anyone, once the window passes), redeem (holders, after settlement) or withdraw_liquidity (the creator, after settlement).

Input parameters:

- `action` (string, required)
- `id` (integer, required): prediction market id
- `outcome` (string): required for propose
- `wallet` (string, required): the agent's wallet address — the one that will sign and send the calls

### `build_prediction_account` (~103 tokens)

Build: solver stake and balance

Deposit or withdraw solver stake (backs the 1% bonds of your proposals), or withdraw your balance (dispute winnings and returned bonds).

Input parameters:

- `action` (string, required)
- `amountUsdc` (string): USDC, for deposit_stake / withdraw_stake, as a decimal string, e.g. "25" or "0.5"
- `wallet` (string, required): the agent's wallet address — the one that will sign and send the calls

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/xyz-indexfy-indexfy/api#diagnostics

## Score history

- 2026-11-21: 68
- 2026-11-20: 68
- 2026-11-19: 68
- 2026-11-18: 67
- 2026-11-17: 67
- 2026-11-16: 66
- 2026-11-15: 66
- 2026-11-14: 65
- 2026-11-13: 65
- 2026-11-12: 64
- 2026-11-11: 64

## Common questions

### What is the Indexfy MCP server?

Indexfy is an MCP server listed in the public MCP registry as xyz.indexfy/indexfy. Buy and sell fully backed crypto index tokens and trade prediction markets on Base, in USDC. This page covers its hosted endpoint (https://api.indexfy.xyz/mcp).

### Is the Indexfy MCP server safe to use?

Indexfy scores 68 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Indexfy MCP server expose?

Indexfy exposes 15 tools: list_indexes, get_index, get_wallet_portfolio, build_create_index, register_index, and 10 more. Their descriptions and schemas cost roughly 1,568 tokens of context every time the server is loaded.

### Does the Indexfy MCP server require authentication?

No. We connected to Indexfy without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Indexfy MCP server still maintained?

Indexfy is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the Indexfy MCP server?

VerifyMCP ran 12 checks on Indexfy, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Indexfy: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://api.indexfy.xyz/mcp
- Website: https://indexfy.xyz/docs
- Changelog RSS feed: https://verifymcp.io/servers/xyz-indexfy-indexfy/api.xml
- Changelog JSON feed: https://verifymcp.io/servers/xyz-indexfy-indexfy/api/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/xyz-indexfy-indexfy/api.json
- HTML version of this page: https://verifymcp.io/servers/xyz-indexfy-indexfy/api
