Sweeppea MCP: Professional US & Canada Sweepstakes Compliance Manage sweepstakes, participants, and winner drawings directly through a unified interface. Create official rules, schedule events, and handle support tickets to streamline your promotion workflow while ensuring legal compliance across the United States and Canada. 🚀 How It Works The Sweeppea MCP Server acts as a secure bridge between AI assistants and the official Sweeppea API. It translates natural language interactions into structured API calls, giving your AI assistant control over: Participant Management & Winner Drawings. Legally Compliant Official Rules Generation. Promotion Calendars & Event Scheduling. Real-time Billing & Data Insights. Architecture Flow Your AI Assistant → MCP (Protocol) → Sweeppea MCP Server → Sweeppea API v3 🔐 Authentication & Pricing This MCP server requires a Sweeppea API Key tied to an active subscription. Why a Professional Service? Running sweepstakes in the United States and/or Canada is legally complex. Each jurisdiction has its own regulations, including registration requirements, bonding thresholds, and prize disclosure laws. Sweeppea manages this complexity by generating official rules that comply with federal and state-level consumer protection statutes. The platform also handles multi-state eligibility and enforces entry limits, providing an auditable record of every participant and winner draw. Your API Key grants access to a system built specifically to keep sweepstakes legally defensible.

MCP readiness

B · 87/100

Readiness is how fully this listing follows its protocol and how it behaved in our probes over 30 days. It is shown for reference and does not move it in search. Search order and leaderboards use the separate quality grade (here C+, 70.0/100), which weighs availability, conformance, p95 speed and descriptor. How the two differ

Valid MCP handshake	10/10	initialize and tools/list both answered.
Live MCP endpoint	24/25	Endpoint answers the MCP initialize handshake (2527 ms); slow response -1.
Protocol revision	8/10	Speaks MCP 2025-11-25, 1 revision(s) behind 2026-07-28.
Signed descriptor	n/a	No MCP standard defines a signed server descriptor.
Uptime (30 days)	15/15	31/31 probes succeeded over 30 days (100%).
Tool declaration	10/10	Lists 60 tool(s) with descriptions.
Verified identity	5/10	Publisher declared (repository, package or homepage); claim this listing to verify domain control.
Freshness + modern flags	4/5	seen in a source within 7 days.
Auth declaration	2/5	Declares credential scheme: smithery_api_key.

Applicable criteria total 90 points, scaled to 100.

Responsiveness: Slow (2527 ms; bands ≤2.5 s, ≤5 s, ≤8 s, slower; penalty only).

Measured 2026-11-11.

Nine criteria, the same as the A2A readiness score, read from our daily MCP probe (initialize + tools/list) and 30-day probe history. No MCP standard defines a signed server descriptor, so that criterion is n/a and the other 90 points are scaled to 100. Grades: A>=90, B>=75, C>=60, D>=40, F<40. Display only: search order uses the quality grade.

Compared with peers

Against 53,039 reachable MCP servers in our daily snapshot (2026-11-12 06:46 UTC). Display only; it does not change search order.

Readiness: Higher than 88% of peers; This listing 87 · peer median 81
Latency: Faster than 18% of peers; This listing 664 ms · peer median 326 ms

Where it loses the most points, and how to win them back

Verified identity −5 — Claim the listing and prove control of its domain.
Now: Publisher declared (repository, package or homepage); claim this listing to verify domain control.
Auth declaration −3 — State how to authenticate (an auth scheme, or that none is needed).
Now: Declares credential scheme: smithery_api_key.
Protocol revision −2 — Support the current protocol revision.
Now: Speaks MCP 2025-11-25, 1 revision(s) behind 2026-07-28.

How many agent tools actually work · All statistics

Listed in

Directories this entry was found in.

smithery since 2026-06-04 ↗

How to connect

MCP endpoint (streamable-http)

https://server.smithery.ai/sweeppea/mcpserver/mcp

JSON-RPC initialize probe

curl -X POST https://server.smithery.ai/sweeppea/mcpserver/mcp \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}'

Homepage

https://mcpdocs.sweeppea.com

Listed at (smithery)

https://mcpdocs.sweeppea.com