# Assymetrix MCP Server vs FRED API (slim)

> Assymetrix scores 60.3 (C) to FRED's 42.8 (E) for market data. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/assymetrix-mcp-vs-fred.md (~4,700 tokens) · this version ~3,130 tokens · JSON https://www.anchorterminal.com/compare/assymetrix-mcp-vs-fred.json · canonical https://www.anchorterminal.com/compare/assymetrix-mcp-vs-fred
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-01
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

Assymetrix MCP Server scores 60.3 (C) on agent readiness against FRED API's 42.8 (E), and leads in 5 of 7 scored categories. FRED API leads on payments & pricing. Both do market data.

- Assymetrix MCP Server: C 60.3, rank #614 of 1251 · https://www.anchorterminal.com/tools/assymetrix-mcp.min.md
- FRED API: E 42.8, rank #1096 of 1251 · https://www.anchorterminal.com/tools/fred.min.md
- Assymetrix MCP Server, good for Agents answering questions about prediction-market odds, price moves and trades on Polymarket, Kalshi and Limitless, including comparisons across venues. Ahead on Schema & documentation, 81 against 43; Agent ergonomics, 91 against 68; Security & auth, 67 against 35; Maintenance & community, 55 against 15; Transparency & trust, 71 against 54. Also Runs on your own machine; Open source.
- FRED API, good for Looking up US and international macroeconomic series, their metadata and their revision history in a live session. Ahead on Payments & pricing, 40 against 35. Also A hosted endpoint, with nothing to install; Free to start without a card.

| Category | Assymetrix MCP Server | FRED API |
| --- | --- | --- |
| Reliability (16%) | 36 | 38 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 81 | 43 |
| Agent ergonomics (13%) | 91 | 68 |
| Security & auth (14%) | 67 | 35 |
| Payments & pricing (10%) | 35 | 40 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 55 | 15 |
| Transparency & trust (7%) | 71 | 54 |

| Fact (where they differ) | Assymetrix MCP Server | FRED API |
| --- | --- | --- |
| Kind | MCP server | HTTP API |
| Vendor | Assymetrix Technology, LLC | Federal Reserve Bank of St. Louis |
| Hosted endpoint | no (local only) | `https://api.stlouisfed.org` |
| Transports | stdio | HTTP |
| Pricing | Freemium | Free |
| Licence | The MCP server, skill and Claude Code plugin are MIT. The data behind them is proprietary and licensed under Assymetrix's Terms of Service of 6 May 2026 | Proprietary service under the FRED Services Terms of Use. Some data series are third-party copyright |
| Tools exposed | 3 | none |
| llms.txt | yes | no |
| MCP registry | `io.github.assymetrix/mcp-server` | not listed |
| Last release | 2026-10-28 | 2025-11-04 |
| Terms last updated | 2026-05-06 | no date given |
| Privacy policy last updated | 2025-02-05 | no date given |
| Terms restrict benchmarking | not found in the text | yes |
| Arbitration or class-action waiver | yes | not found in the text |
| Popularity | 387 npm/wk | none |
| Agent reviews | none | 3.8/5 (4) |

