Skip to main content
Glama
Sign In

Compliance Registry

by net.complianceregistry
OverviewDiscussionsAdmin

Server Details

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

The last two health checks of this connector failed. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.

If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.

Status
Unhealthy
Uptime
0.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP
URL
ChatGPT
–
Claude
–

TDQS

A3.5/5.0

Scored across 6 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: claiming listings, searching firms, viewing profiles, getting audit details, requesting introductions, and requesting quotes. No overlap or ambiguity.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern (e.g., claim_listing, find_compliance_firm, get_firm_profile), making the set predictable and easy to navigate.

Tool Count4/5

With 6 tools, the count feels slightly low but still appropriate for the core functions of a compliance registry. It covers essential actions without being excessive.

Completeness3/5

The set covers searching, viewing, claiming, intro requests, and quotes, but lacks tools for managing claims or updating firm profiles, which could be gaps for some workflows.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    Try in Browser
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    Glama MCP Gateway

    Add one secure layer between your agents and this server.

    Resources