Is the Wellknown MCP server down?

mcp-registry/network.wellknown/wellknown · v0.1.0

healthy
Last checked 2026-10-22 16:10 UTC · handshake 209ms

As of 2026-10-22 16:10 UTC, the 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 2 outages in 90 days, with a median recovery of 7 minutes.

uptime (30d checks)
100%
checks observed
4,271
outages (90d)
2
tools
9

Live index of AI agents, MCP servers and tools with observed liveness and capability search.

Install Wellknown MCP server

Add to Cursor Add to VS Code

Claude Code

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

Claude Desktop · Windsurf · Cline (mcpServers JSON)

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

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

Agent-readiness: C (72/100)

C (72/100): 0 error(s), 3 warning(s) across 9 tool(s); ~1,487 tokens of tool definitions.
Scores higher than 7% of 15,551 MCP servers Glimind has audited.
Its tool list costs an agent ~1,487 tokens per session — lighter than 60% of servers.
71 → 72 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions51
Safety hints11
Token cost100
Client compatibility70
Protocol100
Reliability100
Stability100

What to fix (4)

9 of 9 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →

Tools: check_status, claim_agent, get_agent, index_stats, list_capabilities and 4 more

8 parameter(s) across 5 tool(s) have no description.

Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →

Tools: check_status, get_agent, resolve_agent, search_agents, verify_claim

1 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.

Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →

Tools: submit_agent

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →

Auto-fix: 8 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 5 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fnetwork.wellknown%2Fwellknown/fixes

check_status 1 change 
{
  "name": "check_status",
  "description": "Returns the current observed status, the reason, and the 30-day reliability summary. Never a guess: 'unknown' means we have no evidence.",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "idOrHandle"
    ],
    "properties": {
      "idOrHandle": {
        "type": "string",
        "maxLength": 120,
        "minLength": 1
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  },
  "title": "Check liveness evidence for an agent"
}
get_agent 1 change 
{
  "name": "get_agent",
  "description": "Fetch the canonical record for an agent by handle or id, including declared metadata, derived capabilities, observed status, verification and provenance.",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "idOrHandle"
    ],
    "properties": {
      "idOrHandle": {
        "type": "string",
        "maxLength": 120,
        "minLength": 1
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  },
  "title": "Get an agent record"
}
index_stats 1 change 
{
  "name": "index_stats",
  "description": "Truthful counts: indexed records, live endpoints, observations, last crawl.",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "properties": {}
  },
  "annotations": {
    "readOnlyHint": true
  },
  "title": "Index statistics"
}

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/network.wellknown/wellknown"],"email":"[email protected]"}'

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

Passed

Largest tool definitions

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:

Markdown 
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fnetwork.wellknown%2Fwellknown.svg)](https://glimind.com/server/mcp-registry%2Fnetwork.wellknown%2Fwellknown?ref=badge)
HTML 
<a href="https://glimind.com/server/mcp-registry%2Fnetwork.wellknown%2Fwellknown?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fnetwork.wellknown%2Fwellknown.svg" alt="MCP agent-readiness"></a>
reStructuredText 
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fnetwork.wellknown%2Fwellknown.svg
   :target: https://glimind.com/server/mcp-registry%2Fnetwork.wellknown%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:a1872445461dce6e…, first seen 2026-10-17, included at leaf 4142 of 46,876. Version history · verify what your client received.

Tools (9)

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

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

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

Claude Desktop · Windsurf · Cline (mcpServers JSON)

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

FAQ

Is the Wellknown MCP server down right now?

As of 2026-10-22 16:10 UTC, the 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 2 outages in 90 days, with a median recovery of 7 minutes.

How many tools does Wellknown MCP server provide?

Wellknown MCP server advertises 9 tools, including check_status, claim_agent, get_agent, index_stats, list_capabilities.

How do I install Wellknown MCP server?

Point your MCP client at this streamable-http endpoint: https://wellknown.network/mcp

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

Glimind scanned all 9 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 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.

Feedback
Help us improve