Verdigraph — paid hosted MCP for compute routing

io.github.jdhart81Published by GitHub account jdhart81v0.2.0Updated Oct 26, 2026

Paid hosted MCP for agent-to-agent compute routing. 25% of net revenue funds conservation.

The publisher's own server: Energyai

VerifiedStreamable HTTPWeb executableCloud & InfrastructureDeveloper ToolsAI & ML

Overview

AI-generated overview

Paid hosted MCP endpoint for agent-to-agent compute routing, with a free local Python build of deterministic agent "brain" artifacts.

What you can do
  • Build deterministic, content-addressed brain artifacts from agent files (Claude project exports, OpenAI Assistant configs, prompt lists, Verdigraph genomes)
  • Re-verify saved brain artifacts and inspect invariant reports
  • Create developmental agents, feed them task evaluations, and inspect their graphs and ledgers
  • Choose compute profiles for routing work between agents
When to use it
When you want a reproducible, inspectable identifier for an agent configuration that can be pinned in git or cited in an audit, or when you need compute routing between agents through a hosted paid service.
Requirements
The hosted endpoint requires OAuth authentication and is billed per call. The local option needs Python with pip to install the package and its MCP extra, then runs over stdio.
Before you install
The hosted service is paid per call. Opting into the hosted comparison sends the bundled example to the provider's import endpoint; the README warns against sending private agent files there. The local server makes no network calls.

Installation

In SourceWeft

  1. Open Verdigraph — paid hosted MCP for compute routing in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.jdhart81%2Fverdigraph-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "verdigraph-paid-hosted-for-compute-routi": {
      "type": "http",
      "url": "https://verdigraph-mcp.hartjustin6.workers.dev/mcp"
    }
  }
}

README

verdigraph-neurogenesis

Clone this repo, run one script, and within 60 seconds you're building deterministic, content-addressed brain artifacts from any agent file — Claude project export, OpenAI Assistant config, raw prompt list, or Verdigraph genome JSON. Pure Python core; zero external services required.

[python] [tests] [license] [DOI] [Glama]


60-second quickstart

bash
git clone https://github.com/viridis-security/verdigraph-neurogenesiscd verdigraph-neurogenesisbash quickstart.sh

That's it. The script creates a venv, installs the package editable, runs the brain builder against an example genome, and prints the deterministic brain_id + content_hash. No Cloudflare account, no Stripe key, no verdigraph.dev account needed. Everything runs locally.

The default quickstart builds the bundled synthetic example locally and makes no hosted comparison request. Setup still uses pip to install the package and development dependencies. To compare that synthetic example with the hosted Worker, explicitly opt in:

bash
VERDIGRAPH_VERIFY_HOSTED=1 bash quickstart.sh

This sends the bundled example to https://verdigraph.dev/app/import and compares the returned brain_id. Use the local build commands below for private agent files; do not substitute private inputs into the hosted comparison.


What it is

Verdigraph turns an agent file into an inspectable cognitive graph with a content-addressed identifier you can pin in git, cite in an audit, or paste into a code review. Three things make this useful:

  1. Determinism. Identical input bytes always produce identical brain_id, content_hash, and graph structure. Run it twice, get the same answer twice. Run it in Python locally; run it in TypeScript on the Worker; same answer either way.
  2. Inspectable structure. Every brain carries 9 firing invariants + 1 advisory check (I9_fitness_metric_wired) so you can prove what the agent file actually compiles to without trusting a black box.
  3. Self-contained build pipeline. No external dependencies beyond the Python stdlib. No SaaS lock-in. You can audit every line of verdigraph/brain.py (≈ 660 lines) in an afternoon.

Use it

Build a brain from a Verdigraph genome

bash
python -m verdigraph build --file examples/hypothetical_research_agent.genome.json --format verdigraph_genome --pretty

Or pipe input:

bash
cat my_agent.json | python -m verdigraph build --stdin --format auto --summary --pretty

Build from a Claude project export

bash
python -m verdigraph build --file my_claude_project_export.json --format claude_project_export --pretty

Build from an OpenAI Assistant config

bash
python -m verdigraph build --file my_assistant.json --format openai_assistant --pretty

Build from a flat prompt list

bash
echo -e "You are a helpful assistant.\nSummarize the user's request.\nPlan steps and execute." \  | python -m verdigraph build --stdin --format prompt_list --pretty

Re-verify a saved brain artifact

bash
python -m verdigraph build --file my_agent.json --pretty > brain.jsonpython -m verdigraph verify brain.json

Use it as a Python library

python
from verdigraph.brain import extract, verify_brain, to_dict
genome = b'{"agent_name":"my_agent","purpose":"...","initial_nodes":["planner","executor"],"fitness_metrics":["task_success_rate"]}'
brain = extract("verdigraph_genome", genome)print(brain.brain_id)        # e.g. RMX124YY916WP0TCSEHFYX7M30print(brain.brain_uri)       # verdigraph://brain/RMX124YY916WP0TCSEHFYX7M30print(brain.content_hash)    # sha256 hexprint(len(brain.nodes), "nodes,", len(brain.edges), "edges")
report = verify_brain(brain)assert report.passed         # all non-advisory invariants pass
print(to_dict(brain))        # serialize for storage / round-trip

Expose it as an MCP server for your LLM agent

bash
pip install -e ".[mcp]"verdigraph-mcp                 # runs over stdio

