# com.wellknownhq/wellknown

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

- **Type:** MCP server
- **Trust:** 60/100 (B), scored on the content rubric
- **Verification:** community-indexed — nobody has claimed this listing
- **Version:** 0.1.0
- **Author:** com.wellknownhq
- **License:** Unknown
- **Endpoints:** streamable-http https://wellknownhq.com/mcp
- **Source:** https://wellknownhq.com
- **Endpoint health:** reachable (last checked 2026-09-24T17:33:22.594Z, 5 samples) — uptime is not a security property and is not part of the trust score
- **Compatible clients:** claude-code, cursor, copilot, chatgpt, gemini (basis: transport)

## Trust

60/100 (B), scored on the content rubric
- Publisher verified: no
- Install scripts: nothing suspicious found
- Prompt-injection scan: clean
- Obfuscation scan: clean
- Evidence age: 0 days

## Security scan

- **Status:** clean
- **Scanned:** 2026-09-24T17:33:22.594Z
- **Version scanned:** live
- **CVEs:** no coverage — this entry has no package coordinates to query OSV against, so "no known CVEs" is NOT asserted for it.

## Tools

5 declared. Observed from a live `tools/list` probe.
- `search_registry` — 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. Fin
- `get_capability` — Fetch the full record for a urn:air: identifier returned by search_registry: endpoint, description, publisher, conformance grade, and trust level. Call this bef
- `audit_domain` — 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
- `validate_catalog` — 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,
- `generate_catalog` — 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 sh

## Install

**Verdict: review** — Installable, but 2 things to check first: No CVE coverage: this entry has no npm/PyPI coordinates to query OSV against, so "no known vulnerabilities" is not a claim that can be made about it.
**Cautions** (coverage gaps and advisories — never blocking)
- No CVE coverage: this entry has no npm/PyPI coordinates to query OSV against, so "no known vulnerabilities" is not a claim that can be made about it.
- No publisher has proved control of this listing; it is indexed, not vouched for.
**Config** (claude-code):
```json
"{\n  \"mcpServers\": {\n    \"wellknown\": {\n      \"type\": \"http\",\n      \"url\": \"https://wellknownhq.com/mcp\"\n    }\n  }\n}"
```

## Blast radius

Contained to moderate — no credential declaration found, from the publisher, the upstream registry, or the README. Known so far: runs on someone else's infrastructure; read-only tool surface.
- Floor 9, ceiling 27 (tier: unknown)
- `unknown` means the floor and ceiling land in different bands — not measured enough to name one. It does not mean low.
- This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score.

## Machine-readable views of this entry

- Signed JSON: https://forgeregistry.com/api/v1/packages/com.wellknownhq%2Fwellknown
- Install plan: https://forgeregistry.com/api/v1/packages/com.wellknownhq%2Fwellknown/install-plan
- Alternatives: https://forgeregistry.com/api/v1/alternatives/com.wellknownhq%2Fwellknown
- HTML page: https://forgeregistry.com/registry/com.wellknownhq%2Fwellknown
- MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan`

## About this document

Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.