io.github.selvatuple/revibe-mcp
NPM · REVIBE-MCP · SCANNED AUG 3
Analyze any codebase — get architecture, file roles, execution flows, and agent context.
Available components
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 →
Supply Chain Security87
- No malware found by supply-chain analysis.Pass
- Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 139 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability81
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 507 tokens (~84/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · revibe-mcp
claude mcp add selvatuple-revibe-mcp -- npx -y revibe-mcp
codex mcp add selvatuple-revibe-mcp -- npx -y revibe-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"selvatuple-revibe-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"revibe-mcp"
],
"enabled": true
}
}
} openclaw mcp add selvatuple-revibe-mcp --command npx --arg -y --arg revibe-mcp
mcp_servers:
selvatuple-revibe-mcp:
command: "npx"
args: ["-y", "revibe-mcp"] {
"mcpServers": {
"selvatuple-revibe-mcp": {
"command": "npx",
"args": [
"-y",
"revibe-mcp"
]
}
}
} 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.
- 3 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Aug 26 +48
- Provenance: unverified → fail ▼ security
- Install scripts: unverified → pass ▲ security
- Known CVEs: unverified → partial ▲ security
- Malware scan: unverified → pass ▲ security
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: unverified → excellent ▲ functional
- Dependency health: unverified → partial ▲ functional
- Stability: unverified → 0.20 ▲ functional
- Maintenance: unverified → pass ▲ functional
- MCP protocol: unverified → pass ▲ functional
- License: unverified → pass ▲ functional
- First check of Schema quality: unverified functional
- Licence: MIT functional
- 31 Jul 26 −25
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 46
First indexed and scored.
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 3 Aug 2026 · Analysed npm/[email protected]
Provenance none
Ecosystem: npm · Outcome: none
Dependencies 95 packages
95 packages in the resolved dependency tree · 95 deprecated · 29 stale.
The dependency tree was only partially resolved, so these counts may be incomplete.
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.
analyze_repo ~110
Submit a GitHub repository for Revibe analysis. Analyzes architecture, file roles, execution flows, system design Q&A, and more. If no URL is provided, auto-detects from the current git remote. Analysis takes 3-7 minutes for most repos.
| Name | Type | Req | Description |
|---|---|---|---|
| github_url | string | — | GitHub repository URL (e.g. https://github.com/owner/repo). Auto-detected if empty. |
| reanalyze | boolean | — | Force re-analysis even if already analyzed. |
No output schema declared.
No examples provided.
check_status ~33
Check the status of a Revibe analysis job.
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | yes | The job ID returned from analyze_repo. |
No output schema declared.
No examples provided.
get_agent_context ~79
Get the full agent context JSON for a completed analysis. This is a structured format optimized for AI agents, containing file index, dependency graph, architecture layers, call chains, constraints, design decisions, and database schema. Save the output to agent_context.json for persistent codebase understanding.
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | yes | The job ID from analyze_repo. |
No output schema declared.
No examples provided.
get_section ~189
Get a specific analysis section from a completed Revibe analysis. Available sections: - technical_architecture (or "architecture") — system layers, technologies, diagrams - file_roles — what each file does, importance, dependencies - system_design_qa — interview-style Q&A about design decisions - story_flow (or "execution_flows") — how the app starts up and handles requests - database_schema (or "database") — tables, relationships, ER diagrams - concepts_explanation (or "concepts") — key patterns and concepts used - modules — logical groupings of files - business_logic — core domain logic and rules - flow_implementation — detailed execution flow code traces
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | yes | The job ID from analyze_repo. |
| section | string | yes | Section name (e.g. "architecture", "file_roles", "system_design_qa"). |
No output schema declared.
No examples provided.
get_summary ~49
Get a condensed summary of a completed Revibe analysis. Shows architecture pattern, language, file count, key modules, and available sections.
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | yes | The job ID from analyze_repo. |
No output schema declared.
No examples provided.
revibe_login ~47
Log in to Revibe via browser. Opens a browser window for authentication. After logging in and clicking Authorize, the API key is saved locally so all other Revibe tools work automatically.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.