BovedIA — sistema de memoria personal para Claude Code: notas Markdown en tu disco, sincronizadas en la nube
from $15/mo
Nothing to run from here
Omni Coder Dashboard is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
Open Installation—
p95 latency
—
call success
local
runs on your machine
—
calls last 7d
What it does
OCD (Omni Coder Dashboard) — An AI memory engine with real semantic embeddings, 21 MCP tools, cross-tool routing, trace auditing, and proactive IDE interception. 100% local, zero API keys required.
Quickstart
# 1 — run it from where its publisher ships it
npx -y omni-coder-dashboard
# 2 — ask your agent something
> OCD (Omni Coder Dashboard) — An AI memory engine with real semantic embeddings, 21 MCP tools, cross-tool routing, trace auditing, and
Omni Coder Dashboard is free: there is no plan to choose, no cap to set and nothing that can bill you.
Publishernot claimed
RIAll 1 server
riko56521 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Omni Coder Dashboard as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. It is scanned, signed and pinned to the version you choose — read the surface before you approve it.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. Claude Code registers it in one command.
claude mcp add omni-coder-dashboard-mcp -- npx -y omni-coder-dashboardReconnect, or start a new session, and the tools appear in the model’s tool list.
Free to install, and it runs from its publisher’s own package: no account, no key, no card.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
31 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Search the semantic memory bank for successful code implementations from past coding sessions. Uses real vector similarity (ONNX/Ollama/OpenAI) — results labeled as semantic or keyword match.
Takes no parameters.
Example callreturns →
Fetch architecture patterns, code conventions, and deep context from the Knowledge Graph.
Takes no parameters.
Example callreturns →
Get context from the most recent coding session for continuity.
Takes no parameters.
Example callreturns →
Get which AI tool + model is statistically best for your current task type. For single-tool users, provides model-level optimization and workflow tips instead of cross-tool routing.
Takes no parameters.
Example callreturns →
Get a quick efficiency snapshot of your AI coding productivity.
Takes no parameters.
Example callreturns →
Get active AI coaching recommendations to improve productivity.
Takes no parameters.
Example callreturns →
Get AI development statistics for a specific project.
Takes no parameters.
Example callreturns →
Compare AI model performance and cost across your sessions. Models are normalized (e.g., kimi-k2.5 variants are merged).
Takes no parameters.
Example callreturns →
Save a critical handoff note or architectural decision for future AI agents.
Takes no parameters.
Example callreturns →
Get data-driven guidance on optimal prompt structure based on your history.
Takes no parameters.
Example callreturns →
Get a summary of AI coding activity grouped by topic.
Takes no parameters.
Example callreturns →
Get explicit
Takes no parameters.
Example callreturns →
Get a cost-routing recommendation: should this task use a free local model (Ollama) or a premium cloud model? Returns mathematically proven savings estimate.
Takes no parameters.
Example callreturns →
Retrieve solutions that teammates on the same local network discovered in their OCD instances. Requires P2P_SECRET env var to be set on all nodes.
Takes no parameters.
Example callreturns →
Manually submit a stack trace or error output for instant proactive analysis. OCD will search its memory and return the best matching past solution.
Takes no parameters.
Example callreturns →
Get an AI vs. human code authorship breakdown for commits. Shows per-project, per-branch, and per-tool attribution percentages for engineering managers, compliance reporting, and velocity tracking.
Takes no parameters.
Example callreturns →
Get personalized token-saving tips based on your usage patterns. Returns your daily burn rate, weekly forecast, top token consumers, and actionable quick wins to reduce waste.
Takes no parameters.
Example callreturns →
Check your current session health using cross-session patterns. Returns a status (healthy/degrading/critical), a suggested action (continue/compact/new_session), and context-aware nudges based on your historical usage patterns. Call this periodically to stay ahead of quality degradation.
Takes no parameters.
Example callreturns →
CRITICAL: Call this tool before starting any new action to understand the current scope. Returns the active task from OCD so you do not deviate or cause scope creep.
Takes no parameters.
Example callreturns →
Call this when the user suggests an idea that does not directly contribute to the current active task. Parks the idea in OCD so it is not lost, then redirects focus back to the task.
Takes no parameters.
Example callreturns →
Update the status of the current OCD task. Use this to mark tasks as completed, paused, or to set a new active task.
Takes no parameters.
Example callreturns →
Run a Trace-to-Evidence audit: accepts a question (e.g.
Takes no parameters.
Example callreturns →
List available audit templates for the Trace-to-Evidence system. Templates define evidence-gathering strategies for common audit patterns (mapping validation, ingestion throttling, fallback behavior).
Takes no parameters.
Example callreturns →
Retrieve past Trace-to-Evidence audit runs and their results. Useful for tracking recurring issues, comparing audit outcomes across sessions, and avoiding re-investigating solved problems.
Takes no parameters.
Example callreturns →
Takes no parameters.
Example callreturns →
Check session health for overrun, tool call repetition, and anti-hallucination risks. Returns verdicts (allow/warn/block). Works from any IDE.
Takes no parameters.
Example callreturns →
Log a tool call for repetition tracking. Use from IDEs without hook-based interception.
Takes no parameters.
Example callreturns →
Get the OCD Session Guard KPI effectiveness matrix — intervention counts, token savings, quality impact, repetition loops broken, and hallucination prevention. Shows how much value the guard is delivering.
Takes no parameters.
Example callreturns →
Session Governor: checks if the current session has hit convergence limits (turns, output tokens, duration, errors). Returns continue/checkpoint/hard_stop with actionable instructions. Call this periodically or when the session feels long.
Takes no parameters.
Example callreturns →
Session Governor statistics: checkpoint history, hard stops, overrides, most common triggers, current thresholds. Use to understand session governance patterns.
Takes no parameters.
Example callreturns →
Configure Session Governor thresholds for a project. Only set fields you want to override; others keep defaults.
Takes no parameters.
Example callreturns →
Freeyour plan
$0 forever
- Every tool, no call limit
- No card, no account needed
- Source published under a licence you can read
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because nothing bills
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable. Omni Coder Dashboard costs nothing to install and nothing to call, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: $8.42
$16.58 left
ATrust score 93 / 100
Release 5.5.0 · scanned 25 Aug 2026
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score93
Findings4 threat · 8 capability
Capabilityhigh
Coveragesource
Verificationrepo
Surface digest95c7ddfb3a1207724e4079a894e96063fd013ffebd1904dff1a1695e566cd854
Score vectorthreat 100 → client 93
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | high | capability blast radius (high) — client exposure if the model is manipulated | −6 |
| verification-discount | repo | publisher verification (public source) — no provenance, but the source is public and inspectable | −1 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tool surfaceread
Implementation sourceread
Package metadataread
Live transportnot available
Tools were statically extracted from the published source (24 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. high is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| get_similar_solutions | no tags | |
| get_knowledge_context | untrusted-input | |
| get_last_session_context | no tags | |
| get_routing_recommendation | no tags | |
| get_efficiency_snapshot | no tags | |
| get_active_recommendations | no tags | |
| get_project_stats | no tags | |
| get_model_comparison | no tags | |
| push_handoff_note | no tags | |
| get_optimal_prompt_structure | no tags | |
| get_topic_summary | no tags | |
| get_negative_constraints | no tags | |
| get_arbitrage_recommendation | no tags | |
| get_team_memory | no tags | |
| submit_ide_trace | no tags | |
| get_attribution_report | no tags | |
| get_efficiency_tips | no tags | |
| get_session_health_check | no tags | |
| get_current_task | no tags | |
| park_out_of_scope_idea | no tags | |
| update_task_status | no tags | |
| run_trace_audit | no tags | |
| get_audit_templates | no tags | |
| get_audit_history | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digest95c7ddfb3a120772
Scanned2026-08-25
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Pinned to 5.5.0 — the install command below asks for that release. A pin is part of an install, so it is kept for this visit and written down when you install.
5.5.0
undated
installedNo release note was published with this version.
—
no reviews yet
Reviews are earned
Only accounts with at least 50 real tool calls against this server in the last 90 days can post. Ratings are weighted by how much the reviewer actually uses it, and publishers can reply once per review.
Reviews are earned
Writing one takes an account with at least 50 real tool calls against Omni Coder Dashboard in the last 90 days. That is the whole gate — there is no other way to post, which is why the counts beside each review are worth reading.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes an account with 50 real tool calls against it.