ETFIQ
REMOTE · MCP.ETFIQ.COM · SCANNED SEP 29
Independent US ETF data: holdings, fees, overlap, returns, each with its source and date.
Available components
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
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 Usability74
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1097 tokens (~84/item across 13 items; 13 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management30
- Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 13 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 14 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the ETFIQ MCP server?
ETFIQ is a hosted endpoint at https://mcp.etfiq.com/, 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 · mcp.etfiq.com
claude mcp add --transport http com-etfiq-etfiq 'https://mcp.etfiq.com/'
{
"mcpServers": {
"com-etfiq-etfiq": {
"url": "https://mcp.etfiq.com/"
}
}
} {
"servers": {
"com-etfiq-etfiq": {
"type": "http",
"url": "https://mcp.etfiq.com/"
}
}
} [mcp_servers.com-etfiq-etfiq] url = "https://mcp.etfiq.com/"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-etfiq-etfiq": {
"type": "remote",
"url": "https://mcp.etfiq.com/",
"enabled": true
}
}
} openclaw mcp add com-etfiq-etfiq --url 'https://mcp.etfiq.com/' --transport streamable-http
mcp_servers:
com-etfiq-etfiq:
url: "https://mcp.etfiq.com/" {
"McpServers": {
"com-etfiq-etfiq": {
"Transport": "http",
"Url": "https://mcp.etfiq.com/"
}
}
} assistant mcp add com-etfiq-etfiq -t streamable-http -u 'https://mcp.etfiq.com/'
{
"mcpServers": {
"com-etfiq-etfiq": {
"type": "http",
"url": "https://mcp.etfiq.com/"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 23 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Sept 26 +7
- Authorization: unverified → partial ▲ security
- 21 Sept 26 0
- Schema quality: 982 → 1097 ▼ functional
- Stability: unverified → 0.03 ▲ functional
- New tool “etf_holders” functional
- 20 Sept 26 56
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 29 Sept 2026 · Probed https://mcp.etfiq.com
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=etfiq.com | CN=WE1,O=Google Trust Services,C=US | 20 Sept 2026 | 19 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | c430baa6feae1a9f131c1a2341c6d80b |
| SANs: etfiq.com, mcp.etfiq.com, *.mcp.etfiq.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.etfiq.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| etfiq.com. | absent | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.etfiq.com | Verified | 200 | |
| http (plaintext) | http://mcp.etfiq.com | Served over HTTP | 200 |
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 →
etf_holders ~115
Which US listed ETFs hold a given company, ranked by how much of each fund it is. USE THIS for any "which ETFs hold X", "which fund holds the most X", or "how do I get exposure to X" question, where X is a company rather than a fund. Takes a company name or its ticker. Returns every holder with the weight its issuer published and the date that book was filed. Covers 31,019 companies.
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | yes | – |
| limit | integer | – | – |
No output schema declared.
No examples provided.
etf_holdings ~70
What a fund holds, by weight, and how old that is. ALWAYS read lag_days before presenting it: an issuer file read today and a filing from two months ago both come back here and are not the same answer.
| Name | Type | Req | Description |
|---|---|---|---|
| ticker | string | yes | – |
| top_n | integer | – | – |
No output schema declared.
No examples provided.
etf_overlap ~83
How much of their weight two funds hold in common, as ETFIQ published it on the comparison page for that pair. Use when asked whether two ETFs are the same thing, or whether owning both adds anything. Refuses rather than estimating when the pair is not compared or either holdings book is incomplete.
| Name | Type | Req | Description |
|---|---|---|---|
| a | string | yes | – |
| b | string | yes | – |
No output schema declared.
No examples provided.
etf_profile ~55
Everything ETFIQ publishes about one fund: issuer, desk, and each figure with its source and as-of date, plus a one sentence verdict on how it did against what its own label promises.
| Name | Type | Req | Description |
|---|---|---|---|
| ticker | string | yes | – |
No output schema declared.
No examples provided.
etf_rankings ~79
The ranked lists ETFIQ publishes, or one of them. Each ranks ONE published figure inside a stated set: the cheapest funds in a theme, the leveraged funds furthest from their stated multiple, the buffer funds closest to their cap. Call with no argument for the list.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| slug | string | – | – |
No output schema declared.
No examples provided.
etf_screen ~120
Every fund matching some filters, largest first, each with its net assets and the source and date that figure came from. Use for "find me all X" questions rather than repeated searches. Fees are percentages, not basis points. Funds with no published size are set aside from a size filter and counted in no_size_figure rather than treated as small.
| Name | Type | Req | Description |
|---|---|---|---|
| desk | string | – | – |
| issuer | string | – | – |
| limit | integer | – | – |
| max_fee_pct | number | – | – |
| min_assets_usd | number | – | – |
No output schema declared.
No examples provided.
etf_search ~77
Find US listed ETFs by ticker, fund name, or a word from the name. Use this FIRST when the user names a fund loosely, then etf_profile with the ticker it returns. Refuses rather than returning a near match.
| Name | Type | Req | Description |
|---|---|---|---|
| desk | string | – | – |
| limit | integer | – | – |
| query | string | yes | – |
No output schema declared.
No examples provided.
etf_theme ~82
Every US listed fund in a theme, largest first, with what each charges and how much of it is already in the S&P 500. USE THIS for any "what X ETFs are there" or "top X ETFs" question: it returns the whole published set rather than a sample.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| theme | string | yes | – |
No output schema declared.
No examples provided.
etf_themes ~36
Every theme ETFIQ publishes and how many funds each holds. Call when unsure what a theme is called, then etf_theme.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
etfiq_as_of ~92
What ETFIQ published on a given date, from its frozen dated archive. Use when a question is about a past date, or when a figure needs to stay true after it is quoted: every other tool here answers about today and today moves overnight. Takes YYYY-MM-DD. Covers the pieces written that night, not an arbitrary per-fund figure on an arbitrary day.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | yes | – |
No output schema declared.
No examples provided.
etfiq_list ~82
The pages inside one section, optionally filtered to those whose address contains a word. Use after etfiq_sections to find a page, then etfiq_page to read it. The count returned is the whole matching set even when the list is capped.
| Name | Type | Req | Description |
|---|---|---|---|
| contains | string | – | – |
| limit | integer | – | – |
| section | string | yes | – |
No output schema declared.
No examples provided.
etfiq_page ~97
Read ANY published ETFIQ page as text: a theme hub, a ranking, a comparison of two funds, an issuer, a methodology note, a dated study. Takes a path like /themes/cyber or a full etfiq.com URL. This reaches all 40,000 pages, including everything the typed tools above do not cover, and returns the page content rather than its navigation.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | – |
No output schema declared.
No examples provided.
etfiq_sections ~47
What ETFIQ publishes, section by section, with a page count for each. Start here when the question is not about one fund: it names every section and what is in it.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the ETFIQ MCP server?
ETFIQ is an MCP server listed in the public MCP registry as com.etfiq/etfiq. Independent US ETF data: holdings, fees, overlap, returns, each with its source and date. This page covers its hosted endpoint (https://mcp.etfiq.com).
Is the ETFIQ MCP server safe to use?
ETFIQ scores 66 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 ETFIQ MCP server expose?
ETFIQ exposes 13 tools: etf_search, etf_profile, etf_holdings, etf_theme, etf_themes, and 8 more. Their descriptions and schemas cost roughly 1,035 tokens of context every time the server is loaded.
Does the ETFIQ MCP server require authentication?
No. We connected to ETFIQ without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the ETFIQ MCP server still maintained?
ETFIQ is still listed as active in the MCP registry. We last reached this channel on 29 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.