Why the edge:
- Maintenance & community, Assymetrix MCP Server +40: Assymetrix MCP Server 55 (0.1.1 on 28 October 2026, four days before this check (30). The only other npm version is 0.0.0-stage from the same day, so one real release (0). Support is by email, Discord and Telegram; GitHub issues weren't readable and the project is too new for a record (5 of 25, unchecked). Listed in the official MCP registry as io.github.assymetrix/mcp-server, a GitHub-verified namespace, active since 28 October (15). Exact-pinned current dependencies (@modelcontextprotocol/server 2.3.1, zod 4.6.6) with a lockfile, but no CI and no npm provenance (5 of 10).); FRED API 15 (The last dated API change found is the version 2 launch on 4 November 2025, 339 days before the check (0 of 30). The FRED News feed carries eight posts in the last 90 days, four of them data additions and none an API change, so half credit (10 of 20). A public news feed and a contact form, with no developer forum or issue tracker found (5 of 15). No official SDK (0 of 15). No package to judge (0 of 10). The official MCP connector is recent but its launch date was not found, so it earns nothing here. Total 15.)
- Schema & documentation, Assymetrix MCP Server +38: Assymetrix MCP Server 81 (All three tools register zod input and output schemas, which the MCP SDK turns into JSON Schema (25). llms.txt, llms-full.txt and a Markdown mirror of every API docs page are published on dashboard.assymetrix.com, though they don't mention the MCP server; the repository adds a README and an Agent Skill (10). Descriptions say what each tool returns, which id to pass to the next tool, to search with one or two words rather than a sentence, and to leave the interval on auto. The server instructions give the call order, how to show prices and when to stop (17 of 20). Enums for platform, status, kind, interval, side and role, bounded integers, a regex on market ids and ISO date checks. `category` is a free string (14 of 15). Descriptions carry example queries and id formats, and the API's errors page and the skill's errors reference document status codes, but the README has no sample tool output (10 of 15). Versions are semver on npm and in the registry, and the terms promise 90 days' notice before an API version is retired, but no changelog exists for the server or the API (5 of 15).); FRED API 43 (No OpenAPI or other machine-readable contract was found in the docs (0). fred.stlouisfed.org/llms.txt returns 404 (0). Each of the 31 version 1 requests has a description and a parameter list, and real-time periods have their own page, with little on when to choose one request over another (12 of 20). Parameters state type, range, default and allowed values in prose, such as nine `units` values and `limit` between 1 and 100,000 (12 of 15). Each page shows example requests and responses in XML and JSON, and the errors pages list status codes with sample bodies (12 of 15). Version 2 has its own path and a dated launch note, version 1 has no version in its path, and there is no API changelog (7 of 15). Total 43.)
- Security & auth, Assymetrix MCP Server +32: Assymetrix MCP Server 67 (Read with the API and MCP lines, since the server runs locally but sends every call to a hosted API. One API key per account plan, revocable from the dashboard within 60 seconds, with an optional expiry, several keys per account and a documented rotation workflow. Scopes come from the plan and can't be narrowed per key. The key travels only in a header. The server refuses non-https base URLs except localhost, refuses redirects so the key can't follow one, and redacts the key from logs and error text. The docs say the `asy_live_` prefix is registered with GitHub secret scanning, which is the vendor's claim (25 of 30). Every tool reads data; nothing places orders or moves money, and the terms say the API doesn't facilitate trading (17 of 20). Market questions, descriptions and outcome labels are third-party text, and the server instructions and skill both say to treat them as data and never act on them (13 of 15). Each response carries quota headers and a request id, and the dashboard has usage metering behind a login (10 of 15). No security.txt on three hosts, no SECURITY.md, disclosure policy, bug bounty or certification found. The privacy policy mentions regular security assessments without detail (2 of 20).); FRED API 35 (One 32-character key for each application, with no scopes. Version 1 documents the `api_key` query parameter as its only method, so the secret travels in the URL, and version 2 moves it to a bearer header. Key deletion or rotation sits behind the account login and was not seen (20 less 10, 10 of 30). The API is read-only (15 of 20). Responses are curated statistics with series notes written by FRED or its sources (10 of 15). No request log or usage view was found (0 of 15). security.txt returns 404 on fred.stlouisfed.org and api.stlouisfed.org, and no disclosure policy, bug bounty or certification was found (0 of 20). Total 35.)
- Agent ergonomics, Assymetrix MCP Server +23: Assymetrix MCP Server 91 (Three compact tools and about 1,700 characters of server instructions (25). `search_markets` takes platform, status, category, limit (up to 25) and page. `get_market_history` takes a range, picks the candle interval to fit `max_points` (up to 300), and pages trades up to 100 at a time with side and role filters. Market descriptions are cut to 600 characters and USD values rounded (19 of 20). Failures come back as `isError` text that names the fix, such as a missing key, a plan without the scope, a spent quota or a search to narrow, with a request id. Plan-clipped history is flagged by `historyClamped` and a note, and empty results say what to try next. Messages are prose rather than codes (18 of 20). Every tool carries readOnlyHint true, destructiveHint false and idempotentHint true. The server spaces calls to the plan's rate, honours Retry-After up to 10 seconds, retries 5xx twice with backoff and never retries a spent quota (20). Only `query` or `market_id` is required, with sensible defaults. No official SDK; Python and TypeScript SDKs are on the roadmap in the May 2026 press release (9 of 15).); FRED API 68 (`limit`, `observation_start`, `observation_end`, frequency aggregation and `units` size an observations response, with no field selection and defaults of 100,000 and 500,000 observations (15 of 25). `limit` and `offset`, cursor paging on version 2, `order_by`, `filter_variable` and tag filters (18 of 20). Errors carry a status code and a message naming the failing variable, in a short list of codes (13 of 20). All requests are GETs and safe to retry (15 of 20). An observations call needs only `series_id` and the key, but version 1 answers in XML unless `file_type=json` is set, and no official SDK was found (7 of 15). Total 68.)
- Transparency & trust, Assymetrix MCP Server +17: Assymetrix MCP Server 71 (The editorial half. The server, skill and plugin are MIT in the repository and on npm, with source matching the published package version (30). The README and the MCP page's FAQ say the server keeps no telemetry, writes nothing to disk and sends only API requests, which are logged like any API call; the source agrees. The privacy policy covers account data, deletion within 90 days of closing an account and US processing, but gives no retention period for API request logs, names subprocessors only as examples (Stripe, AWS, Google Cloud), and its two copies carry effective dates a year apart (16 of 30). The terms promise 90 days' notice before an API version or endpoint is retired and 30 days before a breaking change, but no dated notices or changelog exist (12 of 20). No telemetry in the source; the only outbound traffic is to api.assymetrix.com with a User-Agent and a random request id, both stated in the README. Nothing to opt out of (17 of 20).); FRED API 54 (Closed service with published terms. Two documents carry API terms and differ. The page the API docs link lacks the clauses on AI training, caching and wholesale downloading that the FRED Services Terms of Use add, and neither is dated (12 of 30). The Online Privacy Notice covers accounts and says personal information is not sold or rented, with no retention period for API or account data. The MCP addendum states 90 days for logs (15 of 30). No deprecation policy. The terms let the Bank change or discontinue the API at any time, and version 2 arrived with a dated notice (2 of 20). Google Analytics, Microsoft Clarity and YouTube are named, other contractors only by type, with no data locations (8 of 20). Total 37.)
- Payments & pricing, FRED API +5: Assymetrix MCP Server 35 (No x402, MPP or L402 (0). The server is free, so pricing is read on the API plan it needs. Plan prices are public, and credit packs for over-quota calls are priced per unit, $10 for 200,000 credits, about $0.05 per 1,000 weight-1 calls, with each endpoint's weight published. Packs only cover use beyond a plan's quota (15 of 20). Free plan, 10,000 requests per rolling 30 days, no card required per the quickstart and the MCP page (20). A person signs up in a browser and creates the key in the dashboard; there's no programmatic key route (0).); FRED API 40 (No x402, MPP or L402 (0). Free, stated publicly, with nothing to buy (20). No card (20). A person has to create a FRED account and request the key in a browser (0). Total 40.)