AnchorDB
OCI · GHCR.IO/JOLOVICDEV/ANCHOR-DB:1.0.6
Persistent code memory for AI agents: notes pinned to files and symbols that survive refactors.
Available components
Last scanned (5 hours ago)
Scores higher than 85% of OCI servers
Category Memory and Knowledge
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 Security0
- No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
- Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
Provenance & Transparency32
- 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
- License check failed: no license is declared. See how to fix → Fail
- Actively maintained (last published 81 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability84
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1348 tokens (~61/item across 22 items; 21 tools + 1 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 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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "repo_remove" implies "remove" 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 23 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
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Checks we ran (12)
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (4)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Malware scan in Supply Chain Security (scores 0 for this)No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.
- Known CVEs in Supply Chain Security (scores 0 for this)Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
- Install scripts in Supply Chain Security (scores 0 for this)Install-script risk not yet assessed.
- Dependency health in Supply Chain Security (scores 0 for this)Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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
- Stability: 0.97 → pass security
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 −1
- Stability: pass → 0.93 functional
- 31 Oct 26 0
- Provenance: unverified → fail ▼ security
- 30 Oct 26 0
- Provenance: fail → unverified ▼ security
- 29 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 28 Oct 26 0
- Stability: 0.97 → pass security
- Security disclosure: fail → unverified ▼ functional
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
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 oci/ghcr.io/jolovicdev/anchor-db:1.0.6
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | oci |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
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 →
anchor_candidates ~39
Rank the places a stale anchor might now belong, with confidence and a code preview for each.
| Name | Type | Req | Description |
|---|---|---|---|
| anchor_id | string | yes | AnchorDB anchor ID. |
| Name | Type | Req | Description |
|---|---|---|---|
| candidates | null|array | yes | – |
No examples provided.
anchor_close ~27
Archive an anchor without deleting it.
| Name | Type | Req | Description |
|---|---|---|---|
| anchor_id | string | yes | AnchorDB anchor ID. |
| Name | Type | Req | Description |
|---|---|---|---|
| author | string | yes | – |
| binding | object | yes | – |
| body | string | yes | – |
| created_at | string | yes | – |
| id | string | yes | – |
| kind | string | yes | – |
| repo_id | string | yes | – |
| source_ref | string | yes | – |
| status | string | yes | – |
| tags | null|array | yes | – |
| title | string | yes | – |
| updated_at | string | yes | – |
No examples provided.
anchor_comment ~62
Add a threaded comment to an existing AnchorDB anchor.
| Name | Type | Req | Description |
|---|---|---|---|
| anchor_id | string | yes | Anchor ID to comment on. |
| author | string | yes | Actor identity. |
| body | string | yes | Comment body. |
| parent_id | string | – | Optional parent comment ID. |
| Name | Type | Req | Description |
|---|---|---|---|
| anchor_id | string | yes | – |
| author | string | yes | – |
| body | string | yes | – |
| created_at | string | yes | – |
| id | string | yes | – |
| parent_id | string | – | – |
No examples provided.
anchor_comments ~30
List threaded comments for a single AnchorDB anchor.
| Name | Type | Req | Description |
|---|---|---|---|
| anchor_id | string | yes | AnchorDB anchor ID. |
| Name | Type | Req | Description |
|---|---|---|---|
| comments | null|array | yes | – |
No examples provided.
anchor_context ~69
Read AnchorDB context for a repo file or symbol before editing.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | Repo-relative file path. |
| ref | string | yes | Git ref, branch, or WORKTREE. |
| repo_id | string | yes | AnchorDB repo ID. |
| symbol | string | – | Optional symbol path. |
| Name | Type | Req | Description |
|---|---|---|---|
| anchors | null|array | yes | – |
| repo | object | yes | – |
No examples provided.
anchor_create ~208
Create a new AnchorDB anchor attached to a file range.
| Name | Type | Req | Description |
|---|---|---|---|
| author | string | yes | Actor identity, e.g. agent://codex. |
| body | string | yes | Main anchor body. |
| end_col | integer | yes | 1-based ending column. |
| end_line | integer | yes | 1-based ending line. |
| kind | string | yes | warning|todo|handoff|rationale|invariant|question. |
| path | string | yes | Repo-relative file path. |
| ref | string | yes | Ref to read the span from: a commit, branch, or WORKTREE. The anchor follows the working tree from then on. |
| repo_id | string | yes | AnchorDB repo ID. |
| start_col | integer | yes | 1-based starting column. |
| start_line | integer | yes | 1-based starting line. |
| symbol | string | – | Optional explicit symbol path. |
| tags | array|string|null | – | Optional tag list. |
| title | string | yes | Short anchor title. |
| Name | Type | Req | Description |
|---|---|---|---|
| author | string | yes | – |
| binding | object | yes | – |
| body | string | yes | – |
| created_at | string | yes | – |
| id | string | yes | – |
| kind | string | yes | – |
| repo_id | string | yes | – |
| source_ref | string | yes | – |
| status | string | yes | – |
| tags | null|array | yes | – |
| title | string | yes | – |
| updated_at | string | yes | – |
No examples provided.
anchor_events ~46
Read an anchor's history: when it moved, went stale, or was updated, with the reason and confidence for each step.
| Name | Type | Req | Description |
|---|---|---|---|
| anchor_id | string | yes | AnchorDB anchor ID. |
| Name | Type | Req | Description |
|---|---|---|---|
| events | null|array | yes | – |
No examples provided.
anchor_file_view ~60
Read file view data with anchors, comments, and diff metadata.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | Repo-relative file path. |
| ref | string | yes | Git ref, branch, or WORKTREE. |
| repo_id | string | yes | AnchorDB repo ID. |
| Name | Type | Req | Description |
|---|---|---|---|
| anchors | null|array | yes | – |
| candidates | object | yes | – |
| comments | object | yes | – |
| content | string | yes | – |
| diff | string | yes | – |
| files | null|array | yes | – |
| history | object | yes | – |
| lines | null|array | yes | – |
| path | string | yes | – |
| ref | string | yes | – |
| repo | object | yes | – |
No examples provided.
anchor_get ~29
Read a single AnchorDB anchor by ID.
| Name | Type | Req | Description |
|---|---|---|---|
| anchor_id | string | yes | AnchorDB anchor ID. |
| Name | Type | Req | Description |
|---|---|---|---|
| author | string | yes | – |
| binding | object | yes | – |
| body | string | yes | – |
| created_at | string | yes | – |
| id | string | yes | – |
| kind | string | yes | – |
| repo_id | string | yes | – |
| source_ref | string | yes | – |
| status | string | yes | – |
| tags | null|array | yes | – |
| title | string | yes | – |
| updated_at | string | yes | – |
No examples provided.
anchor_relocate ~146
Re-pin a stale anchor, either by accepting a ranked candidate index or by giving an explicit line range. Returns the anchor to active status.
| Name | Type | Req | Description |
|---|---|---|---|
| anchor_id | string | yes | AnchorDB anchor ID. |
| candidate | integer|string|null | – | Index of a ranked candidate from anchor_candidates. Omit to supply an explicit line range instead. |
| end_col | integer | – | 1-based ending column, exclusive: it is one past the last column kept. |
| end_line | integer | – | 1-based ending line. |
| start_col | integer | – | 1-based starting column. |
| start_line | integer | – | 1-based starting line, when not accepting a candidate. |
| Name | Type | Req | Description |
|---|---|---|---|
| author | string | yes | – |
| binding | object | yes | – |
| body | string | yes | – |
| created_at | string | yes | – |
| id | string | yes | – |
| kind | string | yes | – |
| repo_id | string | yes | – |
| source_ref | string | yes | – |
| status | string | yes | – |
| tags | null|array | yes | – |
| title | string | yes | – |
| updated_at | string | yes | – |
No examples provided.
anchor_reopen ~27
Reopen an archived anchor.
| Name | Type | Req | Description |
|---|---|---|---|
| anchor_id | string | yes | AnchorDB anchor ID. |
| Name | Type | Req | Description |
|---|---|---|---|
| author | string | yes | – |
| binding | object | yes | – |
| body | string | yes | – |
| created_at | string | yes | – |
| id | string | yes | – |
| kind | string | yes | – |
| repo_id | string | yes | – |
| source_ref | string | yes | – |
| status | string | yes | – |
| tags | null|array | yes | – |
| title | string | yes | – |
| updated_at | string | yes | – |
No examples provided.
anchor_repos ~16
List repos registered in AnchorDB.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| repos | null|array | yes | – |
No examples provided.
anchor_resolve ~31
Re-run anchor resolution against the current file contents.
| Name | Type | Req | Description |
|---|---|---|---|
| anchor_id | string | yes | AnchorDB anchor ID. |
| Name | Type | Req | Description |
|---|---|---|---|
| author | string | yes | – |
| binding | object | yes | – |
| body | string | yes | – |
| created_at | string | yes | – |
| id | string | yes | – |
| kind | string | yes | – |
| repo_id | string | yes | – |
| source_ref | string | yes | – |
| status | string | yes | – |
| tags | null|array | yes | – |
| title | string | yes | – |
| updated_at | string | yes | – |
No examples provided.
anchor_search ~142
Search AnchorDB anchors by repo, path, symbol, status, kind, tags, and pagination.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | – | Optional anchor kind: warning, todo, handoff, rationale, invariant, or question. |
| limit | integer | – | Optional page size. |
| offset | integer | – | Optional offset. |
| path | string | – | Optional repo-relative file path. |
| repo_id | string | – | Optional repo ID. |
| status | string | – | Optional anchor status: active, stale, or archived. |
| symbol | string | – | Optional symbol path. |
| tags | array|string|null | – | Optional tags; an anchor must carry every listed tag to match. |
| Name | Type | Req | Description |
|---|---|---|---|
| anchors | null|array | yes | – |
No examples provided.
anchor_stale ~69
List anchors that could not be relocated automatically, each with its best relocation suggestion. Use this to find notes that need re-pinning after a refactor.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Optional maximum number of anchors to return. |
| repo_id | string | – | Optional repo ID to scope the queue. |
| Name | Type | Req | Description |
|---|---|---|---|
| stale | null|array | yes | – |
No examples provided.
anchor_text_search ~90
Full-text search over anchor bodies and comments.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | – | Optional anchor kind. |
| limit | integer | – | Optional page size. |
| offset | integer | – | Optional offset. |
| path | string | – | Optional repo-relative file path. |
| query | string | yes | Search query text. |
| repo_id | string | – | Optional repo ID. |
| symbol | string | – | Optional symbol path. |
| Name | Type | Req | Description |
|---|---|---|---|
| hits | null|array | yes | – |
No examples provided.
anchor_update ~89
Update anchor metadata such as kind, title, body, author, or tags.
| Name | Type | Req | Description |
|---|---|---|---|
| anchor_id | string | yes | AnchorDB anchor ID. |
| author | string | – | Optional new author. |
| body | string | – | Optional new body. |
| kind | string | – | Optional new kind. |
| tags | array|string|null | – | Optional replacement tag list. |
| title | string | – | Optional new title. |
| Name | Type | Req | Description |
|---|---|---|---|
| author | string | yes | – |
| binding | object | yes | – |
| body | string | yes | – |
| created_at | string | yes | – |
| id | string | yes | – |
| kind | string | yes | – |
| repo_id | string | yes | – |
| source_ref | string | yes | – |
| status | string | yes | – |
| tags | null|array | yes | – |
| title | string | yes | – |
| updated_at | string | yes | – |
No examples provided.
repo_add ~46
Register a local Git repository with AnchorDB.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Optional display name for the repo. |
| path | string | yes | Absolute or relative path to the local Git repo. |
| Name | Type | Req | Description |
|---|---|---|---|
| created_at | string | yes | – |
| default_ref | string | yes | – |
| id | string | yes | – |
| name | string | yes | – |
| root_path | string | yes | – |
| updated_at | string | yes | – |
No examples provided.
repo_get ~28
Read a single registered repo by ID.
| Name | Type | Req | Description |
|---|---|---|---|
| repo_id | string | yes | AnchorDB repo ID. |
| Name | Type | Req | Description |
|---|---|---|---|
| created_at | string | yes | – |
| default_ref | string | yes | – |
| id | string | yes | – |
| name | string | yes | – |
| root_path | string | yes | – |
| updated_at | string | yes | – |
No examples provided.
repo_remove ~32
Remove a repo and all of its anchors from AnchorDB.
| Name | Type | Req | Description |
|---|---|---|---|
| repo_id | string | yes | AnchorDB repo ID. |
| Name | Type | Req | Description |
|---|---|---|---|
| deleted | boolean | yes | – |
| id | string | yes | – |
No examples provided.
repo_sync ~33
Refresh a repo's HEAD metadata and re-resolve active anchors.
| Name | Type | Req | Description |
|---|---|---|---|
| repo_id | string | yes | AnchorDB repo ID. |
| Name | Type | Req | Description |
|---|---|---|---|
| created_at | string | yes | – |
| default_ref | string | yes | – |
| id | string | yes | – |
| name | string | yes | – |
| root_path | string | yes | – |
| updated_at | string | yes | – |
No examples provided.
How do I install the AnchorDB MCP server?
AnchorDB runs locally as a container image, launched with docker run --rm -i ghcr.io/jolovicdev/anchor-db:1.0.6. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
oci · ghcr.io/jolovicdev/anchor-db:1.0.6
claude mcp add jolovicdev-anchordb -- docker run --rm -i ghcr.io/jolovicdev/anchor-db:1.0.6
What is the AnchorDB MCP server?
AnchorDB is an MCP server listed in the public MCP registry as io.github.jolovicdev/anchordb. Persistent code memory for AI agents: notes pinned to files and symbols that survive refactors. This page covers its container image (ghcr.io/jolovicdev/anchor-db:1.0.6).
Is the AnchorDB MCP server safe to use?
AnchorDB scores 52 out of 100 on VerifyMCP. 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 AnchorDB MCP server expose?
AnchorDB exposes 21 tools: anchor_candidates, anchor_close, anchor_comment, anchor_comments, anchor_context, and 16 more. Their descriptions and schemas cost roughly 1,319 tokens of context every time the server is loaded.
Is the AnchorDB MCP server still maintained?
AnchorDB 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 did VerifyMCP test on the AnchorDB MCP server?
VerifyMCP ran 12 checks on AnchorDB, covering Source repository, Provenance, License, Maintenance and 8 more. 4 items could not be completed, a gap on our side rather than a finding about AnchorDB: Malware scan, Known CVEs, Install scripts and Dependency health. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to a container image, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.