Sequencer Event Poller MCP Server
Related Servers
Alternatives to Sequencer Event Poller MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityFmaintenanceEnables interaction with Instantly.ai email outreach platform through 31 tools across accounts, campaigns, leads, emails, and analytics. Supports both local and remote deployment with multi-tenant authentication.27MIT
- AlicenseAqualityAmaintenanceEnables pushing enriched leads into Instantly or Smartlead campaigns with ICP score gating, deduplication, and dry-run previews via an Apify actor.1111 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to read, search, send, reply, forward, schedule, organize, and analyze email across multiple IMAP/SMTP accounts, with provider-aware labels, drafts, templates, and bulk operations. Additional capabilities include real-time IMAP IDLE watching with AI triage, verification-code capture, calendar extraction, analytics, and optional Streamable HTTP or OAuth2 access.17 npmISC

Winnr MCP Serverofficial
AlicenseNot gradedqualityBmaintenanceEnables AI assistants to manage cold-email infrastructure through natural language, covering domain and mailbox provisioning, DNS setup, email warming, inbox and reply triage, exports, pre-warmed domain purchases, and webhooks. Supports hosted OAuth or local stdio installs with scoped read, write, and purchase permissions, plus two-step confirmation for anything that charges a card.71 PyPIMIT- AlicenseAqualityAmaintenanceEnables MCP clients to read Instantly.ai analytics and manage leads, campaigns, Unibox, sender accounts, blocklist, and webhooks, with write actions gated behind confirm prompts and configurable safety policies.4089 PyPIMIT
- AlicenseNot gradedqualityBmaintenanceEnables agents to collect posts and visible comments from specified X accounts, building unique profiles and analyzing publishing cadence, content style, and high-engagement material, with resumable pagination and CSV/JSONL export backed by PostgreSQL. Supports bounded failover across multiple configured accounts and opt-in hourly monitoring of new posts, edits, and visibility changes, reporting only when asked.24MIT
TDQS
Scored across 1 tool
There is exactly one tool, so there is no possibility of misselection between tools. Its purpose—read-only polling of sequencer events across four named vendors—is stated explicitly and unambiguously.
The single tool follows a clear verb_noun convention (poll_sequencer_events) in snake_case. There is no competing convention to conflict with, so the naming is fully predictable.
The narrow read-only polling domain can legitimately be covered by one tool, but a single tool is thin: there is no separate way to check vendor connection status, list available vendors, or page through results without doing a full billed pull. The surface is defensible but minimal.
For a read-only event ingestion tool, the surface is essentially complete: it returns per-event rows plus a run summary with per-vendor status and errors. Minor gaps remain—vendor/connection discovery and result filtering must be inferred from the summary row rather than queried directly.