"Lottery games and results" matching MCP servers:

Search the fastest-growing US horse boarding directory: 6,000 facilities and 3,800 trainers across 48 states, plus boarding price data by state.

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.

Acts as an anonymizing proxy between AI agents and databases, detecting PII and replacing it with realistic fake data so agents never see real data.

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 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 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.

Enables AI assistants to interact with Databricks workspaces, running SQL queries, managing jobs, and exploring schemas via the Model Context Protocol.

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.

Enables LLMs to interact with generated REST API services by exposing MCP tools and resources for CRUD operations, listing, and retrieval. It lets AI clients discover and call create, update, delete, list, and get-by-id actions against the same data available over REST.

Exposes every generated Express service to LLM clients over HTTP as MCP tools (create, update, delete actions) and resources (list and get-by-id context), so AI assistants can discover and manipulate application data without raw HTTP calls. This lets teams run a single codebase that serves both traditional REST clients and AI agents such as Cursor or Claude.

Enables LLMs to interact with generated CRUD services through MCP tools and resources, so they can create, update, list, and fetch records via a standard protocol. It also provides REST API access from the same codebase for traditional clients.

Enables LLM clients such as Claude, ChatGPT, and Cursor to discover and act on generated CRUD services over HTTP through tools like create, update, list, and delete, plus read-only resources for listing and fetching records by ID, with no extra glue code.

Enables LLMs to discover and invoke generated API operations as MCP tools and resources, supporting create, update, list, and get-by-id actions over the same data exposed by the REST API.

Enables LLMs to discover and use generated REST API services as Model Context Protocol tools and resources, supporting CRUD actions and read-only data access without custom glue code.

Enables LLMs to interact directly with generated REST services by discovering and invoking CRUD tools and reading exposed resources for list and get-by-id data.

It enables AI assistants to discover and invoke CRUD operations as MCP tools and read application data through MCP resources, allowing natural-language interaction with the generated backend.

MCP server for querying student information, validating result data, and analyzing student results from a local database.

It enables LLMs to interact with generated REST APIs by exposing CRUD operations as MCP tools and readable records as MCP resources. This lets AI clients discover and manage API data through the Model Context Protocol.

Enables LLMs to discover and invoke CRUD operations and read-only data resources for generated services through the Model Context Protocol, alongside traditional REST endpoints.

An MCP server that provides targeted PostgreSQL schema access to AI agents, retrieving only relevant tables for a question and enforcing read-only access through multiple layers.

A read-only DuckDB MCP server offering context-efficient analytics tools (list_datasets, describe_table, profile_column, explain, query) with a semantic layer for business rules, security guards, and disclosed truncation to help LLMs produce correct answers while minimizing token usage.

Enables querying logs and metrics with plain SQL from any MCP client via pooml's read-only query API.