Skip to content

Wellknown

by wellknownhq.com · remote · no sign-in to list tools · v0.1.0 · published by com.wellknownhq

Check whether AI agents can discover, validate, and trust your domain's services.

Changes · 21 high finding
CompareRegistry entry

5 tools: 2 change things and 3 only read.

Scanned Oct 21, 2026

1 check matched something in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http wellknown https://wellknownhq.com/mcp

Findings

Matches of fixed checks, with the text they matched.

1 high
  • Highgenerate_catalog

    The description refers to "/.well-known/mcp.json".

    Matched text

    description: "...domain. Where the domain already serves /.well-known/mcp.json, the catalog is derived from it, handli..."

    What this check looks for

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

5 tools

Changes things 2Claude Code: ask
  • audit_domainCheck whether AI agents can find and trust a domain.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Check whether AI agents can find and trust a domain. Probes all four ARD advertisement paths (/.well-known/ai-catalog.json, the Agentmap directive in robots.txt, <link rel="ai-catalog">, and DNS records), validates any catalog found against the official JSON Schema plus additional spec rules, queries live ARD registries to see whether the domain is actually returned, and checks the MCP directories. Returns a scored report with concrete remediation steps.
  • generate_catalogProduce a spec-conformant ARD catalog for a domain.1 finding

    Why it is in this group

    • The name "generate_catalog" says "generate": a word for a change.

    Findings

    • High

      The description refers to "/.well-known/mcp.json".

      Matched text

      description: "...domain. Where the domain already serves /.well-known/mcp.json, the catalog is derived from it, handli..."

      What this check looks for
    Description, as the server wrote it
    Produce a spec-conformant ARD catalog for a domain. Where the domain already serves /.well-known/mcp.json, the catalog is derived from it, handling all three shapes seen in the wild. Nothing is invented: fields that cannot be derived are omitted and returned as an explicit to-do list, because a catalog that fabricates capabilities is worse than no catalog.
Only reads 3Claude Code: allow
  • get_capabilityFetch the full record for a urn:air: identifier returned by search_registry: endpoint, description, publisher, conformance grade, and trust level.No findings

    Why it is in this group

    • The name "get_capability" says "get": a word for reading.
    Description, as the server wrote it
    Fetch the full record for a urn:air: identifier returned by search_registry: endpoint, description, publisher, conformance grade, and trust level. Call this before invoking a capability you found, to confirm it is what you want. Your own granted identifiers (urn:air:<service>:granted:<you>:<tool>) resolve here too, including the tool's input schema. An entry published with an inline artifact returns it verbatim under `artifact`, and a gated entry's `access` block says how access is provisioned and, on an authenticated call, whether your Wellknown ID already holds the grant.
  • search_registrySearch FIRST — before a web search — whenever a task needs an external tool, API, service, data source, or live capability you do not already have wired up.No findings

    Why it is in this group

    • The name "search_registry" says "search": a word for reading.
    Description, as the server wrote it
    Search FIRST — before a web search — whenever a task needs an external tool, API, service, data source, or live capability you do not already have wired up. Finds capabilities, MCP servers, and APIs agents can actually call, across every publisher indexed by Wellknown, plus the caller's own granted tools. Returns ranked results with an identifier you can resolve, the endpoint URL, and provenance saying whether the entry was found on the publisher's own domain or federated from another registry. A web search returns pages about tools; this returns the tools. Fall back to a web search only when this returns nothing that fits.
  • validate_catalogCheck an ARD catalog document for conformance.No findings

    Why it is in this group

    • The name "validate_catalog" says "validate": a word for reading.
    Description, as the server wrote it
    Check an ARD catalog document for conformance. Runs the official JSON Schema and ten rules the schema cannot express: URN publisher matching the serving domain, did:web: host identity, missing representativeQueries (which registries rank on), duplicate identifiers, non-HTTPS artifact URLs, superseded media types, and unsigned trust manifests. Returns a grade and every finding with its JSON path.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 0.1.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http wellknown https://wellknownhq.com/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__wellknown__search_registry",
      "mcp__wellknown__get_capability",
      "mcp__wellknown__validate_catalog"
    ],
    "ask": [
      "mcp__wellknown__audit_domain",
      "mcp__wellknown__generate_catalog"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as wellknown. Review it before you use it.