Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

LINQ to DB

NUGET · LINQ2DB.CLI · SCANNED SEP 20

Inspect database schemas and execute SQL queries across multiple database providers with LINQ to DB.

Available components

+4 this week 72 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency45
Schema Quality & AI Usability71
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 819 tokens (~204/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management30
  • Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "linq2db_query" implies "execute" and declares readOnlyHint instead, contradicting what its own name says it does. See how to fix → Fail
  • An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Install

How do I install the LINQ to DB MCP server?

LINQ to DB runs locally as a NuGet package, launched with dnx linq2db.cli@6.5.0 --yes. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.

nuget · linq2db.cli

# add to Claude Code
claude mcp add linq2db-linq2db-cli -- dnx linq2db.cli@6.5.0 --yes
// .cursor/mcp.json
{
  "mcpServers": {
    "linq2db-linq2db-cli": {
      "command": "dnx",
      "args": [
        "linq2db.cli@6.5.0",
        "--yes"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "linq2db-linq2db-cli": {
      "command": "dnx",
      "args": [
        "linq2db.cli@6.5.0",
        "--yes"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add linq2db-linq2db-cli -- dnx linq2db.cli@6.5.0 --yes
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "linq2db-linq2db-cli": {
      "type": "local",
      "command": [
        "dnx",
        "linq2db.cli@6.5.0",
        "--yes"
      ],
      "enabled": true
    }
  }
}
# ~/.hermes/config.yaml
mcp_servers:
  linq2db-linq2db-cli:
    command: "dnx"
    args: ["linq2db.cli@6.5.0", "--yes"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "linq2db-linq2db-cli": {
      "Transport": "stdio",
      "Command": "dnx",
      "Arguments": [
        "linq2db.cli@6.5.0",
        "--yes"
      ]
    }
  }
}
// mcp.json
{
  "mcpServers": {
    "linq2db-linq2db-cli": {
      "command": "dnx",
      "args": [
        "linq2db.cli@6.5.0",
        "--yes"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 19 Sept 26 +4
    • Stability: unverified → 0.27 functional
  • 11 Sept 26 68

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 20 Sept 2026 · Analysed nuget/linq2db.cli@6.5.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem nuget
Reason Signature present, unreadable

Background: How many MCP packages publish verified provenance →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 4 exposed · ~721 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
linq2db_info ~94

Returns non-secret linq2db MCP query configuration information. Call this tool first when available profiles, providers, SQL dialects, output defaults, row limits, or execute availability are unknown. Use linq2db_schema to inspect database objects. Use linq2db_skill for the full usage guide. This tool never returns connection strings, passwords, provider assembly paths, impersonation credentials, or environment variable values.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

linq2db_query ~236

Executes one read-only SQL statement using a configured linq2db profile. Call linq2db_info first when the profile or SQL dialect is unknown. Call linq2db_schema when database objects are unknown and call linq2db_skill for detailed guidance. Multiple statements and SQL that cannot be classified as read-only are rejected. Do not use it for write-capable SQL.

NameTypeReqDescription
maxRowsinteger|nullOptional row limit. Prefer a small value for exploration; use 0 only when the full result set is explicitly needed.
outputstring|nullOptional output: json or json-table. Prefer json-table for metadata, duplicate column names, expressions, or joins; use json for object-shaped rows with unique names.
profilestring|nullOptional profile returned by linq2db_info or explicitly provided by the user. If omitted, the server startup/default profile is used. Requires server startup with --config.
sqlstringyesOne provider-appropriate read-only SQL statement. Prefer SELECT or WITH. Use explicit aliases for expressions and joins because json output requires unique column names.

No output schema declared.

No examples provided.

linq2db_schema ~330

Returns provider-independent database schema metadata for the selected linq2db query/MCP profile. Use this tool before generating SQL when table names, column names, keys, relationships, schemas, or catalogs are unknown. It reads metadata only, does not read table data or execute SQL, and does not return secrets. Procedures and functions are not supported.

NameTypeReqDescription
defaultSchemastring|nullDefault schema name.
detailLevelstring|nullSchema detail level. Allowed values: full, names. Use names for compact object discovery, then request full metadata with filters.
filterCatalogsarray|nullOptional catalog name filters. Exact names only.
filterSchemasarray|nullOptional schema name filters. Exact names only.
filterTablesarray|nullOptional table or view name filters. Matches name, schema.name, or catalog.schema.name. Use regex: or rx: prefix for regular expressions.
generateChar1AsStringboolean|nullMap char(1) metadata to string instead of char.
getForeignKeysboolean|nullRead foreign key metadata.
getTablesboolean|nullRead table and view metadata.
ignoreSystemHistoryTablesboolean|nullIgnore SQL Server temporal history tables when provider supports it.
preferProviderSpecificTypesboolean|nullPrefer provider-specific .NET types in schema metadata.
profilestring|nullOptional profile returned by linq2db_info or explicitly provided by the user. If omitted, the server startup/default profile is used. Requires server startup with --config.

No output schema declared.

No examples provided.

linq2db_skill ~61

Returns the full embedded linq2db CLI agent skill as Markdown. Use it for detailed configuration, provider loading, SQL safety, output, timeout, impersonation, and workflow guidance. This documentation-only tool does not access a database or return secrets.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Common questions

What is the LINQ to DB MCP server?

LINQ to DB is an MCP server listed in the public MCP registry as io.github.linq2db/linq2db.cli. Inspect database schemas and execute SQL queries across multiple database providers with LINQ to DB. This page covers its NuGet package (linq2db.cli).

Is the LINQ to DB MCP server safe to use?

LINQ to DB scores 72 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the LINQ to DB MCP server expose?

LINQ to DB exposes 4 tools: linq2db_info, linq2db_query, linq2db_skill, linq2db_schema. Their descriptions and schemas cost roughly 721 tokens of context every time the server is loaded.

Is the LINQ to DB MCP server still maintained?

LINQ to DB is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the LINQ to DB MCP server under?

LINQ to DB declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.