Xpoz

Created By
Xpoz-AI6 months ago
Remote-only social media MCP server for Twitter/X, Instagram, and TikTok data & insights.
Overview

What is Xpoz?

Xpoz is a remote-only social media MCP server that provides access to data and insights from Twitter/X, Instagram, and TikTok, enabling users to perform social intelligence analysis.

How to use Xpoz?

To use Xpoz, simply add the endpoint URL to your configuration, and you can start querying data without any installation or API keys.

Key features of Xpoz?

  • Zero setup required; no local dependencies needed.
  • No API keys or rate limit management.
  • Access to comprehensive data including user profiles, posts, and engagement metrics.
  • CSV export for bulk data analysis.
  • Secure OAuth 2.0 authentication.
  • Over 1.5 billion posts indexed, including historical data.
  • Multi-platform querying for Twitter/X and Instagram.

Use cases of Xpoz?

  1. Brand monitoring and sentiment analysis.
  2. Competitive intelligence and analysis.
  3. Influencer research and verification.
  4. Content trend analysis.
  5. Social media analytics and OSINT research.

FAQ from Xpoz?

  • Can I access TikTok data?

Yes, TikTok data access is coming soon.

  • Is there a limit to the number of queries I can make?

No, there are no API keys or rate limits to manage.

  • How do I export data?

You can export full datasets to CSV for large-scale analysis.

Server Config

{
  "mcpServers": {
    "xpoz": {
      "url": "https://mcp.xpoz.ai/mcp",
      "transport": "http-streaming",
      "headers": {
        "Authorization": "Bearer [xpoz personal token]"
      }
    }
  }
}
Project Info
Created At
6 months ago
Updated At
6 months ago
Author Name
Xpoz-AI
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

18 hours ago
Crevio

a day ago