Package Registry MCP vs Rebase
A side-by-side look at the Package Registry MCP and Rebase MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Package Registry MCP for databases work as a local process; choose Rebase for databases as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Package Registry MCP when
- You need dedicated capabilities in the Databases domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
get-cargo-package-details, search-cargo-packages, list-cargo-package-versions.
Choose Rebase when
- You need dedicated capabilities in the Databases domain.
- You prefer a local stdio subprocess transport.
- You want tools like
rebase_schema_generate, rebase_db_push, rebase_schema_introspect.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Databases | Databases |
| Quality signal | 64/100 · Good | 65/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | No auth required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 39 | 23 |
| Directory activity | 4 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 16 | 42 |
| Full listing | View Package Registry MCP | View Rebase |
Tools & capabilities
Package Registry MCP tools 16
get-cargo-package-detailsGet detailed information about a specific Cargo packagesearch-cargo-packagesSearch the Cargo registry for packageslist-cargo-package-versionsList all versions of a specific Cargo packageget-github-advisoryGet detailed information about a specific GitHub Security Advisory by its GHSA ID (e.g., GHSA-grv7-fg5c-xmjg).search-github-advisoriesSearch the GitHub Security Advisory Database for vulnerabilities. Filter by ecosystem (npm, pip, maven, etc.), severity, type, or CVE ID.get-package-advisoriesGet all security advisories affecting a specific package. Use this to check if a package like "braces" or "lodash" has known vulnerabilities.get-golang-package-detailsGet detailed information about a specific Go module/packagelist-golang-package-versionsList all versions of a specific Go module/packageget-npm-package-detailsGet detailed information about a specific NPM packagesearch-npm-packagesSearch the NPM registry for packageslist-npm-package-versionsList all versions of a specific NPM packageget-nuget-package-detailsGet detailed information about a specific NuGet package- +4 more on the listing page
Rebase tools 42
rebase_schema_generateGenerate Drizzle schema from Rebase TypeScript collection definitions. Run this after adding or modifying collection files.rebase_db_pushApply the current Drizzle schema directly to the database (development shortcut, skips migration files). Refuses changes that destroy data — use rebase_schema_plan first, then ask the human to run `rebase db push --allow-destructive`.rebase_schema_introspectIntrospect the live database and generate Rebase collection definitions from existing tables.rebase_db_generateGenerate SQL migration files from schema changes (compares current Drizzle schema against the last entity).rebase_db_migrateRun all pending SQL migrations against the database.rebase_generate_sdkGenerate a fully-typed JavaScript/TypeScript SDK from collection definitions.rebase_doctorDetect schema drift between collection definitions, generated Drizzle schema, and the live PostgreSQL database.rebase_db_branch_createCreate a new database branch (Admins only).rebase_db_branch_listList all database branches (Admins only).rebase_db_branch_deleteDelete an existing database branch (Admins only).rebase_db_branch_infoShow information and status for a database branch (Admins only).rebase_db_branch_switchPoint this checkout at a database branch, or back at the main database (Admins only). With no name, reports which branch is active. Writes a local pointer, never `.env`.- +30 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Package Registry MCP
{
"mcpServers": {
"artmann-package-registry-mcp": {
"command": "npx",
"args": [
"-y",
"package-registry-mcp"
]
}
}
}
Rebase
{
"mcpServers": {
"rebase": {
"command": "npx",
"args": [
"-y",
"@rebasepro/mcp"
]
}
}
}
Frequently asked questions
Package Registry MCP is categorized under Databases and uses a local stdio subprocess. Rebase belongs to Databases and uses a local stdio subprocess. Pick Package Registry MCP for databases work and Rebase for databases.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Package Registry MCP is listed as free. Auth: no auth required. Rebase has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add artmann-package-registry-mcp and rebase as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Package Registry MCP has a quality signal of 64/100 (Good) with 4 views, 0 installs and 39 GitHub stars. Rebase has 65/100 (Great) with 1 views, 0 installs and 23 GitHub stars.