Rebase
NPM · @REBASEPRO/MCP
Schema, database, document, user and dev-server tools for a Rebase backend project.
Available components
Last scanned (17 minutes ago)
Scores higher than 97% of npm servers
Category Databases
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 32 of 100 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to rebasepro/rebase). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 0 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability79
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 3599 tokens (~67/item across 53 items; 53 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage99
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 97% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 6 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "rebase_db_branch_delete" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 53 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 0
- Package version: 0.25.1 → 0.28.0 functional
- 3 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- Stability: 0.97 → pass security
- 2 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- Stability: pass → 0.97 functional
- Package version: 0.26.0 → 0.27.0 functional
- 29 Oct 26 0
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Schema quality: 47 → 62 ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Package version: 0.25.1 → 0.26.0 functional
- 17 Oct 26 +2
- Stability: 0.83 → pass security
- 16 Oct 26 −2
- Stability: pass → 0.83 functional
- 15 Oct 26 +45
- Injection markers: unverified → pass ▲ security
- Stability: unverified → pass ▲ security
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Package version: 0.23.0 → 0.25.1 functional
- 14 Oct 26 −44
- Stability: 0.93 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- Package version: 0.23.0 → 0.25.1 functional
- Package version: 0.23.0 → 0.25.0 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/@rebasepro/mcp@0.28.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | rebasepro/rebase |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/rebasepro/rebase/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3693120438 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:8337e3f1b1f826e2d42f6298b58eeab6c2e1ca9b353547515d60739842fa9817205b530b5ca5251e2a4ef6456f50a1cae9fd050c4cadd75f4d209cf69 |
Background: How many MCP packages publish verified provenance →
Dependencies 100 packages
| Packages resolved | 100 |
|---|---|
| Stale | 32 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
storage_list_objects ~76
List files/objects stored in Rebase storage.
| Name | Type | Req | Description |
|---|---|---|---|
| bucket | string | – | Filter by storage bucket name |
| maxResults | number | – | Maximum number of results to return (default 50) |
| pageToken | string | – | Pagination token |
| prefix | string | – | Filter objects by prefix (e.g. 'images/') |
No output schema declared.
No examples provided.
update_document ~46
Update an existing document in a Rebase collection.
| Name | Type | Req | Description |
|---|---|---|---|
| collection | string | yes | Collection slug |
| data | object | yes | Fields to update |
| id | string | yes | Document ID |
No output schema declared.
No examples provided.
update_user ~51
Update an existing user (email, display name, roles).
| Name | Type | Req | Description |
|---|---|---|---|
| displayName | string | – | – |
| string | – | – | |
| roles | array | – | – |
| uid | string | yes | User UID |
No output schema declared.
No examples provided.
How do I install the Rebase MCP server?
Rebase runs locally as an npm package, launched with npx -y @rebasepro/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @rebasepro/mcp
claude mcp add rebasepro-rebase -- npx -y @rebasepro/mcp
What is the Rebase MCP server?
Rebase is an MCP server listed in the public MCP registry as io.github.rebasepro/rebase. Schema, database, document, user and dev-server tools for a Rebase backend project. This page covers its npm package (@rebasepro/mcp).
Is the Rebase MCP server safe to use?
Rebase scores 94 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Rebase MCP server expose?
Rebase exposes 53 tools: rebase_schema_generate, rebase_db_push, rebase_schema_introspect, rebase_db_generate, rebase_db_migrate, and 48 more. Their descriptions and schemas cost roughly 3,599 tokens of context every time the server is loaded.
Is the Rebase MCP server still maintained?
Rebase is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Rebase MCP server under?
Rebase declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.