Coremcp: MCP server, setup and security

What Coremcp does

According to its repository: “Tunnel-based bridge connecting local and on-premise databases (such as MSSQL) to LLMs, with AST-based query safety and PII masking.”

The Model Context Protocol (MCP) is a standard plug between an AI agent and an outside service: once the server is connected, its tools show up in the agent, which decides when to call them. Coremcp is listed under Databases, a category of 138 servers in the directory, where it ranks #122 by stars.

Topics declared by the repository: database-bridge, golang, legacy-systems, llm-ops, mssql.

Installing and connecting Coremcp

No package or remote server is declared in the official MCP registry: you install it from source, following the repository README.

It works with any MCP-compatible client (Claude Desktop, Claude Code, Cursor, VS Code, Codex and most recent agents). You add one entry to the client's MCP configuration: server name, start command or URL, environment variables. Project language: Go.

Security: what to check

Connecting an MCP server means installing software that talks straight to your agent: it runs with your rights and the model trusts its tool descriptions. The risk therefore depends on what it can touch and how far its code can be trusted.

None of the risk signals we track (system access, secrets, missing licence, abandonment) applies to Coremcp. That does not replace reading the code.

Good practice: grant only the rights needed (least privilege), require human approval for irreversible actions, and run the AI agent security check.

Project activity and maintenance

Created on February 11, 2026, the CoreBaseHQ/coremcp repository has 11 stars and 2 forks, with 1 open issues. It has more stars than 28% of the servers in the directory. Last change 3 months ago.

Stars measure attention, not quality: a recent, heavily promoted project can collect them fast, while a useful but niche server will have few.