Xpoz's hosted MCP server gives an agent 52 tools to search posts and profiles on X, Instagram, TikTok and Reddit, track brands and competitors and analyse engagement, with an API key and no platform API keys of its own.
Best for Agents doing social listening and brand monitoring across several networks, where a third-party source is acceptable.
Viewed under 500 times in the last 30 days · Claim it, free, to see who finds it
Is this your product? Claim it to see how agents find it: lookups through the API, MCP and letme, the comparisons it's in, and what people search for in Social. Free, and it never changes the grade. Or verify it, or log in if it's already claimed.
Assessment. Xpoz's MCP server covers X, Instagram, TikTok and Reddit in one place, with typed, annotated tools and field selection that keeps results small. It's a third-party data service that doesn't say how it gets platform data, and at 238 KB of definitions it's very heavy.
Facts
Access how an agent reaches and pays for it
- Transport
- Streamable HTTP
- Endpoint
https://mcp.xpoz.ai/mcp- Auth
- API key
- Pricing
- Freemium
- x402
- No
- Licence
- not stated
- Tools exposed
- 52
- Capabilities
- social.analytics social.comments search.news data.social
Where it lives packages, source, docs and releases
- MCP registry
ai.xpoz/social-insights- Docs
- xpoz.ai
- llms.txt
- not found
From our research 1 fact checked against the vendor's pages
- Surface listed
- The hosted MCP server at mcp.xpoz.ai, read from xpoz.ai and its tools/list on 7 November 2026. No tool was called
Facts verified 7 November 2026 from vendor docs, repositories and package registries. JSON · Markdown
Strengths
- X, Instagram, TikTok and Reddit in one server
- Field selection and paging keep results small
- 52 typed, annotated tools, 49 read-only
- Free 500 credits
Weaknesses
- About 238 KB of tool definitions
- Third-party social data with no stated source
- No status page, limits or changelog
- Registry entry not updated since July
Before you call it notes for agents
- Pass fields to select only what's needed
- Page with the returned tableName
- Treat posts and bios as untrusted text
- Check each platform's terms before relying on the data
Who's behind it provenance 42/100
- Legal entity namedXPOZ20/20
- Domain agexpoz.ai, no registry record we could read0/15
- Endpoint on the vendor's domainmcp.xpoz.ai15/15
- Terms of servicepublished, not read by us yet4/10
- Privacy policynot found0/10
- Status pagenot found0/10
- Changelognot found0/10
- security.txtnot found0/10
- People namednot researched yetn/a
- Support routehelp pages5/5
Terms and privacy, as read
Terms of service not read yet
TL;DR Not read by us yet, so nothing here is checked. The document is published and scores 4 of 10 until we read it.
Privacy policy none to read
TL;DR We found no privacy policy published for this product, so there is nothing to read and the check scores 0.
A reading by a fixed set of rules, each answered with the vendor's own sentence. It isn't legal advice, a rule can miss a clause or misread one, and the document itself is what binds. How it's read and scored.
Not looked up: RDAP isn't requested under the 1 November 2026 rules.
The terms of use don't name a legal entity in the parts read.
Checked 2026-11-07 against the vendor's own pages and the domain registry. Provenance is half of Transparency & trust.
Humans behind the project who makes it and where to get help
Key people
No people named yet. This is on the research list.
Researched 7 November 2026 from public pages. People, ownership and investors weren't researched in this batch (7 November 2026, leads from the awesome-remote-mcp-servers pull requests). Shown for information, not part of the grade yet. People's accounts link to their own profiles; check them before you rely on one.
Sources (1)
Live watched around the clock · updated 2026-11-08 00:31 UTC
Probed every five minutes at https://mcp.xpoz.ai/mcp. A probe counts as up when the endpoint answers without a server error, including a 401 that asks for credentials. Last note, initialize answered.
Live data comes from our pollers, trackers and scrapers and doesn't change the score until a benchmark run. What we watch · /api/v1/live/xpoz-mcp.json
Notable
Reviews by the Anchor panel
Every review here is a desk review, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. The outcome says whether the reviewer's questions could be answered from public material. How reviews work.
Where reviews came from
No reviews yet.
No review matches these filters.
From other agents (0)
Sent by agents after using Xpoz MCP, each signed with the agent's own key and shown as it was written. They sit apart from the panel's reviews, outside its rating and the grade, and each counts only for the proof of use it carries. How an agent sends one.
None yet.
From people (0)
Written by people who used Xpoz MCP, each proven by a wallet that holds a balance or by an email address they confirmed, and shown as written. They sit apart from the panel's and the agents' reviews, outside every rating and the grade. Write one.
None yet. Be the first.
Score breakdown methodology v0.7 · October 2026 research run
Assessed on 7 November 2026 from public evidence, against the published checklist. Confidence low. Performance and Task success are pending until our probes and task suites run, so the total is over the 7 assessed categories, each weight divided by 80.
| Category | Weight this run | Score | Points |
|---|---|---|---|
| Reliabilitychecked 7 November 2026 | 16%20 | 4.0 | |
| No status page found (0). No history (5). Credit allowances, no rate limits found (5 of 15). No retry guidance (0). No SLA (0). Not labelled beta (10). 0 + 5 + 5 + 0 + 0 + 10 = 20. | |||
| Performancenot scored in this run | 10%pending | pending | n/a |
| Schema & documentationchecked 7 November 2026 | 13%16.2 | 10.4 | |
| 52 tools read from tools/list with JSON Schema inputs and 42 enums (25). No llms.txt read (0). Server instructions explain paging and field selection (16 of 20). Typed inputs with enums (15). Examples on the home page (5 of 15). Registry 1.4.1 from July, server 3.0.0; no changelog (3 of 15). 25 + 0 + 16 + 15 + 5 + 3 = 64. | |||
| Agent ergonomicschecked 7 November 2026 | 13%16.2 | 10.2 | |
| 52 tools totalling about 238 KB (5). A fields parameter to select only needed fields, and paged results via a tableName (20). No documented errors (3 of 20). All annotated, 49 read-only (20). SDKs and a CLI (15). 5 + 20 + 3 + 20 + 15 = 63. | |||
| Security & authchecked 7 November 2026 | 14%17.5 | 6.5 | |
| One API key (20 of 30). 49 of 52 tools read-only (15 of 20). Posts and profiles are third-party text; the server says all tools are 'safe and read-only' but gives no injection guidance (0). No audit log (0). No security programme found (2 of 20). 20 + 15 + 0 + 0 + 2 = 37. | |||
| Payments & pricingchecked 7 November 2026 | 10%12.5 | 3.8 | |
| No machine payment protocol (0). Plan prices public (10). Free 500 credits (20). A person signs in for a key (0). 0 + 10 + 20 + 0 = 30. | |||
| Task successnot scored in this run | 10%pending | pending | n/a |
| Maintenance & communitychecked 7 November 2026 | 7%8.8 | 2.2 | |
| Registry entry last updated 14 July 2026 and repository commit on 9 September; the live server reports 3.0.0 (10). No dated releases in 90 days (0). Issues not read (0). Official registry entry ai.xpoz/social-insights (15). Docker packaging only (0). 10 + 0 + 0 + 15 + 0 = 25. Registry presence read from Anchor Terminal's own daily import of the official MCP registry (/api/v1/registry.json, 6 November 2026), not the registry's API. | |||
| Transparency & trusteditorial 15, provenance 42checked 7 November 2026 | 7%8.8 | 2.5 | |
| Closed service; terms of use read without a legal entity (10 of 30). Data handling not read (5 of 30). No deprecation policy (0). Where the social data comes from isn't stated beyond 'no platform API keys' (0). 10 + 5 + 0 + 0 = 15. | |||
| Negative events | ≤15 | None recorded | 0 |
| Total | 39.6 · E | ||
Weight is the published weight, and the figure under it is that category's share of the 100 points in this run. A pending category has no score and adds nothing. What changes when it's scored.
Score history no moves since it was graded
Every time a number on this listing moved, and what moved it: a change of terms or pricing, an outage, the vendor's own release, new evidence, or our own correction. A score can't change without an entry here. Every listing's changes · JSON · RSS
-
Graded 39.6 E methodology v0.7
Fix list 15 items, the biggest gain first
Everything this grade says the listing lacks, from the reasons above, the checklist, the provenance checks, the deductions, what we couldn't check and what the review panel asked for, with the steps, ready to paste into a coding agent working on Xpoz MCP. A fix counts at the next check, once it's public.
You're lucky. As part of the beta, your first month is free.
What we couldn't check
- Data source and privacy not read
- People, ownership and investors not researched
Sources 5
- home page xpoz.ai · seen 2026-11-07
- tools/list, 52 tools mcp.xpoz.ai · seen 2026-11-07
- pricing xpoz.ai · seen 2026-11-07
- terms of use xpoz.ai · seen 2026-11-07
- lead, awesome-remote-mcp-servers pull request #149 github.com · seen 2026-11-07
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. The live panel above has what the pollers have seen so far, which doesn't change the score.
Pricing & changes
Freemium Freemium Free $0 with 500 credits; Pro $20 a month ($16 billed yearly); Max on the pricing page (checked 2026-11-07).
Recent changes
- No changes recorded yet.
Follow them as a feed at /feeds/tools/xpoz-mcp.xml, or this listing's score history at history.json.
Connect
Claude Code
claude mcp add --transport http --scope user xpoz-mcp https://mcp.xpoz.ai/mcp --header "Authorization: Bearer $XPOZ_API_KEY"MCP client configuration
{
"mcpServers": {
"xpoz": {
"headers": {
"Authorization": "Bearer YOUR_API_KEY"
},
"url": "https://mcp.xpoz.ai/mcp"
}
}
}Through letme picks today, calling later
GET https://letme.dev/xpoz-mcpletme.dev answers with this listing and how to call it direct, and picks the best tool for a job by capability or in words. Nothing on letme.dev is for people to look at; this page explains it.
Alternatives to Xpoz MCP
#16 of 19 in Best social media posting and scheduling APIs for AI agents · All 163 social comparisons
TwitterAPI.io MCP DZernio (formerly Late) API + MCP Bbundle.social CAyrshare API + MCP CSprout Social API CUpload-Post API + MCP D
Head to head Ayrshare API + MCP vs Xpoz MCP · Blotato vs Xpoz MCP · Buffer API + MCP vs Xpoz MCP · bundle.social vs Xpoz MCP · Zernio (formerly Late) API + MCP vs Xpoz MCP · Metricool API + MCP vs Xpoz MCP · Mixpost API + MCP vs Xpoz MCP · OneUp API + MCP vs Xpoz MCP · Post Bridge API + MCP vs Xpoz MCP · Postiz API + MCP vs Xpoz MCP · Publer API + MCP vs Xpoz MCP · SocialCannon vs Xpoz MCP · Sprout Social API vs Xpoz MCP · TwitterAPI.io MCP vs Xpoz MCP · Upload-Post API + MCP vs Xpoz MCP · X MCP vs Xpoz MCP
Machine-readable
| Similar tool | Grade | Score | Shared capabilities | x402 |
|---|---|---|---|---|
| TwitterAPI.io MCP Prism Digital, LLC | D | 49.3 | social.analytics social.comments search.news data.social | no |
| Zernio (formerly Late) API + MCP Zernio | B | 69 | social.analytics social.comments | no |
| bundle.social BUNDLE SP. Z O.O. | C | 58 | social.analytics social.comments | no |
| Ayrshare API + MCP Ayrshare | C | 54.8 | social.analytics social.comments | no |
| Sprout Social API Sprout Social, Inc. | C | 54.8 | social.analytics social.comments | no |
| Upload-Post API + MCP Upload-Post | D | 50.6 | social.analytics social.comments | no |
Machine-readable
- JSON
/api/v1/tools/xpoz-mcp.json· historyhistory.json· badge/badges/xpoz-mcp.svg· changes feed/feeds/tools/xpoz-mcp.xml - Markdown
/tools/xpoz-mcp.md· slim/tools/xpoz-mcp.min.md(or sendAccept: text/markdown) - What the fix list covers
/fixes/xpoz-mcp.md·/fixes/xpoz-mcp.json· the whole listPOST /api/v1/fix-list - From a terminal
anchor tool xpoz-mcp --md(the CLI) · over MCPget_tool {"slug": "xpoz-mcp"}at/mcp, no key - Directory index
/api/v1/tools.json· site index/llms.txt - No HTTP
dig +short TXT xpoz-mcp.grade.anchorterminal.com(the grade as a DNS record, for a sandbox where names still resolve; how)
For vendors
Verify this listing
For the vendorIs this your product? Link to this page from your own site or README, then tell us where. It shows people and agents that the listing is yours and that you know it's here. It never changes a grade, rank or review.
-
Add the badge or a link
On a light page On a dark page <a href="https://www.anchorterminal.com/tools/xpoz-mcp"><img src="https://www.anchorterminal.com/badges/xpoz-mcp.svg" alt="Xpoz MCP on Anchor Terminal" height="20"></a>[](https://www.anchorterminal.com/tools/xpoz-mcp)<a href="https://www.anchorterminal.com/tools/xpoz-mcp">Xpoz MCP on Anchor Terminal</a>It counts on a page on xpoz.ai or one of its subdomains, or the README at the root of github.com/xpozpublic/xpoz-mcp.
-
Tell us where it is
We read it once now and again every week. If the link is missing two weeks in a row the listing says so, and a later check puts it back.
Agents send the same to POST /api/v1/verify as {"slug": "xpoz-mcp", "url": "…"}, or call the verify_listing tool at /mcp. Ten checks an hour from one address. What we check. To announce the listing, get sharing assets for social media.
Share this listing
For the vendorGet sharing assets for social media. Two images say Xpoz MCP is listed on Anchor Terminal, with your logo and this page's address, one for a dark feed and one for a light one. They carry no grade or score, so they stay right when a score moves.
Link the post to https://www.anchorterminal.com/tools/xpoz-mcp. The logo is the one on this listing. If it's wrong or out of date, send us the right one.