ViralSpy MCP

The remote Streamable HTTP endpoint is:

https://api.viralspy.com/mcp

MCP is a protocol between an AI client and ViralSpy. ViralSpy publishes tool names, descriptions, strict argument and result schemas, workflow instructions, resources, and prompt templates. Your client exposes those capabilities to its model; the model chooses calls and receives the structured results directly.

Recommended workflow

1. Use a narrow search or feed tool.
2. Fetch interesting items by immutable ID.
3. Compare source fields and URLs.
4. Use viralspy_analyze only when the high-level analyst adds value; it consumes the shared monthly allowance.

The server's first instructions emphasize this workflow so agents can make sensible calls without copying a large prompt into every conversation. Prompts are optional user-invoked templates; resources provide deeper reference material; tools perform the actual work.

Transport and compatibility

ViralSpy implements the current MCP per-request protocol and maintains stateless compatibility with 2025-era Streamable HTTP clients. Responses use an SSE stream, including keep-alive frames for long-running viralspy_analyze calls, followed by the terminal JSON-RPC result. During beta, API-key authentication is the default. OAuth 2.1 is available to explicitly registered clients.