WhoDB — Watchlist | MCP100 Index

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Follow database-driver and read/write tool changes because database support is broad

Reviewed Oct 5, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

Exploring and querying databases through a local web interface with optional AI assistance.

What we know

WhoDB is a database exploration application that can run locally and connect to supported databases, with optional AI features.

Maintenance / activity evidence

Observed Oct 5, 2026 (UTC)chore: update downloads badge

Tracking evidence observed Oct 5, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: high.

Activity source · commits ↗Activity source · releases ↗

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Can access data according to the configured database account. Writes: Depends on database features and configured permissions.
Uses the credentials required by connected databases/providers.
Sensitive access: Database contents, Database credentials

Database access can expose sensitive structured data and may allow writes depending on account privileges.

Security source · repository notice ↗Security source · policy file ↗

Full authority, access and evidence limits are available in Review context and Access & risk.

Popularity

5,028 repository stars · 996 package downloads / 30 days

Stars observed Oct 6, 2026. Downloads observed Oct 6, 2026.

All limitations / Review context

Which database engines and operation boundaries are documented for the MCP server?

The bounded assessment reviewed the official README, repository notices, security policy path, and security page for known material public-tracking blockers. No such blocker was identified. This is a public-tracking assessment, not an installation safety certification.

Database access can expose sensitive structured data and may allow writes depending on account privileges.
Can access data according to the configured database account.
Uses the credentials required by connected databases/providers.
Database content is processed by the local application; optional AI providers may receive selected context.
Reviewed write actions: Depends on database features and configured permissions
Sensitive access: Database contents, Database credentials
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
No independent runtime, installation, or comprehensive security audit was performed.
No installation, runtime, client matrix, or complete tool-contract audit was performed in this review.
Database authentication and permissions depend on each configured connection.
This is primarily a host/application rather than a standalone MCP server.

Original activity observations

2026-10-05T03:43:50Z: chore: update downloads badge

Technical identity

github.com/clidey/whodb

Exact implementation source: https://github.com/clidey/whodb ↗
Reviewed resource type: Host
Repository identity: clidey/whodb
Package identity: npm:@clidey/whodb
Service endpoint: http://localhost:8080

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 5, 2026 · Latest source observation Oct 6, 2026

GitHub repository ↗
clidey/whodb
Recorded repository material and project history.
Package registry ↗
@clidey/whodb
Recorded package identity, distribution or download evidence.
Includes references whose attribution is not established.

Setup · Watchlist

Host / Desktop app setup

Publisher instructions.

Source evidence observed Oct 13, 2026.

Additional setup details required — see the specific gaps below.

Download / install
Publisher instructions
Publisher-specific setup path. Follow prerequisites, then register or connect to your MCP host.
publisher documented install or connect · Publisher instructions · Review before use
```
npm install -g @clidey/whodb
whodb mcp serve
```
Configure application / integrations
MCP100 setup guide
WhoDB CLI has its own MCP server mode `whodb mcp serve`; register command `whodb` and args `["mcp", "serve"]` in your host.
Advanced configuration · generic mcpServers json · MCP100 composed guide
generic mcpServers json · MCP100 composed guide
{ "mcpServers": { "whodb": { "command": "whodb", "args": [ "mcp", "serve" ] } } }
Check connection
Suggested check
Verify `whodb --help`, then confirm the client discovers WhoDB MCP tools.
Disconnect / uninstall / revoke
MCP100 setup guide
Remove WhoDB MCP entry from the client; `npm uninstall -g @clidey/whodb` only if you also wish to uninstall the CLI.

Official Documentation & Sources

What it does

WhoDB is a database exploration application that can run locally and connect to supported databases, with optional AI features.

Capability: Data & Databases
Resource type: Host
Industry: Software & Technology
Best fit: Exploring and querying databases through a local web interface with optional AI assistance.

Representative uses

Browse database schemas
Inspect tables and records
Query supported databases
Use AI-assisted database exploration

Limitations

Database authentication and permissions depend on each configured connection.
This is primarily a host/application rather than a standalone MCP server.

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: Uses the credentials required by connected databases/providers.
Permissions: Can access data according to the configured database account.
Data handling: Database content is processed by the local application; optional AI providers may receive selected context.
Cost: unknown
Risk and cautions: Database access can expose sensitive structured data and may allow writes depending on account privileges.

Access scope and cautions

Write actions: Depends on database features and configured permissions
Sensitive access: Database contents Database credentials
Risk level: high

FAQ

Based on reviewed evidence as of 2026-10-06. Watchlist tracking is not a recommendation or a security certification.

Which tasks are documented for this implementation?

The reviewed tasks include: Browse database schemas; Inspect tables and records; Query supported databases; Use AI-assisted database exploration.

What setup and authentication are documented?

Recorded installation/entrypoint step: docker run --rm -it -p 8080:8080 clidey/whodb. Recorded endpoint: http://localhost:8080. Recorded transport: other. Prerequisites: Docker or supported local installation. These are the documented setup details, not a claim that installation or client compatibility was independently tested. Authentication: Database/provider-specific.

Can it modify data or perform write operations?

Documented write actions include: Depends on database features and configured permissions. Recorded permission boundary: Can access data according to the configured database account.

What data-handling boundary should I consider?

Database content is processed by the local application; optional AI providers may receive selected context. Recorded sensitive-access context: Database contents; Database credentials.

What limitations and risks should I check before use?

Database access can expose sensitive structured data and may allow writes depending on account privileges. Database authentication and permissions depend on each configured connection. This is primarily a host/application rather than a standalone MCP server. No independent runtime, installation, or comprehensive security audit was performed.

Is this an official MCP?

Clidey is listed as First-party MCP in MCP100’s current evidence.