npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@ahmedshaikh/db-query-mcp

v0.1.0

Published

Query SQLite database files as an MCP server — structured rows, table/schema introspection, read-only by default. No more sqlite3 shell escaping.

Readme

db-query

Query SQLite .db files and get structured rows — instead of shelling out to sqlite3 with awkward escaping and re-parsing tabular text. Read-only by default for safety.

query({ db_path: "app.db", sql: "SELECT type, count(*) n FROM events WHERE ts > ? GROUP BY type", params: [cutoff] })
→ { columns: ["type", "n"], row_count: 4, rows: [ { type: "click", n: 812 }, … ] }

Tools

  • query(db_path, sql, params?) — structured { columns, rows, row_count, truncated }. Use ? placeholders + params. Writes are blocked unless the server runs with DB_QUERY_WRITE=1.
  • tables(db_path) — every table + its columns (name/type).
  • schema(db_path, table?) — the CREATE DDL.

db_path can be omitted if the server is started with a DB_QUERY_DB default.

Safety

Read-only by default: only SELECT / EXPLAIN / read PRAGMA / WITH …-select statements run; anything mutating is rejected with a clear message. Set DB_QUERY_WRITE=1 to allow writes. Rows are capped at 1000 (with truncated flagged).

Setup

npm install   # Node 22+ (uses the built-in node:sqlite — no native build)
npm test
claude mcp add db-query -- node /abs/path/db-query/dist/server.js
# CLI: agent-db tables app.db
#      agent-db query app.db "SELECT * FROM users LIMIT 5"

Honest limits

  • SQLite only (it's what node:sqlite speaks).
  • Read-only is enforced by statement inspection, not a sandbox — robust for the common cases, but DB_QUERY_WRITE=1 is the real boundary if you need writes.
  • 1000-row cap per query (use LIMIT/WHERE to scope; truncated tells you).