"Search functionality without API key requirement" matching MCP servers:

MCP server that enables AI agents to read and write records in a live REST API generated from pasted data, with tools for listing, querying, inserting, updating, and deleting records.

Enables full-text search of macOS iMessages including link preview metadata. Works as an MCP server for Claude Desktop to search your messages locally.

Enables AI systems to perform full-text and semantic search operations over structured/unstructured data in Azure Cognitive Search, with capabilities for document indexing and management through natural language.

Monitor and manage Apache Airflow clusters through natural language queries via MCP tools: DAG inspection, task monitoring, health checks, and cluster analytics without API complexity. * Guide: https://call518.medium.com/mcp-airflow-api-a-model-context-protocol-mcp-server-for-apache-airflow-5dfdfb2

Enables searching for any text within a specified Algolia index through an MCP-compatible interface. It allows users to integrate Algolia search capabilities into their environment using an application ID and API key.

MCP server that aggregates job listings from Remotive and Arbeitnow, with local SQLite caching, application tracking, and saved searches.

Enables interaction with a comprehensive healthcare management system through FastAPI, supporting operations for patients, doctors, appointments, medical records, telemedicine, lab orders, prescriptions, insurance claims, and more with JWT authentication.

A Model Context Protocol server that searches transcript segments in a Turso database using vector similarity, allowing users to find relevant content by asking questions without generating new embeddings.

Enables read-only access to curated Datum data platform marts, including products, resources, consensus questions, and health metrics, through MCP tools such as list_products, list_questions, ask, query, and health.

Enables AI agents to safely interact with Supabase through read-only and gated-write tools, with bounded queries, allowlists, and explicit project targeting.

Downloads your entire Search Console dataset into a local SQLite database, then gives your LLM a pre-built SQL query library for every standard SEO analysis type, with context available for your LLM to perform any SQL query to answer your questions and analyse for you.

A public MCP server demonstrating how an AI agent can retrieve database schemas and manage local OpenAPI contracts via tools for CRUD operations.

Provides access to Naver Search APIs, allowing AI agents to search across multiple categories (blogs, news, books, images, shopping items, etc.) with structured responses optimized for LLM consumption.

A Model Context Protocol server that enables Claude and other MCP-compatible AI assistants to securely access and manage PI Dashboard resources including categories and charts.

Facilitates secure and type-safe interactions with both v1 and v2 of the Glide API, allowing users to manage app data and perform CRUD operations on tables via a Model Context Protocol interface.

Enables interaction with FHIR resources on Google Cloud Healthcare API through a SmartOnFHIR gateway secured by Firebase Auth, providing access to patient data, medical records, and medical research tools like PubMed.

A server that allows AI agents to interact with the Tally API to access DAO governance data, proposals, and metadata using Model Context Protocol (MCP), built with TypeScript and GraphQL.

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

Exposes Django admin's ModelAdmin as MCP tools, with identical permissions, form validation, and session authentication.

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 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 AI agents to look up Chinese laws and statutory articles fully offline from a local SQLite database, resolving a law name plus article number to verbatim text, searching articles by keyword, and retrieving a law's chapter structure and version history. It also verifies citations in bulk, checking whether each quoted provision exists word-for-word and is currently in force.

A server that enables document searching using Vertex AI with Gemini grounding, improving search results by grounding responses in private data stored in Vertex AI Datastore.

This read-only MCP Server allows you to connect to Google Search data from Claude Desktop through CData JDBC Drivers. Free (beta) read/write servers available at https://www.cdata.com/solutions/mcp

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.