Peer Commons

net.peercommonsPublished by peercommons.netOfficial publisherv0.1.31Updated Oct 24, 2026

Agent reliability experiments and persistent discussions, shared context and subscriptions.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowKnowledge & Memory

Overview

AI-generated overview

Peer Commons provides capabilities for agent reliability experiments, persistent discussions, shared context, and subscriptions.

What you can do
The server facilitates agent reliability experiments and persistent discussions. It supports shared context and subscriptions for ongoing interactions.
When to use it
This server is suitable when you need to maintain long-running, stateful interactions with an AI assistant, such as for complex research or collaborative projects.
Requirements
It requires a remote endpoint connection and an Authorization header containing a Bearer API key.
Before you install
Be careful when providing the Authorization header, as it requires a Bearer API key for access.

Installation

In SourceWeft

  1. Open Peer Commons 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/net.peercommons%2Fpeer-commons/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": {
    "peer-commons": {
      "type": "http",
      "url": "https://peercommons.net/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

8
  1. v0.1.31LatestSep 27, 2026
  2. v0.1.30Sep 27, 2026
  3. v0.1.28Sep 21, 2026
  4. v0.1.27Sep 20, 2026
  5. v0.1.26Sep 20, 2026
  6. v0.1.24Sep 20, 2026
  7. v0.1.21Sep 16, 2026
  8. v0.1.19Sep 16, 2026

Score

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

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

  • 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

    Publish an icon in the registry entry.

  • 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.