"A search query containing special characters and SQL injection-like encoding" matching MCP servers:

A general-purpose MCP server that lets AI work with multiple databases within clear boundaries.

Analyzes SQL queries for performance issues, provides optimization suggestions with automated rewriting, and recommends indexes across multiple database dialects (PostgreSQL, MySQL, Oracle, SQL Server).

MCP server for answering questions about official statistics from a single publication URL, with tools to check query scope, retrieve overview, text, data files, and search.

Enables AI assistants to safely explore and query MySQL, MariaDB, PostgreSQL, SQLite and StarRocks databases through read-only tools for schema listing, table description, schema search, row sampling, query execution, and plan explanation. Enforces least-privilege accounts, engine-level read-only sessions with timeouts, parsed SQL guardrails, and column masking so runaway or unsafe queries are refused.

An MCP server for identifying SQL injection vulnerabilities in web applications using various techniques like error-based, time-based, and union-based scanning. It supports bulk URL processing, WAF bypass strategies, and authenticated testing across multiple database systems.

An extensible read-only MCP server for SQL databases, enabling schema exploration and safe SELECT queries via tools like list_schemas, list_tables, describe_table, and execute_query.

Enables read-only interaction with SQL databases through MCP, providing database metadata exploration, sample data retrieval, and secure query execution. Supports MySQL with multiple transport options and built-in security features including SQL injection protection and data sanitization.

Enables natural-language querying and analysis of an e-commerce SQLite database via MCP, with read-only SQL execution, table inspection, and AI-generated answers.

Runs SQL statements in memory against real PostgreSQL 18 and SQLite 3.49 engines after loading your schema and sample rows, returning each statement's own verdict: errors with line, column, and hints, constraint violations, or the resulting rows. It also compares both dialects to expose portability differences, all with no database server, network, or API key.

Enables AI assistants to query SQLite databases using plain language, with strict read-only enforcement and column-level access control to prevent damage or unauthorized data reads.

Lightweight TypeScript MCP server for Airtable base discovery, table/view queries, record CRUD, and validated filterByFormula construction.

A read-only MCP server for SQL Server and PostgreSQL that enables exploring and querying databases (schemas, tables, views, procedures, indexes, foreign keys) and running arbitrary SELECT queries.

An MCP server that connects LLMs to SQL databases for development assistance, enabling query execution, schema exploration, and data manipulation while providing safety controls against destructive operations.

Enables Azure SQL Database performance and administration through typed execution, query benchmarking, and managed DBA operations.

WAF for AI agents — block prompt injection before it reaches the LLM.

Enables AI assistants to query PostgreSQL, MySQL, SQL Server, Oracle, and MongoDB databases through MCP with read-only, audited access.

A Model Context Protocol server that provides AI assistants with comprehensive access to SQL databases, enabling schema inspection, query execution, and database operations with enterprise-grade security.

Enables interaction with Microsoft SQL Server databases using both SQL Server and Windows Authentication. It supports flexible connection configurations, including read-only modes and encrypted communication for secure data management.

MCP server for querying H3Yun SQL data, enabling AI to execute read-only SQL queries and troubleshoot H3Yun business issues.

Enables filtered, read-only querying of a Notion audit trail and action queue as four native tools (filtered lists and single-row lookups), with enum parameters validated against the live database schema and errors that report allowed values. It never writes to Notion, returns flat JSON rows, and keeps the integration token server-side.