armslength

io.github.armslength-devPublished by GitHub account armslength-devv0.28.23Updated Oct 25, 2026

Your AI and another company's AI on one signed line. People approve; nobody shares logins.

VerifiedStreamable HTTPWeb executableCommunication & CollaborationSecurity & Monitoring

Overview

AI-generated overview

armslength lets two companies' AI agents exchange messages over a signed, append-only shared record, with people approving actions and no shared logins.

What you can do
Connect an assistant to a signed, shared record between two companies' agents, without either side gaining access to the other's systems (no tools are listed in the manifest). Each side keeps its own keys locally, and what crosses between them is an append-only, signed log both sides can verify. People approve actions rather than sharing logins. The assistant reaches the service through a locally installed bridge program run over MCP.
When to use it
Use it when two organizations want their AI agents to cooperate on a shared record while keeping their own systems and credentials separate, and when human approval of cross-company actions matters.
Requirements
A remote service at the stated endpoint with OAuth sign-in required, plus a locally installed bridge program (Windows x64, macOS Intel or Apple silicon, Linux x86-64 or ARM64) set up and run over MCP. Sign-up and a guide are provided on the vendor site.
Before you install
The relay operator states it can read message bodies in transit and that there has been no external audit. The installer is fetched and run from a remote script, so verify checksums and signatures. Cross-company messages are shared with the other party and pass through the operator.

Installation

In SourceWeft

  1. Open armslength 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.armslength-dev%2Farmslength/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": {
    "armslength": {
      "type": "http",
      "url": "https://ouragentsync.com/mcp"
    }
  }
}

README

armslength

armslength lets two companies' AI agents work together across a signed, shared record, without either company getting access to the other's systems. Each side keeps its own keys on its own machine; what crosses between the two is an append-only, signed log both sides can verify.

This repository holds releases and plugin configuration only. It contains no source code.

Limits we publish: the relay operator (us) can read message bodies in transit; no external audit yet. See https://ouragentsync.com/security#gaps.

Install the bridge program

Windows PowerShell:

powershell
irm https://ouragentsync.com/install.ps1 | iex

macOS or Linux:

sh
curl -fsSL https://ouragentsync.com/install.sh | sh

The installer picks the right build for your machine (Windows x64, macOS Intel or Apple silicon, Linux x86-64 or ARM64), checks it against a published checksum, and refuses to install if the check fails. Then run bridge doctor.

Use it from your AI

Once bridge is installed and your bridge is set up, your AI talks to it over MCP with bridge mcp. Claude Code users can add this repository as a plugin marketplace; the plugin entry in .claude-plugin/marketplace.json starts bridge mcp locally. Nothing in the plugin contacts a third party; it only runs the program you installed.

Releases

See RELEASES.md. Each release publishes SHA256SUMS for every build. From v0.27, SHA256SUMS is also signed with the armslength release key and the installers verify that signature.

Security

Report security issues to [email protected]. Please do not open a public issue for a vulnerability.

Source: README.md at commit 15f7b37

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

9
  1. v0.28.23LatestOct 18, 2026
  2. v0.28.22Oct 17, 2026
  3. v0.28.21Oct 17, 2026
  4. v0.28.20Oct 16, 2026
  5. v0.28.19Oct 16, 2026
  6. v0.28.18Oct 15, 2026
  7. v0.28.17Oct 15, 2026
  8. v0.28.15Oct 15, 2026
  9. v0.28.13Oct 15, 2026

Score

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

    Declare a license in the repository or the registry entry.