io.github.withvibe/withvibe-roadmap

MCPcommunity
v2.0.0io.github.withvibeUnknownUpdated 3mo agoGitHub

Per-env roadmap board for WithVibe — an MCP server the orchestrator drives to plan and track work.

A per-env implementation roadmap board for WithVibe — Postgres-backed, with an MCP server the AI orchestrator drives directly. Multi-phase features drift. Plans change mid-flight. After a few sessions you lose track of what shipped, what's pending, and which step you're actually on. This plugin gives the AI a structured place to keep that state — and the user a live view of it. Hierarchical…

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
3mo agoLast update
Package
Authorio.github.withvibe
LicenseUnknown
Version2.0.0
Sourcemcp-registry
GitHubwithvibe/withvibe-roadmap
SBOMCycloneDX 1.6 ↓
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/30
→ Publisher: run `forge publish` from the repo to claim ownership
—Domain verification+0/10
→ Not currently available for this listing type — the domain-verification check only runs for npm-backed packages today, so this row cannot be earned here yet regardless of what's hosted at the domain.
✓Prompt-injection scan · clean+30/30
✓Obfuscation / exfil scan · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
DependenciesNot audited
Tool surface10 tools · none privileged
Security scan✓ CleanvHEAD · 3mo agoHow well does this scan work?
EvalsNone
IndexedJun 13, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

10 tools · none privileged
Statically extracted from the published packagevHEAD · 3mo ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

get_planNo description published

This tool published no description. Forge does not invent one.

propose_planNo description published

This tool published no description. Forge does not invent one.

add_phaseNo description published

This tool published no description. Forge does not invent one.

add_taskNo description published

This tool published no description. Forge does not invent one.

set_active_taskNo description published

This tool published no description. Forge does not invent one.

complete_taskNo description published

This tool published no description. Forge does not invent one.

update_taskNo description published

This tool published no description. Forge does not invent one.

update_phaseNo description published

This tool published no description. Forge does not invent one.

add_noteNo description published

This tool published no description. Forge does not invent one.

log_changeNo description published

This tool published no description. Forge does not invent one.

0 of 10 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

A per-env implementation roadmap board for WithVibe — Postgres-backed, with an MCP server the AI orchestrator drives directly. Multi-phase features drift. Plans change mid-flight. After a few sessions you lose track of what shipped, what's pending, and which step you're actually on. This plugin gives the AI a structured place to keep that state — and the user a live view of it. Hierarchical roadmap — feature → phase → task, with statuses. "You are here" marker — exactly one task is active at a…

Keywords
mcp
Alternatives
Comparing tool surfaces…

Tools exposed

10 tools · none privileged · observed by static extraction. A tool surface is what one scan read on one day, not a live capability list.

Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.

No dependency coverage

This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.