ICE Data Services MCP server icon

ICE Data Services

by ICE Data Services

HIPAA CompliantSOC2 ReadyISO 27001 Ready
Finance6 tools

Query ICE fixed income evaluations, bond trades and reference data from an AI agent. Anthropic lists 6 read-only tools; ICE publishes no tool list. ICE SSO with MFA, and your existing ICE entitlements bound every result.

Verified connector

Listed by Anthropic as a partner connector in its Connectors Directory.

Connection checked by Agentman on .

Anthropic states this reflects the level of review a connector received, not a security audit.

Connect ICE Data Services via MCP

https://fids-mcp.ice.com/mcp

Works in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.

ICE Data Services Tools & Capabilities (6)

Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.

Limits

  • We could not verify the authentication posture, and no one can from outside. The entire fids-mcp.ice.com host sits behind a Cloudflare edge deny. An anonymous initialize, three RFC 9728 and OAuth metadata paths, a nonsense control path and even robots.txt all returned
  • No OAuth scopes could be read, so none can be reported. The resource and authorization metadata documents were unreachable behind the same block. We cannot say whether any scope boundary exists. Since all six listed tools read, there is in any case no irreversible action for a scope to sit in front of — but that conclusion rests on the name census, not on a schema.
  • Three of the six tool names are generic, and the verb census may not describe the surface. ids_compute, ids_get_schema and ids_describe_concept name operations rather than resources. Without a single input schema we cannot rule out that one takes a dataset, method or action as an argument and forwards it to a wider ICE API — the shape that would make a six-name count meaningless. We have no evidence that it does; we simply could not look, and on a licensed-data connector that gap is worth stating rather than glossing.
  • ICE publishes no tool list at all. The six names come from Anthropic's directory. ICE's connector page contains zero tool identifiers. There is no vendor enumeration to diff against.
  • The one third-party listing is not an independent check. PromptArmor publishes the same six names, but its page carries Anthropic's own directory UUID and a directoryUrl field, and its tool descriptions are null — it mirrors the directory rather than probing the server. It corroborates that the directory was transcribed correctly and nothing more.
  • No prompts or resources could be enumerated. Anthropic's directory records no prompt names, and the blocked endpoint meant we never read an initialize capabilities block. We cannot say whether the server declares prompts or resources at all.
  • Your entitlements narrow everything. ICE states access is governed by your existing ICE entitlements, so nothing on this page tells you what *your* account can reach. Two users of the same connector will see different data and possibly different tools.
  • History begins January 2026. ICE states earlier dates return sparse or no results, and that queries over a month may time out. Anything needing a long back-series is out of scope for this channel regardless of what ICE holds elsewhere.
  • ICE disclaims the model's output. ICE states that LLM reasoning and responses vary and that it does not control or take responsibility for third-party LLM outputs. Its AI principles page states human review is mandatory for material decisions. Do not let an agent's narrative be the final artefact in a pricing control.
  • Reuse rules are not knowable from public documents. ICE's three public market-data policies each govern a *different* ICE entity or product — English-law feeds, futures-only derived data, and index-feed non-display use — and none mentions MCP or AI. Your own ICE agreement governs, and an MCP-specific addendum may exist that modifies it. Settle this with ICE client services before storing or redistributing anything the connector returns.
  • The documentation link Anthropic publishes is two redirects from the real page, and ICE's own sitemap points at the wrong one. The directory's documentation URL is an opaque vanity string, ice.com/ieoauoau, which 302s to /claude-mcp-connector, which 302s again to /mcp-connector — the only path serving HTTP 200 directly, and the one the page's own og:url names. ICE's sitemap lists the middle hop rather than the destination. Cite /mcp-connector.

Frequently asked questions

Yes, and there is no self-service path. ICE requires an active ICE Data Services account holding licences to the specific content sets in the MCP server, plus multi-factor authentication enabled on your ICE SSO account. ICE states that access to its data is governed by customers' existing ICE entitlements, so two users of the same connector can see different data.

No. Anthropic's directory records this connector's permissions as Read, and all six listed tool names begin with query, get, describe, classify or compute. No name carries a create, update, delete, send or order verb. This is a retrieval and calculation surface over ICE's data, not a system that writes back to ICE or to any trading venue.

To January 2026, which is much shorter than ICE's underlying history. ICE's own search tips state that data coverage begins January 2026 and that earlier dates return sparse or no results. ICE separately markets 15-plus years of AAA Municipal Bond Curve history, so the connector exposes a recent window rather than the full archive behind it.

Because the date range is too wide. ICE states that queries spanning more than one month may time out, and recommends single-day or weekly ranges for the fastest performance. If you specify no range at all, ICE says the system defaults to the last seven calendar days. Narrowing by asset category or sector also improves query performance.

Assume not without checking your own ICE agreement first. ICE's published market-data terms restrict sublicensing, reselling and redistributing its data, and restrict derived works. None of ICE's public policy documents mentions MCP, AI or large language models, so the terms covering this connector are the ones in your negotiated ICE contract, which we could not read.

ICE lists five: End-of-Day Fixed Income Evaluations, Enhanced Evaluation Transparency, the ICE AAA Municipal Bond Curve, US Treasury Benchmark data, and FINRA TRACE and MSRB RTRS trade data. Anthropic's directory description names only the TRACE and RTRS trades and bond reference data, so the directory understates the content by three datasets.

Anthropic's directory records it as working with Claude and the Claude API only, not Claude Code or Claude Desktop. ICE's own instructions describe connecting through Claude Desktop or Claude.ai settings, which is broader than the directory records. ICE's announcement says the open MCP standard enables future compatibility with additional AI platforms.

By issuer name, and ICE resolves it for you. ICE states the connector maps issuer names to the correct identifiers behind the scenes, so you need not supply a CUSIP or ISIN. You can also search by asset category, sector, maturity range or other bond characteristics, and ICE's own sample prompts use plain ISINs where you have one.

Sources

Use in Agentman

Connect once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.

Open in Agentman Studio

Resources

Server Info

Category
Finance
Developer
ICE Data Services
Tools
6
Domain
fids-mcp.ice.com

Using Claude Desktop or another MCP client? Setup docs — the connection URL above works anywhere.

Similar MCP Servers for Finance

Stripe logo

Stripe

by Stripe

Coming Soon
Finance23 tools
View detailsConnect
PayPal logo

PayPal

by PayPal

Finance28 tools
View detailsConnect
Square logo

Square

by Square, Inc.

Coming Soon
Finance3 tools
View detailsConnect

Related Resources

Browse All MCP ServersClaude & ChatGPT Setup GuideBrowse AI Skills