LiteScope runs on your own machine — the client starts it, so there is no endpoint to ping. 35 installs a week from npm. Last commit 14 Jul 2026.
Operations toolchain for SQLite, Cloudflare D1 & Turso: inspect, diff, migrate, monitor & repair.
We read the source, 9 h ago · rules 3dff92dd89df
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
postinstall: node scripts/install.js
const child = spawn(bin, process.argv.slice(2), { stdio: "inherit" });
Found in continuous integration, deployment or infrastructure files, or in a neighbouring package of the same monorepo. None of this is installed when you add the server: it describes how the project is built and released. We list it because a leaked key in a build pipeline is still a real problem, but it is not something this server does on your machine.
path := filepath.Join(dir, name)
$("#app").innerHTML = html;
if strings.Contains(webhookURL, "hooks.slack.com") || strings.Contains(webhookURL, "slack") {
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add litescope -- npx -y litescope
{
"mcpServers": {
"litescope": {
"args": [
"-y",
"litescope"
],
"command": "npx"
}
}
}
[mcp_servers.litescope]
command = "npx"
args = ["-y", "litescope"]
{
"mcpServers": {
"litescope": {
"args": [
"-y",
"litescope"
],
"command": "npx"
}
}
}
{
"mcpServers": {
"litescope": {
"args": [
"-y",
"litescope"
],
"command": "npx"
}
}
}
This one needs environment variables set before it will start:
CLOUDFLARE_API_TOKEN (Cloudflare API token — only needed for Cloudflare D1 sources (d1://...)), CLOUDFLARE_ACCOUNT_ID (Cloudflare account ID — only needed for Cloudflare D1 sources).
The author declared them in the registry entry; get the values from the project itself.
MCP server for local SQLite database operations
Database management — query, schema inspection, migrations for PostgreSQL, MySQL, SQLite.
Lints PostgreSQL migrations for dangerous locking operations and suggests safe rewrites.
MCP server for Microsoft SQL Server — read and data write operations, no DDL
Evidence-grounded agent memory with mandatory provenance, on local SQLite or Cloudflare D1
Safe, audited PostgreSQL operations for AI agents: queries, migrations, EXPLAIN, containers
Persistent memory + decision tracking for Claude across sessions. Local SQLite, no cloud.
SQL pipeline observability and DBT integration monitor.
Answers built from our own checks of this server.