Indexfy
REMOTE · API.INDEXFY.XYZ
Buy and sell fully backed crypto index tokens and trade prediction markets on Base, in USDC.
Available components
Last scanned (16 hours ago)
Scores higher than 52% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Crypto and Web3
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. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability63
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management33
- Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage90
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 69% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 15 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 16 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (12)
- TLS certificate
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation 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.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 19 Nov 26 +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.
- 17 Nov 26 +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.
- 15 Nov 26 +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.
- 13 Nov 26 +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.
- 12 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 11 Nov 26 64
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Probed https://api.indexfy.xyz/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=api.indexfy.xyz | CN=YE1,O=Let's Encrypt,C=US | 23 Sept 2026 | 22 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 56afefb5a72934c870d0c7c3ee383569b0d |
| SANs: api.indexfy.xyz | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.indexfy.xyz. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| xyz. | DS published | 3599, 18130 | 8, 8 | Verified |
| indexfy.xyz. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| content-security-policy | default-src 'self';base-uri 'self';font-src 'self' https: data:;form-action 'self';frame-ancestors 'self';img-src 'self' data:;object-src 'none';script-src 'self';script-src-attr 'none';style-src 'self' https: 'unsafe-inline';upgrade-insecure-requests |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | no-referrer |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.indexfy.xyz/mcp | Verified | 200 | |
| http (plaintext) | http://api.indexfy.xyz/mcp | HTTPS enforced | 308 | https://api.indexfy.xyz/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
build_buy_index Build: buy an index ~110
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.
| Name | Type | Req | Description |
|---|---|---|---|
| index | – | yes | the index's token address |
| usdcAmount | string | yes | USDC to spend at most, as a decimal string, e.g. "25" or "0.5" |
| wallet | string | yes | the agent's wallet address — the one that will sign and send the calls |
No output schema declared.
No examples provided.
build_create_index Build: create an index ~262
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.
| Name | Type | Req | Description |
|---|---|---|---|
| assets | array | yes | – |
| 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 | yes | e.g. "AI Agents Index" |
| proposer | – | – | who may propose rebalances (default: wallet) |
| symbol | string | yes | ticker, 1–12 letters/digits, e.g. "AGENT5" |
| tvlFeePct | number | – | management fee in % per year (max 0.2) |
| wallet | string | yes | the agent's wallet address — the one that will sign and send the calls |
No output schema declared.
No examples provided.
build_create_prediction_market Build: create a prediction market ~246
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.
| Name | Type | Req | Description |
|---|---|---|---|
| closeTime | string | yes | ISO 8601 time trading stops, e.g. 2026-12-31T00:00:00Z |
| liquidityUsdc | string | yes | USDC liquidity to seed (minimum 100), as a decimal string, e.g. "25" or "0.5" |
| question | string | yes | 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 | yes | ISO 8601 earliest time the solver may propose the outcome (≥ closeTime) |
| sector | string | yes | – |
| solver | – | yes | the address that will resolve the market (not the wallet) |
| wallet | string | yes | the agent's wallet address — the one that will sign and send the calls |
No output schema declared.
No examples provided.
build_prediction_account Build: solver stake and balance ~103
Deposit or withdraw solver stake (backs the 1% bonds of your proposals), or withdraw your balance (dispute winnings and returned bonds).
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | – |
| amountUsdc | string | – | USDC, for deposit_stake / withdraw_stake, as a decimal string, e.g. "25" or "0.5" |
| wallet | string | yes | the agent's wallet address — the one that will sign and send the calls |
No output schema declared.
No examples provided.
build_prediction_resolution Build: resolve or settle a prediction market ~121
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).
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | – |
| id | integer | yes | prediction market id |
| outcome | string | – | required for propose |
| wallet | string | yes | the agent's wallet address — the one that will sign and send the calls |
No output schema declared.
No examples provided.
build_prediction_trade Build: trade a prediction market ~148
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.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | – |
| amount | string | yes | USDC to spend (buy) or shares to sell (sell), as a decimal string, e.g. "25" or "0.5" |
| id | integer | yes | prediction market id |
| side | string | yes | – |
| slippageBps | integer | – | max price movement, in basis points (100 = 1%) |
| wallet | string | yes | the agent's wallet address — the one that will sign and send the calls |
No output schema declared.
No examples provided.
build_sell_index Build: sell an index ~103
Sell index shares for USDC: one transaction redeems the shares for the basket and sells each token on KyberSwap, reverting below the quoted minimum.
| Name | Type | Req | Description |
|---|---|---|---|
| index | – | yes | the index's token address |
| shares | string | yes | index shares to sell (18 decimals), as a decimal string, e.g. "25" or "0.5" |
| wallet | string | yes | the agent's wallet address — the one that will sign and send the calls |
No output schema declared.
No examples provided.
get_index Get index ~41
One index's stats, mandate and current holdings (each basket token's amount, USD value and weight).
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | the index's token address |
No output schema declared.
No examples provided.
get_prediction_market Get prediction market ~64
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | prediction market id |
| wallet | string | – | – |
No output schema declared.
No examples provided.
get_wallet_portfolio Get wallet portfolio ~37
A wallet's Indexfy index holdings with value and profit/loss, plus its Indexfy points.
| Name | Type | Req | Description |
|---|---|---|---|
| wallet | string | yes | – |
No output schema declared.
No examples provided.
list_indexes List indexes ~71
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.
| Name | Type | Req | Description |
|---|---|---|---|
| creator | string | – | only indexes launched by this address |
| limit | integer | – | – |
| sort | string | – | – |
No output schema declared.
No examples provided.
list_prediction_markets List prediction markets ~75
Prediction markets on Indexfy with live YES/NO prices (= implied probability), money in the market, phase and deadlines.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| search | string | – | words in the question |
| sector | string | – | – |
| status | string | – | open = still trading; closed = trading ended |
No output schema declared.
No examples provided.
quote_prediction_trade Quote a prediction trade ~95
Exact quote from the market maker: shares for a USDC buy, or USDC for a share sell, fees included.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | – |
| amount | string | yes | USDC to spend (buy) or shares to sell (sell), as a decimal string, e.g. "25" or "0.5" |
| id | integer | yes | prediction market id |
| side | string | yes | – |
No output schema declared.
No examples provided.
register_index Register a created index ~40
Lists a newly created index on indexfy.xyz right away. Call with the deployFolio transaction hash once it's mined.
| Name | Type | Req | Description |
|---|---|---|---|
| txHash | string | yes | – |
No output schema declared.
No examples provided.
register_prediction_market Register a created prediction market ~52
Lists a newly created market on indexfy.xyz under its sector. Call with the createMarket transaction hash once mined, within 1 hour.
| Name | Type | Req | Description |
|---|---|---|---|
| sector | string | yes | – |
| txHash | string | yes | – |
No output schema declared.
No examples provided.
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.
remote · api.indexfy.xyz
claude mcp add --transport http xyz-indexfy-indexfy 'https://api.indexfy.xyz/mcp'
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.