Technical specification

Remote MCP connector

ViralShark exposes a focused Model Context Protocol surface for approved AI clients.

Connection details

Endpoint
https://api.viralshark.app/mcp

Transport
Streamable HTTP

Authorization
OAuth 2.1 authorization code flow with PKCE

Response format
MCP tool results with structured content and source URLs

Architecture

AI client
  → ViralShark MCP gateway
    → authenticated ViralShark workflows
      → selected evidence and source links

The gateway is deliberately thin. Search quality, freshness checks, source selection, usage controls, and future workflow improvements remain in ViralShark’s backend. Clients benefit from those improvements without changing their connector configuration.

Access boundaries

Every protected capability requires an authorized ViralShark user.
Plan and usage controls are enforced by the ViralShark backend.
The connector cannot access another customer’s chats, saved posts, or account data.
Users can revoke connector access from their account or AI client.