GenPark Consistent Hash Ring Router

io.github.alphaparkincPublished by GitHub account alphaparkincv1.0.1Updated Nov 7, 2026

Consistent hashing ring with virtual nodes for distributed LLM cache routing and agent partitioning

The publisher's own server: 370.ai — AI Gateway: 100+ Chat Models, Image & Speech Generation

VerifiedSTDIODesktop onlyAI & ML

Overview

AI-generated overview

A local MCP server providing a consistent hashing ring with virtual nodes, for routing distributed LLM caches and partitioning agents.

What you can do
  • Provides a consistent hashing ring with virtual nodes.
  • Intended for routing distributed LLM cache entries across nodes.
  • Intended for partitioning agents across a cluster.
  • No individual tools are listed in the manifest, so exact operations are not documented.
When to use it
Worth considering when you are building a distributed LLM cache or multi-agent setup and want the assistant to place keys or agents on a consistent hash ring with virtual nodes.
Requirements
Runs as a local process on the user's machine via a desktop MCP bundle (mcpb) over stdio. Desktop only; no web execution. No authentication, environment variables or headers are declared.
Before you install
The manifest lists no tools, README or instructions, so behavior cannot be verified before installing. It is a local desktop-only package, and no credentials are requested.

Installation

In SourceWeft

  1. Open GenPark Consistent Hash Ring Router in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft started this package once in an isolated sandbox, without credentials, to list its tools. That failed: the package type cannot run in the sandbox.

Version history

1
  1. v1.0.1LatestOct 24, 2026

Score

25% 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 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • 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

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.

Other Router integrations