Statuser vs XPOZ Social Insights
A side-by-side look at the Statuser and XPOZ Social Insights MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
X
XPOZ Social InsightsMonitoring · Remote HTTP/SSETwitter/X and Instagram data access without API keys. Get profiles, posts, comments, and metrics.39FairAuth: no auth requiredVerdict: choose Statuser for monitoring work as a local process; choose XPOZ Social Insights for monitoring over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Statuser when
- You need dedicated capabilities in the Monitoring domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
STATUSER_API_KEY.
XChoose XPOZ Social Insights when
- You need dedicated capabilities in the Monitoring domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: No auth required.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | X XPOZ Social Insights | |
|---|---|---|
| Category | Monitoring | Monitoring |
| Quality signal | 45/100 · Fair | 39/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | API key required | No auth required |
| Pricing | BYOK (pay the provider) | Not declared |
| Required env vars | STATUSER_API_KEY | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 24 | — |
| Directory activity | 0 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Statuser | View XPOZ Social Insights |
Tools & capabilities
Statuser tools
No tool names declared yet. Check the project README from the listing page.
XPOZ Social Insights tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Statuser
{
"mcpServers": {
"statuser": {
"command": "npx",
"args": [
"-y",
"@statuser/mcp"
],
"env": {
"STATUSER_API_KEY": "YOUR_STATUSER_API_KEY_HERE"
}
}
}
}
XPOZ Social Insights
{
"mcpServers": {
"xpoz-social-insights": {
"command": "npx",
"args": [
"-y",
"xpoz-social-insights"
]
}
}
}
Frequently asked questions
Statuser is categorized under Monitoring and uses a local stdio subprocess. XPOZ Social Insights belongs to Monitoring and uses a remote HTTP/SSE transport. Pick Statuser for monitoring work and XPOZ Social Insights for monitoring.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Statuser is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: api key required. XPOZ Social Insights has no declared pricing — check the project's own site. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add statuser and xpoz-social-insights as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Statuser has a quality signal of 45/100 (Fair) with 0 views, 0 installs and 24 GitHub stars. XPOZ Social Insights has 39/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.