Verdigraph — Paid Hosted MCP For Compute Routing
Route agent workloads through a hosted MCP when you need paid, remote compute orchestration between agents instead of wiring custom broker APIs.
Overview
Verdigraph is a MCP server for the Build phase that provides paid hosted agent-to-agent compute routing over remote HTTP MCP transports.
What is this MCP server?
- Paid hosted remote MCP at verdigraph-mcp.hartjustin6.workers.dev with streamable-http and SSE transports
- Agent-to-agent compute routing exposed as MCP tools over HTTP rather than a local-only stdio package
- Version 0.2.0 catalog entry with GitHub source at viridis-security/verdigraph-neurogenesis
- 25% of net revenue allocated to conservation per publisher description
- Catalog version 0.2.0
- Two remote transport types listed: streamable-http and SSE on the same MCP URL
- Publisher states 25% of net revenue funds conservation
Community signal: 1 GitHub stars.
What problem does it solve?
Solo builders wiring multiple agents together waste time on custom routing glue and have no standard way to offload compute orchestration from the IDE.
Who is it for?
Indie builders with a working agent product who want a hosted routing layer without operating their own broker infrastructure.
Skip if: Teams still exploring ideas with no agents in scope, or anyone who needs a free self-hosted routing stack only.
What do I get? / Deliverables
After you register the remote Verdigraph MCP URL in your agent, delegation and routing calls happen through MCP tools instead of one-off HTTP clients you maintain.
- Remote MCP connection config for agent-to-agent routing
- Callable MCP tools for compute routing from your agent session
- Reduced custom broker code in your agent integration layer
Recommended MCP Servers
Journey fit
Compute routing sits in Build because you wire it into the agent stack as tooling once the product direction is set. Agent-tooling is the canonical shelf for MCP servers that connect one agent runtime to external agent/compute services.
How it compares
Hosted MCP integration for agent compute routing, not a local skill file or a generic cloud deploy skill.
Common Questions / FAQ
Who is Verdigraph MCP for?
It is for developers shipping agent-based software who want remote MCP-accessible compute routing rather than custom inter-agent APIs.
When should I use Verdigraph MCP?
Use it during Build when agents need to hand off or route work to other agents or compute backends and you accept a paid hosted service.
How do I add Verdigraph MCP to my agent?
Add the remote MCP server URL https://verdigraph-mcp.hartjustin6.workers.dev/mcp in your client’s MCP config using streamable-http or SSE as supported, then authenticate per the host’s current docs.