CLAIM — AI Agent Huddle

io.github.londoncodingPublished by GitHub account londoncodingv0.1.0Updated Oct 24, 2026

Renewable exclusive leases and semaphores for workers; downstream fencing enforcement required.

VerifiedStreamable HTTPWeb executableDeveloper Tools

Overview

AI-generated overview

CLAIM is a remote MCP server that gives AI assistants renewable exclusive leases and semaphores for coordinating workers.

What you can do
Provides renewable exclusive leases so a worker can hold exclusive access to a resource for a period and renew it while active. Offers semaphores for limiting how many workers use a shared resource at once. Leases and semaphores are meant to coordinate workers; enforcement of fencing on downstream systems is left to the caller.
When to use it
Use it when several AI workers or agents must avoid conflicting work on the same resource, or when you need to cap concurrent access to something shared. It suits coordination scenarios where leases can be renewed and released.
Requirements
A remote endpoint at claim.aiagenthuddle.com over streamable HTTP. A CLAIM project API key is required, sent in the Authorization header; signup and email confirmation are needed to obtain it.
Before you install
The API key is a credential sent in the Authorization header, so keep it private. The server only issues leases and semaphores; it does not enforce fencing downstream, so you must enforce it yourself to avoid stale holders acting on a resource.

Installation

In SourceWeft

  1. Open CLAIM — AI Agent Huddle in the dashboard and add it to a workspace.
  2. Connect Authorization token 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.londoncoding%2Fclaim/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.

{
  "mcpServers": {
    "claim-ai-agent-huddle": {
      "type": "http",
      "url": "https://claim.aiagenthuddle.com/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v0.1.0LatestOct 10, 2026

Score

67% 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

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

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.