Then in Claude Desktop config (~/Library/Application Support/Claude/claude_desktop_config.json):

json
{  "mcpServers": {    "verdigraph": {      "command": "/absolute/path/to/repo/.venv/bin/verdigraph-mcp",      "args": []    }  }}

Or in Claude Code: claude mcp add --transport stdio verdigraph /absolute/path/to/repo/.venv/bin/verdigraph-mcp.

Restart your client. Your agent now has verdigraph_* tools to create developmental agents, feed them task evaluations, inspect their graphs and ledgers, and choose compute profiles. Brain artifacts are built with python -m verdigraph build (above). No network calls; everything runs on your machine.


Determinism and verifiability

FieldWhat it isHow to verify
brain_id26-char Crockford-base32; derived from sha256(input_bytes + b":" + format) over the exact input bytes, so reformatting a file (whitespace, key order) gives a new idpython -m verdigraph build --file <same bytes> — same id every time
brain_uriverdigraph://brain/<brain_id>Self-describing form; safe for content-safety classifiers
content_hashsha256(canonicalize(brain_body_minus_content_hash))See docs/CANONICALIZATION.md for the exact algorithm
input_sha256sha256(raw_input_bytes)sha256sum your_file.json
Invariant report9 required checks + 1 advisory I9_fitness_metric_wiredAll carry id, description, passed, optional passed_with_default, advisory, detail

Canonicalization rule (one sentence)

Apply json.dumps with separators=(",", ":") after recursively sorting every object's keys lexicographically by codepoint and coercing integer-valued floats to integers (matches JavaScript JSON.stringify byte-for-byte). UTF-8 encoded before hashing. See verdigraph/brain.py::canonicalize (≈ 20 lines, stdlib only).

Identifiers are computed over the exact bytes you submit, so a pretty-printed genome and its minified form get different brain_ids. Pin one serialization (for example jq -c . genome.json). Test vectors, and a reference implementation that reproduces real hashes, are in docs/CANONICALIZATION.md.


Layout

verdigraph-neurogenesis/├── README.md                     ← you are here├── quickstart.sh                 ← clone → first brain in 60 seconds├── pyproject.toml                ← Python package metadata├── verdigraph/                   ← Python core (no external deps)│   ├── brain.py                  ← deterministic build pipeline (extract / canonicalize / verify)│   ├── cli.py                    ← `python -m verdigraph` CLI│   ├── genome.py                 ← AgentGenome / GrowthRules / SafetyAxioms (live-agent runtime)│   ├── graph.py                  ← CognitiveGraph / CognitiveNode / CognitiveEdge│   ├── agent.py                  ← DevelopmentalAgent (live-agent runtime)│   ├── growth.py / pruning.py    ← evolution operators│   ├── evaluation.py             ← task-outcome ledger│   ├── compute.py                ← compute-routing helpers│   └── ledger.py                 ← immutable event log├── verdigraph_mcp/               ← optional: stdio MCP server (`pip install -e ".[mcp]"`)├── tests/                        ← pytest, all green on a clean clone├── examples/                     ← runnable demos with fixture genomes├── docs/                         ← canonicalization spec, architecture, invariants└── papers/                       ← three companion papers (Zenodo-archived)

Hosted

Hosted: verdigraph.dev, paid per call. Viridis commits 25% of the net revenue it keeps (after creator payouts and pass-through costs) to conservation; the ledger is public at https://verdigraph.dev/conservation/public. Self-host: the Python MCP server in verdigraph_mcp/


Run the tests

Python core:

bash
source .venv/bin/activatepip install -e ".[dev]"pytest -q

The Python suite runs in CI (.github/workflows/tests.yml) on every push and pull request across Python 3.10 / 3.11 / 3.12. A secret-scan job fails the build if a live Stripe identifier is committed. The hosted service runs its TypeScript and cross-core parity tests in the private service repository.

The tests/test_brain_parity.py suite locks the deterministic-build contract — specifically that b'{"agent_name":"x","purpose":"y","initial_nodes":["a"],"fitness_metrics":["task_success_rate"]}' produces brain_id == "RMX124YY916WP0TCSEHFYX7M30" and content_hash == "20b9e5be0e5a0d34e564df6d0a554b1232ff9cc3ff309ab8da77a97756602c0c". If either side ever drifts, that test fails on the next CI run and we ship the divergence as a deliberate schema bump.


Companion papers

In papers/:

  1. PAPER_1_Physical_NeuroGenesis_SynapseForge.md — physical version: AI-agent-architected, 3D-printed, solution-grown neuromorphic substrates.
  2. PAPER_2_Verdigraph_Digital_NeuroGenesis.md — software version: self-evolving digital cognitive graphs.
  3. PAPER_3_Verdigraph_Compute_Efficiency.md — compute-efficiency layer.

To cite:

Hart, Justin. (2026). Verdigraph NeuroGenesis: A Software Framework for Self-Evolving AI-Agent Cognitive Substrates (Version 0.1.0). Zenodo. https://doi.org/10.5281/zenodo.20261687


License & contact

MIT. Maintained by Viridis LLC. Contact: [email protected].

This is an experimental research framework. It does not create autonomous unrestricted self-modifying AI. All growth and pruning actions are constrained by explicit genome rules, safety invariants, and an auditable ledger.

Source: README.md at commit 7732223

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v0.2.0LatestSep 16, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Energyaisolution integrations