Supported Games
Real-time multiplayer server discovery
Officially Supported Titles
ServerPulse natively queries over 40 active multiplayer ecosystems using standardized UDP/TCP handshake implementations.
Valve Source Engine
Queries Counter-Strike 2, Team Fortress 2, Garry's Mod, and Rust via A2S_INFO on ports 27015-27030. Returns player counts, map cycles, and workshop addon IDs.
Minecraft Java Edition
Implements the full MC Server List Ping protocol (versions 1.7.10 through 1.21.x). Fetches MOTD, favicon, player lists, and forge/fabric modpack metadata.
ARK: Survival Ascended
Uses Steam Query with custom ARK payload parsing. Extracts tribe limits, day/night cycle settings, and custom mutation multipliers from master servers.
Unturned
Direct UDP broadcast listening on port 27016. Decodes region locks, gamemode flags, and custom difficulty profiles for regional browser filtering.
Query Protocol Specifications
Every supported title relies on deterministic packet structures to minimize latency and prevent false-positive server discoveries.
ServerPulse routes requests through dedicated query nodes that respect TTL and rate-limit thresholds. Source engine games use the standard A2S_INFO challenge-response flow, while Minecraft relies on TCP handshake version negotiation. Each protocol handler enforces a 200ms timeout window and automatically retries fragmented packets up to three times. Response payloads are sanitized against malformed UTF-8 sequences and stripped of executable script tags before rendering in the browser UI.
Custom protocol handlers compile to WebAssembly and run in isolated sandbox environments. This ensures that a malformed packet from a legacy DayZ server never impacts the query throughput for modern titles like Palworld or Conan Exiles.
Community Protocol Plugin System
Missing a favorite title? Contribute a query adapter using our open-source plugin framework.
Developers can author new protocol handlers using TypeScript or Rust. The @serverpulse/protocol-sdk provides pre-built parsers for common UDP/TCP structures, challenge token management, and regional DNS resolution. Once submitted, community plugins undergo automated validation in our staging cluster before merging into the public registry.
Accepted adapters receive automatic CDN distribution and are featured in the main browser dropdown within 48 hours of approval. Contributors retain full attribution and can opt into revenue sharing from premium API tiers.