# X MCP > X MCP is X Corp.'s hosted Model Context Protocol server for the X API at api.x.com/mcp. It lets a model search posts, look up users, manage bookmarks, read trends and news, and draft Articles. - Canonical: https://www.anchorterminal.com/tools/x-mcp - Markdown: https://www.anchorterminal.com/tools/x-mcp.md (~7,350 tokens) - Slim: https://www.anchorterminal.com/tools/x-mcp.min.md (~1,480 tokens, same facts, less prose, for token-sensitive contexts) - JSON: https://www.anchorterminal.com/tools/x-mcp.json (this page as data, same URL with Accept: application/json) - Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.txt) - API: https://www.anchorterminal.com/api/v1/index.json - Updated: 2026-10-08 ## Overview **Grade C · 55.4/100 · rank #451 of 629 · #6 in Social media posting APIs · not agent-ready · confidence medium** ## Assessment First-party access to full-archive post search, user lookup, trends and news, with OAuth 2.0 PKCE scopes and per-resource prices published without a login. Every user must create a paid X developer app, the tool list isn't published, and the documented tools don't create posts. ## Facts | Field | Value | | --- | --- | | Vendor | X Corp. (https://docs.x.com/tools/mcp) | | Kind | MCP server | | Category | Social media posting APIs (https://www.anchorterminal.com/categories/social-media) | | Transport | Streamable HTTP, stdio | | Endpoint | `https://api.x.com/mcp` | | Auth | OAuth or key · A person creates an app in the X Developer Portal, on the Pay-per-use package in Production. Reads work with the app-only Bearer token in an `Authorization` header sent straight to https://api.x.com/mcp. User-context tools (bookmarks, Articles, the current user) need OAuth 2.0 authorisation code with PKCE through the local `xurl mcp` bridge, which takes CLIENT_ID and CLIENT_SECRET, needs the redirect URI http://localhost:8080/callback registered, opens a browser once, then caches and refreshes tokens in ~/.xurl. No dynamic client registration. Self-serve, with no review step documented. | | Pricing | Pay per use ($0.005 / call) · Pay-per-use credits bought in advance in the Developer Console, with no subscription and no free tier. Reads are charged per resource returned ($0.005 a post, $0.010 a user, $0.001 for the app owner's own data) and writes per request ($0.005 a bookmark, $0.010 a trends request). A one-time $20 credit needs a saved payment card. The MCP page doesn't say MCP calls are billed at these API rates, though it requires a Pay-per-use app (https://docs.x.com/x-api/getting-started/pricing.md). | | x402 | No · No x402, MPP or L402 in the MCP page, the pricing page, the docs index or the OpenAPI spec (checked 2026-10-08). | | Licence | Proprietary hosted server under the X Developer Agreement. The xurl bridge on GitHub and npm is MIT | | Packages | npm: `@xdevplatform/xurl` | | Source | https://github.com/xdevplatform/xurl | | Docs | https://docs.x.com/tools/mcp | | llms.txt | https://docs.x.com/llms.txt | | Last release | 2026-09-29 | | GitHub stars | 1,352 (as of 2026-10-08) | | npm downloads / week | 6,027 | | Server | Hosted Streamable HTTP at https://api.x.com/mcp, protocol 2025-06-18, serverInfo `xmcp`. Closed source | | Tools | Posts (lookup, likers, reposters, quoters, counts), full-archive post search, user search, news search, user lookup and timelines, bookmarks and folders, trends by location, Article drafts and publishing. The tool count isn't published | | Not covered | Creating posts or replies, likes, follows and direct messages aren't in the documented tool groups | | Access | Own X developer app on Pay-per-use in Production. App-only Bearer token for reads, or OAuth 2.0 PKCE through the `xurl mcp` bridge for user context | | Bridge | @xdevplatform/xurl 1.3.4 (MIT, Go, 29 September 2026), run with npx. Tokens cached in ~/.xurl | | Pricing | Prepaid credits. $0.005 a post read, $0.010 a user read, $0.001 an owned read, $0.005 a bookmark write, capped at 3 million post reads a month on Pay-per-use | | Rate limits | Per endpoint and 15-minute window on the API, such as 300 per 15 minutes and 1 a second for full-archive search and 50 per 15 minutes for bookmark writes. No MCP-specific limits published | | Docs for agents | llms.txt, llms-full.txt, Markdown for every page, skill.md, AGENTS.md and an OpenAPI spec at https://api.x.com/2/openapi.json | | Capabilities | social.analytics | | Tags | official, hosted, mcp, oauth, usage-priced, prepaid, card-required, openapi, llms-txt, closed-source, cli, go | | JSON | https://www.anchorterminal.com/api/v1/tools/x-mcp.json | ## Score breakdown (methodology v0.4, October 2026 research run) Assessed 2026-10-08 from public evidence against the published checklist (https://www.anchorterminal.com/benchmark/#checklist). Confidence: medium. Performance and Task success pending (no score, not in the total); the total is Σ(score × weight) ÷ 80 over the 7 assessed categories. "This run" is each category's share of the 100 points. | Category | Weight | This run | Score (0–100) | Points | | --- | --- | --- | --- | --- | | Reliability | 16% | 20 | 72 | 14.4 | | Performance | 10% | pending | pending | n/a | | Schema & documentation | 13% | 16.2 | 65 | 10.6 | | Agent ergonomics | 13% | 16.2 | 45 | 7.3 | | Security & auth | 14% | 17.5 | 48 | 8.4 | | Payments & pricing | 10% | 12.5 | 20 | 2.5 | | Task success | 10% | pending | pending | n/a | | Maintenance & community | 7% | 8.8 | 70 | 6.1 | | Transparency & trust (editorial 50, provenance 89) | 7% | 8.8 | 70 | 6.1 | | Negative events | up to −15 | up to −15 | none recorded | 0 | | **Total** | | | | **55.4 → C** | ### Why each score - Reliability 72: Read with the hosted lines, since the server runs at api.x.com and the bridge only relays. A status page exists at developer.x.com/status but needs JavaScript and showed our reader nothing. The dated incident history at docs.x.com/incidents.md lists incidents by title, with no component view and no MCP entry (15 of 20). That history has no incident dated after 1 July 2026, so the 90 days to 8 October are clean, apart from a 'Missing entities.annotations' entry marked ongoing since 24 March 2026 (25 of 30). API rate limits are published per endpoint, such as 300 per 15 minutes and 1 a second for full-archive search and 50 per 15 minutes for bookmark writes. The MCP page gives no numbers of its own and says only that writes are stricter than reads (12 of 15). 429s come with `x-rate-limit-reset` and the docs advise waiting for it and backing off. No Retry-After and no idempotency keys for writes were found (10 of 15). No SLA found for Pay-per-use (0). The MCP page carries no beta or preview label (10). 72. - Performance: Pending. Latency is measured per call by our probes, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until the first probe window closes. - Schema & documentation 65: A public OpenAPI spec covers the API behind it (version 2.169, 175 paths, 218 operations). The MCP tool list and input schemas aren't published, and tools/list answers 401 without a token, so we didn't read them (18 of 25). llms.txt, llms-full.txt, skill.md and Markdown for every page (10). The MCP page describes six groups of tools and names one tool, `article_publish`, with no per-tool guidance on when to use which (6 of 20). The API parameters are typed in the spec. Whether the MCP tools carry the same enums and constraints is unread (8 of 15). Client configs for five clients, a troubleshooting table of eight symptoms and a documented problem+json error format with eleven error types (12 of 15). The API is versioned in the path and has a dated changelog with an RSS feed, latest entry 2 October 2026, but the changelog has no entry for the hosted MCP server and the server publishes no version history (11 of 15). 65. - Agent ergonomics 45: The number of tools isn't published. One docs page lists six groups and another says XMCP exposes 200+ endpoints as tools, so we scored context cost as not established (5 of 25). The API has `max_results`, `pagination_token`, field selection and expansions. Whether each MCP tool passes them through is unread (12 of 20). Errors are problem+json with a type URI, title and detail, and the bridge turns transport and token failures into JSON-RPC errors keyed to the request (15 of 20). No idempotency keys, and no readOnlyHint or destructiveHint documented. The bridge refreshes the token and retries after a 401 (4 of 20). One npx line starts the bridge and the URL has a default, but each user first creates an app, registers a redirect URI and sets a 300-second startup timeout. Official XDKs exist for Python and TypeScript (9 of 15). 45. - Security & auth 48: OAuth 2.0 authorisation code with PKCE (S256), scopes and refresh tokens, and the resource metadata accepts bearer tokens in the header only. Less 6 because xurl 1.3.4 requests a fixed set of 24 scopes including tweet.write and dm.write with no flag to narrow them, and the bridge config holds the client secret in plain text (24 of 30). The app-only Bearer route is read-only per the docs. No confirmation step is documented for `article_publish` or for removing bookmarks, so approval rests with the MCP client (10 of 20). Posts, profiles and news text come from anyone on X, and the security section has no guidance on prompt injection (0 of 15). The Developer Console shows usage and spend live and /2/usage/tweets returns daily counts. No per-call log was found (6 of 15). x.com's security.txt points to HackerOne but expired on 1 January 2024, and we found no SOC 2 or ISO 27001 statement in what we read (8 of 20). 48. - Payments & pricing 20: No x402, MPP or L402 (0). Per-resource and per-request prices are published without a login, such as $0.005 a post read, $0.010 a user read and $0.005 a bookmark write (20). No free tier. Credits are bought in advance, and the one-time $20 credit needs a saved payment card (0). A person signs in to the developer portal, creates an app and completes a browser login (0). 20. - Task success: Pending. Task success needs the category task suites run through each tool, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until then. A data provider's data-quality score is published on its listing now and becomes half of this category when it's scored. - Maintenance & community 70: The xurl bridge reached 1.3.4 on 29 September 2026 and the platform changelog's latest entry is 2 October 2026 (30). Six xurl releases since 16 July 2026, and ten platform changelog entries since 21 July (20). The xurl changelog credits fixes to numbered issues, and the repository showed 7 open issues and 8 open pull requests on 8 October. We couldn't read the threads or the developer forum, which answered 403 (12 of 25). No X entry in the official MCP registry under searches for xmcp, xdevplatform and com.x (0). Go 1.24 with build, test, gofmt and release-build jobs in CI (8 of 10). 70. - Transparency & trust 70: The hosted server is closed, under a Developer Agreement last updated 27 April 2026, and the bridge is MIT (18 of 30). The privacy policy, effective 15 January 2026, describes retention by data type and names the controllers. The terms of service let X use content to train its AI models. No DPA or subprocessor list for developers was found in what we read (14 of 30). The versioning page limits breaking changes to major versions, at most yearly, with migration guides. Dated notices exist but can be short, such as five days for the Account Activity replay endpoint in March 2026 and four days for the removal of follows, likes and quote posts from self-serve tiers in April 2026 (14 of 20). Controllers for the US and Europe are named. No subprocessor or data location list found (4 of 20). 50. Fix list for a coding agent, everything this grade says the listing lacks, the biggest gain first (21 items): https://www.anchorterminal.com/fixes/x-mcp.md (JSON https://www.anchorterminal.com/fixes/x-mcp.json) ### What we couldn't check - unchecked: the MCP tool list, input schemas, descriptions and annotations. tools/list needs a token from a Pay-per-use app, which we don't have - unchecked: the live status page at developer.x.com/status, which needs JavaScript. Incident history was read from docs.x.com/incidents.md - unchecked: issue and pull request threads on xdevplatform/xurl (the GitHub API was rate-limited) and devcommunity.x.com, which answered 403 - unchecked: the HackerOne programme page, which is a JavaScript app. The only pointer read is the expired security.txt - How many tools the server exposes. The MCP page lists six groups and the Agent Resources page says 200+ endpoints - Whether MCP calls are billed at the published API rates and whether failed calls are charged. The MCP page requires a Pay-per-use app but doesn't say - When the hosted server launched. The docs give no date, and the first dated evidence is `xurl mcp` on 25 June 2026 - The docs say the endpoint has no MCP OAuth discovery, yet it serves protected resource metadata. We didn't test whether a client can sign in directly with a pre-registered client ID - Whether the developer.write and developer.billing.write scopes listed for the MCP resource back tools that create apps or buy credits - The category has no capability for searching or reading a network. We used social.analytics as the nearest and left out social.post, since the only publishing tool documented is for Articles - No deduction was made for the short-notice API changes of February and April 2026, which predate the hosted server and concern posting endpoints it doesn't document ### Sources - MCP page (setup, auth routes, tool groups, troubleshooting, security): (seen 2026-10-08) - Agent Resources page: (seen 2026-10-08) - MCP endpoint, unauthenticated initialize (401 with resource_metadata): (seen 2026-10-08) - OAuth protected resource metadata: (seen 2026-10-08) - OAuth authorisation server metadata: (seen 2026-10-08) - OpenAPI spec 2.169: (seen 2026-10-08) - pricing: (seen 2026-10-08) - free credit incentives: (seen 2026-10-08) - rate limits and 429 handling: (seen 2026-10-08) - response codes and errors: (seen 2026-10-08) - versioning policy: (seen 2026-10-08) - platform changelog: (seen 2026-10-08) - incident history: (seen 2026-10-08) - docs index for agents: (seen 2026-10-08) - Developer Agreement: (seen 2026-10-08) - xurl repository (README, CHANGELOG, auth/auth.go, CI workflows, tags), cloned: (seen 2026-10-08) - xmcp repository (older local server), cloned: (seen 2026-10-08) - xurl on npm, version 1.3.4: (seen 2026-10-08) - npm weekly downloads, 28 September to 4 October: (seen 2026-10-08) - official MCP registry search: (seen 2026-10-08) - X terms of service: (seen 2026-10-08) - X privacy policy: (seen 2026-10-08) - security.txt (expired 1 January 2024): (seen 2026-10-08) - RDAP record for x.com: (seen 2026-10-08) ## Who's behind it (provenance 89/100, checked 2026-10-08) | Check | Finding | Points | | --- | --- | --- | | Legal entity named | X Corp. | 20/20 | | Domain age | x.com, registered 1993-04-02 (33 years) | 15/15 | | Endpoint on the vendor's domain | api.x.com | 15/15 | | Terms of service | read, states 6 of the 7 things a reader expects, and has 1 clause that costs points | 7.1/10 | | Privacy policy | published, but our reader couldn't read it | 7/10 | | Status page | developer.x.com/status | 10/10 | | Changelog | published | 10/10 | | security.txt | published but past its Expires date | 5/10 | The X terms of service name X Corp., 800 W Cesar Chavez St., Austin, TX 78701, and the privacy policy (effective 15 January 2026) names X Internet Unlimited Company as controller for the EU, EFTA and the UK. https://x.com/.well-known/security.txt is PGP-signed, points to hackerone.com/twitter and expired on 1 January 2024. api.x.com and docs.x.com return 404 for the file. https://developer.x.com/status needs JavaScript and showed our reader no status data. The incident history is readable at https://docs.x.com/incidents.md. RDAP for x.com gives a registration date of 1993-04-02. ### Terms and privacy, as read A reading by a fixed set of rules, each answered with the vendor's own sentence. Not legal advice. **Terms of service** (https://docs.x.com/developer-terms/agreement), read 2026-10-08, dated 2026-04-27, states 6 of the 7 things a reader expects. - To know. Restricts benchmarking or competitive use (costs points). "use or access the Licensed Material to create or attempt to create a substitute or similar service or product to the X Applications" - To know. Says access can be ended without notice or for any reason. "X may terminate this Agreement for any reason at X’s sole discretion." - To know. Requires arbitration or waives class actions. "Class Action Waiver. To the extent permitted by law, you also waive the right to participate as a plaintiff or class member in any purported class action, collective action, or representative action proceeding." - Gives the date it was last updated. Last updated 2026-04-27. - Names the governing law or courts. The law of the State of Texas. - States a limit on its liability. Capped at $50.00. - Says how changes to the terms are announced. Says it gives notice of a change. - Not found in the text. Refers to a service level or uptime commitment. - Also in the text (2026-10-08). X's total liability for all claims under the agreement is capped at 50 US dollars. "IN ANY CASE, X’S AGGREGATE LIABILITY FOR ANY AND ALL CLAIMS UNDER THIS AGREEMENT WILL NOT EXCEED FIFTY DOLLARS ($50.00)." - Also in the text (2026-10-08). The X API and X Content may not be used to fine-tune or train a foundation or frontier model. "use the X API or X Content to fine-tune or train a foundation or frontier model" - Also in the text (2026-10-08). On termination the developer must permanently delete all Licensed Material and, if X asks, give evidence of deletion within ten business days. "Upon the request of X for any reason, you will promptly (and in any event within ten (10) business days of such request) provide evidence (e.g., screenshots of deletion confirmation) of compliance with the provisions of the aforementioned subpart (b) of this Section." **Privacy policy** (https://x.com/en/privacy), read 2026-10-08. Our reader couldn't read it (robots.txt asks readers like ours not to fetch it). ## Live (updated 2026-10-08 17:36 UTC) - Right now: up, HTTP 401, 142 ms, checked 2026-10-08 17:36 UTC (mcp-initialize on `https://api.x.com/mcp`, asks for auth) - Uptime 24h 100.0% (25 probes) · 30 days 100.0% (25 probes) · p50 137 ms · p95 304 ms - Vendor status page: unknown, no machine-readable status found - github `xdevplatform/xurl` v1.3.4, released 2026-09-29 - npm `@xdevplatform/xurl` 1.3.4 - security.txt: expired, expires 2024-01-01T06:00:00.000Z - Always current: https://www.anchorterminal.com/api/v1/live/x-mcp.json ## Probe metrics Not measured yet. Our benchmark probes haven't run, so there's no availability, latency or error rate from a run and Performance is pending. Live uptime, where we poll the endpoint, is under Live and doesn't change the score. ## Prices | Item | Price | Unit | Note | | --- | --- | --- | --- | | Post read | $0.005 | per record | per post returned, deduplicated within a UTC day | | User read | $0.01 | per record | per user returned | | Owned read (the app owner's own posts, bookmarks, followers) | $0.001 | per record | when the authenticated user owns the app | | Bookmark write | $0.005 | per call | per request | | Trends request | $0.01 | per call | per request | Across all listings: https://www.anchorterminal.com/prices/index.md ## Strengths - Hosted by X on api.x.com, with full-archive post search, user search and news search among the documented tools - OAuth 2.0 with PKCE (S256), refresh tokens and header-only bearer tokens, per the server's published metadata - Per-resource prices are public, such as $0.005 a post read and $0.001 for reads of the app owner's own data - The xurl bridge is MIT, at 1.3.4 from 29 September 2026, with six releases since 16 July - llms.txt, Markdown for every docs page and a public OpenAPI spec (version 2.169, 175 paths) ## Weaknesses - No dynamic client registration, so each user creates an X developer app on the Pay-per-use package in Production - The tool list and tool schemas aren't published, and the endpoint answers 401 without a token - The documented tools don't create posts, replies, likes or follows. Writes cover bookmarks and Articles - xurl 1.3.4 asks for a fixed set of 24 scopes, including tweet.write and dm.write, with no flag to narrow them - No guidance on prompt injection, though every post returned is text written by strangers - Not in the official MCP registry, and the platform changelog has no entry for the hosted server ## Before you call it (notes for agents) 1. Use the app-only Bearer header for read-only work. Bookmarks, Articles and any tool working in the user's name need the xurl bridge 2. Set the client's startup timeout to 300 seconds or more, because the bridge holds the handshake until the first browser login ends 3. On a headless host run `xurl auth oauth2 --headless` first, with CLIENT_ID and CLIENT_SECRET exported in that shell 4. On `client-not-enrolled`, move the app to Pay-per-use and Production in the developer portal 5. On 429, wait until the Unix time in `x-rate-limit-reset`. No Retry-After header is documented ## Connect Install: ```bash npm install -g @xdevplatform/xurl ``` MCP client configuration: ```json { "mcpServers": { "xapi": { "args": [ "-y", "@xdevplatform/xurl", "mcp", "https://api.x.com/mcp" ], "command": "npx", "env": { "CLIENT_ID": "YOUR_X_APP_CLIENT_ID", "CLIENT_SECRET": "YOUR_X_APP_CLIENT_SECRET" } } } } ``` Through letme (picks today, calling later): https://letme.dev/x-mcp. letme answers with the pick and how to call it direct; calling through letme (one key, the vendor's own price) comes later. How it works: https://www.anchorterminal.com/letme/index.md ## Similar tools Ranked by shared capabilities, then score. Same-category tools with no shared capability key are listed last. | Tool | Grade | Score | Rank | Shared capabilities | x402 | Markdown | | --- | --- | --- | --- | --- | --- | --- | | Zernio (formerly Late) API + MCP | B | 67.5 | 192 | social.analytics | no | https://www.anchorterminal.com/tools/late.md | | Buffer API + MCP | B | 62 | 311 | social.analytics | no | https://www.anchorterminal.com/tools/buffer.md | | Postiz API + MCP | C | 59.3 | 381 | social.analytics | no | https://www.anchorterminal.com/tools/postiz.md | | Upload-Post API + MCP | C | 58.7 | 396 | social.analytics | no | https://www.anchorterminal.com/tools/upload-post.md | | Ayrshare API + MCP | C | 57.2 | 424 | social.analytics | no | https://www.anchorterminal.com/tools/ayrshare.md | | Mixpost API + MCP | D | 49.5 | 529 | social.analytics | no | https://www.anchorterminal.com/tools/mixpost.md | ## Panel reviews (0) Reviewed by the Anchor panel (https://www.anchorterminal.com/reviewers/index.md): . Desk reviews, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. For a desk review, the outcome says whether the reviewer's questions could be answered from public material: success, partial or failure. How reviews work: https://www.anchorterminal.com/reviews/how-it-works.md ## Notable - Hosted Streamable HTTP server at https://api.x.com/mcp, protocol 2025-06-18, reporting itself as `xmcp`. Two routes are documented, a static app-only Bearer token for reads or the local `xurl mcp` bridge for OAuth 2.0 user context (source: ) - The docs say the endpoint has no native MCP OAuth discovery. On 8 October 2026 it answered an unauthenticated request with 401 and a `resource_metadata` pointer, and https://api.x.com/.well-known/oauth-protected-resource listed 17 scopes for the resource. The authorisation server metadata has no registration endpoint, which matches the docs on dynamic client registration - The scopes listed for the MCP resource include bookmark.write, list.write, block.write, dm.write, developer.write and developer.billing.write, and leave out tweet.write, like.write and follows.write (source: ) - The MCP page lists six groups of tools (posts, search, users, bookmarks, news and trends, Articles) and names one tool, `article_publish`. The Agent Resources page says XMCP exposes 200+ X API endpoints as tools. We couldn't list the tools without a paid app (source: ) - `xurl mcp` was added on 25 June 2026 and shipped in xurl 1.2.0 on 29 June 2026. The platform changelog has no entry for the hosted server (source: ) - An older local server, xdevplatform/xmcp, builds tools from the OpenAPI spec with FastMCP. It was announced on 6 February 2026 and last changed on 9 April 2026. This listing grades the hosted server (source: ) - A second hosted server at https://docs.x.com/mcp needs no credentials and has two tools, `search_x` and `get_page_x`, for the documentation only (source: ) - The Developer Agreement, last updated 27 April 2026, forbids using the X API or X Content to fine-tune or train a foundation or frontier model (source: ) ## Compare - [Ayrshare API + MCP vs X MCP](https://www.anchorterminal.com/compare/ayrshare-vs-x-mcp.md): C 57.2 vs C 55.4 - [Buffer API + MCP vs X MCP](https://www.anchorterminal.com/compare/buffer-vs-x-mcp.md): B 62 vs C 55.4 - [Zernio (formerly Late) API + MCP vs X MCP](https://www.anchorterminal.com/compare/late-vs-x-mcp.md): B 67.5 vs C 55.4 - [Metricool API + MCP vs X MCP](https://www.anchorterminal.com/compare/metricool-vs-x-mcp.md): E 38.3 vs C 55.4 - [Mixpost API + MCP vs X MCP](https://www.anchorterminal.com/compare/mixpost-vs-x-mcp.md): D 49.5 vs C 55.4 - [OneUp API + MCP vs X MCP](https://www.anchorterminal.com/compare/oneup-vs-x-mcp.md): F 24.4 vs C 55.4 - [Post Bridge API + MCP vs X MCP](https://www.anchorterminal.com/compare/post-bridge-vs-x-mcp.md): D 48.3 vs C 55.4 - [Postiz API + MCP vs X MCP](https://www.anchorterminal.com/compare/postiz-vs-x-mcp.md): C 59.3 vs C 55.4 - [Publer API + MCP vs X MCP](https://www.anchorterminal.com/compare/publer-vs-x-mcp.md): D 46.8 vs C 55.4 - [Upload-Post API + MCP vs X MCP](https://www.anchorterminal.com/compare/upload-post-vs-x-mcp.md): C 58.7 vs C 55.4 ## Verify this listing For the vendor. The badge or a plain link to this page verifies the listing, from a page on docs.x.com or one of its subdomains, or the README of github.com/xdevplatform/xurl. It shows the listing is the vendor's and that the vendor knows it's here, and it never changes a grade, rank or review. The vendor sends the page's address to `POST https://www.anchorterminal.com/api/v1/verify` as `{"slug": "x-mcp", "url": "…"}`, or calls the `verify_listing` tool at https://www.anchorterminal.com/mcp. We fetch the page once, then again every week; two failed checks in a row and the verification lapses, and a later pass restores it. What we check: https://www.anchorterminal.com/builders/index.md#verify HTML badge: ```html X MCP on Anchor Terminal ``` Markdown badge, for a README: ```markdown [![X MCP on Anchor Terminal](https://www.anchorterminal.com/badges/x-mcp.svg)](https://www.anchorterminal.com/tools/x-mcp) ``` Plain link: ```html X MCP on Anchor Terminal ``` ## Share this listing For the vendor. Sharing assets for social media, two PNGs of 1200 × 630 that say X MCP is listed on Anchor Terminal, with the vendor's logo and this page's address and no grade or score. - Dark: https://www.anchorterminal.com/assets/share/x-mcp-dark.png - Light: https://www.anchorterminal.com/assets/share/x-mcp-light.png