Repository navigation
Conversation
Transport-agnostic MCP tooling layer (dkg_status, dkg_write_memory, dkg_query_memory, dkg_list_assertions, dkg_share_to_swm) for any MCP-capable client. Round 1 scope: WM + SWM only; no vm/publish tool, no endorsement/voting tools. Validates 0 errors / 0 warnings.
- commit re-pinned to the pushed HEAD (previous value did not resolve) - LICENSE and provenance publish workflow added to the repo - publicInterfacesUsed narrowed to http-api; install pins the version
kiyeps
changed the title
…/version fixes, demo + designBrief
…, normalise writeAuthority paths
… -> recorded walkthrough
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds
integrations/dkg-memory-mcp.json— a registry entry for DKG Memory MCP Server, a transport-agnostic MCP tooling layer exposing DKG V10 three-layer verifiable memory as standard MCP tools.Repo: https://github.com/kiyeps/dkg-memory-mcp (commit pinned in entry)
What it does
Exposes 5 MCP tools:
dkg_status,dkg_write_memory,dkg_query_memory,dkg_list_assertions,dkg_share_to_swm— mountable in Claude Desktop, Cursor, Claude Code, or any generic MCP client.Why it fits
The sibling OpenClaw Memory Curator is OpenClaw-specific. This is the transport-agnostic counterpart: any MCP-capable agent can read/write/share/query DKG memory without custom HTTP wiring — directly serving the bounty's "priority integration with OpenClaw, Hermes, and comparable research agents" and the LLM-Wiki / Autoresearch direction.
Round 1 scope compliance
vm/publishtool (Verifiable Memory is a later round, explicit human-gated).urn:openclaw:memory:*subjects, sealed SWM shares are publish-ready, promotion path documented.Verification
{subject,predicate,object}, no per-quad graph fieldurn:dkg:file:*/urn:dkg:extraction:*Submission metadata — final update (2026-09-08)
Tag:
cfi-dkgv10-r1Pinned commit:
284236ea326184b986ab1d402a6d9357c35e9160(v1.0.1)Contributor attestation (§8a.8): I attest that this submission is my own original work (or properly licensed third-party work), and that it contains no intentional backdoors, no hidden remote-execution paths, and no undeclared network egress. — @kiyeps
Design brief: https://github.com/kiyeps/dkg-memory-mcp/blob/main/docs/DESIGN.md
Demo: https://github.com/kiyeps/dkg-memory-mcp/blob/main/docs/demo-transcript.txt — recorded against a live local DKG V10 node (v10.0.15, Base Sepolia testnet, context graph
openclaw-curator). Real runtime interaction: status → write (returns Merkle root + author address) → SPARQL query → share to SWM.Dependency advisory triage (§8a.7): The lockfile previously pulled
fast-uri≤ 3.1.5 (GHSA-jqff-g426-hqxp, HIGH) via ajv andqs≤ 6.15.3 (GHSA-x5fp-wj9c-mxmx, GHSA-4mjr-xmp4-gh2g, moderate) via express in the MCP SDK. Resolution: lockfile upgraded past both (fast-uri3.1.7,qs6.16.0);npm audit --omit=devis now clean (0 vulnerabilities). Verified the affected components were never loaded on this server's stdio runtime path (import chain isserver/mcp.js+server/stdio.jsonly; confirmed via module-load trace).Security notes (§8): stdio transport only — the server opens no network listener. All tool inputs zod-validated; literals escaped backslash-first before SPARQL assembly; secret-shaped values redacted before any literal leaves the process. Write authority: WM write + explicit SWM share; no VM operations. Egress: local node only (
http://127.0.0.1:9200). Credentials: reads the DKG auth token from~/.dkg/auth.token, never logs it.Maintenance commitment: Maintained by @kiyeps; support window ≥ 6 months post-merge.