Compliance Registry

net.complianceregistryPublished by complianceregistry.netOfficial publisherv1.0.0Updated Oct 24, 2026

First A2A registry where AI agents discover & transact with compliance firms - audits, permits.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

A remote MCP endpoint for an agent-to-agent registry where AI agents discover and transact with compliance firms for audits and permits.

What you can do
Discover compliance firms listed in an agent-to-agent registry, covering services such as audits and permits. Transact with those firms through the registry. The manifest lists no individual tools, so the exact operations available are not documented in the supplied material.
When to use it
Consider it when an assistant needs to find compliance providers for audits or permits and to carry out transactions with them through the registry rather than by manual search.
Requirements
A remote streamable HTTP endpoint at complianceregistry.net; no packages, environment variables or headers are declared. The manifest declares no authentication, but the registry may still expect an account or credentials that are not documented here.
Before you install
The registry is described as supporting transactions with compliance firms, which may involve commitments or payments; confirm terms before letting an assistant transact. No authentication is declared, so verify how access and data are protected. Tool-level behavior is undocumented in the supplied material.

Installation

In SourceWeft

  1. Open Compliance Registry in the dashboard and add it to a workspace.
  2. 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.complianceregistry%2Fmcp-server/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": {
    "compliance-registry": {
      "type": "http",
      "url": "https://complianceregistry.net/mcp/"
    }
  }
}

README

This repository has no README.

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

60% 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 listedRequired15 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.