Assymetrix MCP Server vs Codex

Assymetrix MCP Server 36

Read with the local-software lines, because the owner runs the server over stdio, though every tool call lands on Assymetrix's hosted Data API. Installs from the official npm package @assymetrix/mcp-server with Node.js 20 or later stated in engines (20). The repository holds seven vitest files and a check script that type-checks, builds and runs them offline, but no GitHub Actions workflow was found and npm shows no provenance, so no passing run is public (5 of 25). GitHub's issue pages and API weren't reachable from this session, and the package is four days old, so there's little record to read (8 of 25, unchecked). Semver numbering with a test that keeps the version constant equal to package.json, but no changelog, release notes or tags were found (3 of 15). Version 0.1.1 (0).

Codex 85

Hosted lines. Status page at status.codex.io (incident.io) with API, Dashboard and 25 network components and a history page (20). The history from 8 August to 6 November lists an elevated-latency incident on 11 August (balances queries, 42 minutes, labelled degraded performance), a 5xx spike the same day, degraded filterTokens on 12 August, and network delays on Robinhood, BNB, Cronos, Fogo and Solana pricing in late August and September, with none in October or November. All read as partial or degraded, so minor only (20). Per-plan rate limits (5 a second free, 300 on Growth with a 500 burst) and per-request maxima are published (15). 429 TOO_MANY_REQUESTS carries retryAfterSeconds and Retry-After, OVER_CAPACITY says to wait 30 seconds, and the errors page says which codes to retry; writes are limited to webhook and token mutations (15). The pricing page shows '99.9% Uptime SLA' as a headline figure and custom SLAs on Enterprise, with no SLA document found (5 of 10). The API is generally available (10). 20+20+15+15+5+10 = 85.

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).

Codex 80

MPP (Machine Payments Protocol) on every query endpoint, paid in USDC on Tempo; subscriptions and webhooks are not covered, and it is not x402 (35 of 40). $0.001 a query through MPP, compute-unit costs per operation, and Growth at $120 per million compute units, all public (20). The Almost free plan's 10,000 compute units need a one-time $1 activation fee by card or 1 USDC, which the terms say confirms a payment method (5 of 20). An agent can pay per query with no account or key (20). 35+20+5+20 = 80.

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).

Codex 80

Closed service. Newest changelog entry 2 November 2026 (30). Weekly entries from 3 August to 2 November, and SDK releases 2.5.10 to 2.5.20 between 28 October and 5 November (20). Public changelog, a Discord, a support address and a status page with a report link; GitHub issue replies were not sampled (10 of 15). Current official TypeScript SDK, no other languages (12 of 15). The SDK repository runs lint and test on pull requests and a release workflow (8 of 10). 30+20+10+12+8 = 80.

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).

Codex 49

Secret API keys in a header, never in the URL. Short-lived tokens from createApiTokens with an expiry and a request limit, per-key compute-unit limits and key deactivation. No scopes (22 of 30). The surface is mostly reads; mutations create webhooks and short-lived tokens. No read-only key (12 of 20). Token names, symbols, social links and community notes come from token deployers and other sources, and the docs warn tokens may be scams, with no prompt-injection guidance (5 of 15). The dashboard usage page breaks compute units down by operation, apiUsage reports the period's use and usageData the cost of each request (10 of 15). security.txt returns 404, and no disclosure policy, bug bounty or certification was found on the site or docs (0 of 20). 22+12+5+10+0 = 49.

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).

Codex 79

GraphQL field selection, so a response holds only the fields asked for, and usageData reports the cost of a request (23 of 25). limit on filter queries up to 200, rankings and 100+ filter signals on filterTokens; some list arguments drop extra inputs silently rather than failing (18 of 20). Coded errors an agent can branch on, but most arrive as HTTP 200 in an errors array, and an inline input type mismatch returns only a message (16 of 20). Queries are reads and identical requests cost the same; errors are not billed except NOT_FOUND. No idempotency key on the webhook and token mutations (14 of 20). Few required arguments beyond networkId. One official SDK, TypeScript (8 of 15). 23+18+16+14+8 = 79.

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).

Codex 59

Closed service under terms that name Codex Data Inc., last updated 29 October 2026; the SDK is MIT (15 of 30). The privacy policy (effective 29 September 2026) is general, keeps data 'only for as long as is necessary' with no periods, transfers data to the United States, and links no DPA or subprocessor list (10 of 30). The changelog dates deprecations, such as NFT endpoints removed on 31 March 2026 and the transactions fields deprecated on 2 November, with no written deprecation policy or notice period (12 of 20). The terms name Mixpanel, Rollbar and Sentry and the privacy policy says data is processed in the United States; no fuller subprocessor list found (8 of 20). 15+10+12+8 = 45.