io.github.linq2db/linq2db.cli

MCPcommunity
v6.5.0io.github.linq2dbUnknownUpdated 24d agoGitHub

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

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
3kGitHub stars
479Forks
24d agoLast update
Package
Authorio.github.linq2db
LicenseUnknown
Version6.5.0
Sourcemcp-registry
GitHublinq2db/linq2db
SBOMCycloneDX 1.6 ↓
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/30
→ Publisher: run `forge publish` from the repo to claim ownership
—Domain verification+0/10
→ Not currently available for this listing type — the domain-verification check only runs for npm-backed packages today, so this row cannot be earned here yet regardless of what's hosted at the domain.
✓Prompt-injection scan · clean+30/30
✓Obfuscation / exfil scan · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
DependenciesNot audited
Tool surface—
Security scan✓ CleanvHEAD · 23d agoHow well does this scan work?
EvalsNone
IndexedSep 11, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

Source not readable23d ago

The repository archive could not be read at scan time (tarball exceeds size cap), so no tool declarations could be extracted from it. Nothing here is a statement about what this exposes.

About

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

Keywords
mcp
Alternatives
Comparing tool surfaces…

No dependency coverage

This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.