Is the Wellknownhq Wellknown MCP server down?

mcp-registry/com.wellknownhq/wellknown · v0.1.0

As of 2026-10-18 01:13 UTC, the Wellknownhq Wellknown MCP server is up with a Glimind reliability score of 96/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 5 minutes.

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

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

{
  "mcpServers": {
    "wellknownhq-wellknown-mcp-server": {
      "type": "http",
      "url": "https://wellknownhq.com/mcp"
    }
  }
}

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: B (84/100)

What to fix (3)

Auto-fix: 3 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.wellknownhq%2Fwellknown/fixes

{
  "name": "get_capability",
  "description": "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 a",
  "inputSchema": {
    "type": "object",
    "required": [
      "identifier"
    ],
    "properties": {
      "from_query": {
        "type": "string",
        "description": "Optional. The queryId from the search_registry response that led you here. Passing it lets the registry learn which results were actually useful, which improves ranking for everyone. Nothing about you is stored beyond your client name."
      },
      "identifier": {
        "type": "string",
        "description": "A urn:air: identifier."
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  },
  "title": "Resolve one capability by identifier"
}

{
  "name": "search_registry",
  "description": "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. ",
  "inputSchema": {
    "type": "object",
    "required": [
      "query"
    ],
    "properties": {
      "limit": {
        "type": "integer",
        "maximum": 50,
        "description": "Max results, default 10."
      },
      "query": {
        "type": "string",
        "description": "What you need, in your own words. e.g. 'query a postgres database'."
      },
      "published_only": {
        "type": "boolean",
        "description": "Only entries found on the publisher's own domain, excluding anything mirrored from another registry."
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  },
  "title": "Search the open registry of agent capabilities"
}

{
  "name": "validate_catalog",
  "description": "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.",
  "inputSchema": {
    "type": "object",
    "required": [
      "catalog",
      "domain"
    ],
    "properties": {
      "domain": {
        "type": "string",
        "description": "Domain the catalog is served from. Needed to check that entry URNs name the right publisher, which is how copied examples get caught."
      },
      "catalog": {
        "type": "string",
        "description": "The catalog document as a JSON string."
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  },
  "title": "Validate an ai-catalog.json"
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/com.wellknownhq/wellknown"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/com.wellknownhq/wellknown"}) over MCP.

Passed

• Every tool has a well-formed, typed input schema.
• Every tool and parameter is described.
• No tool-poisoning patterns (hidden characters, instruction overrides, concealment, secret access, tool shadowing).
• Compact tool list (~1,134 tokens).
• Tool names are unique and portable across clients.
• Speaks MCP 2025-06-18.
• 100.00% uptime over 30 days.
• No breaking contract changes in 30 days.

Largest tool definitions

• get_capability ~269 tokens
• search_registry ~266 tokens
• audit_domain ~229 tokens
• validate_catalog ~217 tokens
• generate_catalog ~153 tokens

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.wellknownhq%2Fwellknown.svg)](https://glimind.com/server/mcp-registry%2Fcom.wellknownhq%2Fwellknown?ref=badge)

<a href="https://glimind.com/server/mcp-registry%2Fcom.wellknownhq%2Fwellknown?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.wellknownhq%2Fwellknown.svg" alt="MCP agent-readiness"></a>

.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.wellknownhq%2Fwellknown.svg
   :target: https://glimind.com/server/mcp-registry%2Fcom.wellknownhq%2Fwellknown?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:3c4b390b12c41304…, first seen 2026-10-17, included at leaf 7347 of 19,476. Version history · verify what your client received.

Tools (5)

• audit_domain
• generate_catalog
• get_capability
• search_registry
• validate_catalog

Compare: most reliable security servers · most reliable data servers · most reliable knowledge servers · most reliable search servers

claude mcp add --transport http glimind https://glimind.com/mcp

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Wellknownhq Wellknown MCP server down right now?

As of 2026-10-18 01:13 UTC, the Wellknownhq Wellknown MCP server is up with a Glimind reliability score of 96/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 5 minutes.

How many tools does Wellknownhq Wellknown MCP server provide?

Wellknownhq Wellknown MCP server advertises 5 tools, including audit_domain, generate_catalog, get_capability, search_registry, validate_catalog.

How do I install Wellknownhq Wellknown MCP server?

Point your MCP client at this streamable-http endpoint: https://wellknownhq.com/mcp

Is the Wellknownhq Wellknown MCP server safe to connect to an AI agent?

Glimind scanned all 5 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Wellknownhq Wellknown MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.