"Lottery games and results" matching MCP servers:

Relays a result screenshot to Slack so you can review a coding agent's output without opening the app.

Official MCP server for Scorezilla (leaderboards for games). Your AI coding assistant can bootstrap a leaderboard, inspect games and boards, read top-N standings, and paste ready-to-run SDK integration code — without leaving the editor.

Social layer for AI coding — DMs, presence, discovery, and multiplayer games between developers. 68 tools including messaging, presence, memory, and 27 multiplayer games.

Local MCP server for the Spawn Games agent API, enabling LLMs to manage game projects, push updates, and interact with live games via a Playwright Chromium client.

Enables AI assistants to manage TapTap minigames and H5 games, including leaderboards, sharing, multiplayer, cloud saves, and game DC data query, with zero-config OAuth 2.0 authentication.

Validates a built HTML5 game against CrazyGames portal rules — build checks, an emulated SDK v3 session, and frame/layout audits — returning dense JSON lists of failures, warnings and rules it could not exercise instead of screenshots or ad-hoc Playwright scripts. It emulates the portal entirely in-process (no server or port) using the game's own Playwright/Chromium, with a small per-game scenario file driving gameplay steps.

Monitor failing GitHub Actions workflows, auto-fix them with OpenCode, and retry the run — driven by a workflow_run webhook, coordinated through an MCP server.

Enables AI agents to break down complex tasks into manageable pieces using a structured JSON format with task tracking, context preservation, and progress monitoring capabilities.

A stdio-based MCP server that enables users to play and manage Minesweeper games through a Rails 8 REST API. It provides tools to start games, track states, and perform actions like opening cells and flagging mines.

Game modules, project scaffold and SDK skills for building cross-platform and web3 games on iDos Games. Read-only local server: npx -y @idosgames/mcp.

Enables building, publishing, and improving PWA games from your editor by scaffolding games, updating files, and auto-deploying to a live URL.

Connect AI agents to your test results, insights, and targets. Query test runs, failures, flaky tests, and regressions across frameworks including Playwright, Jest, Pytest, Cypress and more.

Integrates ForgeaX game development into DeepSeek Harness by wiring the @forgeax/game MCP server, bundled Skills, and a workspace guard into DSH sessions.

Enables LLM clients such as Cursor and Claude to discover and use generated REST services through MCP tools for create, update, and delete actions and MCP resources for list and get-by-id context. Services generated in one command are exposed simultaneously as REST endpoints and MCP tools and resources.

Enables AI assistants to interact with generated REST APIs by discovering and using CRUD tools and read-only data resources.

Enables AI assistants to discover and invoke CRUD tools and read-only resources over the Model Context Protocol for generated API services.

Enables AI assistants to interact directly with generated REST APIs by exposing CRUD operations as MCP tools and read-only data as resources.

Exposes generated CRUD services to LLM clients over the Model Context Protocol, providing tools for create, update, and delete actions plus read-only resources for listing and fetching records by id. It lets assistants like Claude, ChatGPT, and Cursor discover and manipulate the same data served by the project's REST endpoints without any extra glue code.

Exposes every generated CRUD service to LLM clients such as Claude, ChatGPT, or Cursor through discoverable MCP tools for create, update, and list actions plus read-only resources, so models can query and manipulate data without raw HTTP calls. It runs alongside the same codebase's REST endpoints, letting clients and AI share one data layer.

Enables LLMs to discover and invoke generated CRUD operations as MCP tools and read data through MCP resources, alongside standard REST endpoints, using one codebase.

Enables LLMs to discover and invoke generated CRUD tools and resources, allowing AI assistants to interact with the same data exposed by the REST API. Supports MCP clients such as Cursor and Claude over HTTP.

Enables LLMs to discover and invoke generated API actions as MCP tools and read context through MCP resources for list and get-by-id operations. It provides HTTP-based MCP access for clients such as Cursor and Claude without extra glue code.

Enables LLMs to interact directly with generated REST APIs by exposing CRUD actions as MCP tools and read-only data as MCP resources.

Enables AI assistants to publish and manage HTML5 browser games, giving each game its own address and catalogue page with leaderboards, cloud saves, player clips, daily stats, versioning, and rollback.

Enables LLMs and MCP clients to discover and use generated CRUD services through MCP tools and resources, exposing actions like create, update, delete, and read-only list/get access alongside REST endpoints.

Enables AI assistants to discover and invoke generated CRUD tools and read-only resources, letting them interact directly with REST-backed services built on Express, Mongoose, or Sequelize.

Enables AI agents to query the deno.land/x third-party module registry for module metadata, version lists, individual version details, search results, and best-effort dependency information. It provides keyless access to these registry lookups through MCP tools.

Enables LLMs and AI assistants to discover and use tools and resources for CRUD operations on generated services, providing direct interaction with the same data exposed by REST endpoints.

. A good description should be concise and describe what the server enables users to do, e.g. * Enables to interact with WordPress sites...' Then a huge block? Actually the user message includes the README content inside tags, then after the readme, there is a large block of text starting with '{

Enables LLMs to discover and invoke CRUD tools and read-only resources for generated services, allowing direct interaction with the same data exposed by the REST API.