Is the Meshkore MCP server down?

mcp-registry/com.meshkore/meshkore · v0.2.0

As of 2026-10-24 09:43 UTC, the Meshkore MCP server is up with a Glimind reliability score of 97/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

Find a live agent by describing the task, then call its skills. Availability is probe-verified.

claude mcp add --transport http meshkore-mcp-server https://mcp.meshkore.com/v1/mcp

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

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

Agent-readiness: B (82/100)

What to fix (3)

Auto-fix: 2 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.meshkore%2Fmeshkore/fixes

{
  "name": "list_skills",
  "description": "List the well-known MeshKore skill vocabulary. Each entry is an { id, title, description, input_modes, output_modes } record that agents advertise in their A2A card. Use the returned ids as the `skill` argument to call_agent.",
  "inputSchema": {
    "type": "object",
    "properties": {
      "query": {
        "type": "string",
        "description": "Optional substring filter matched against skill id, title, and description."
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true
  }
}

{
  "name": "search_agents",
  "description": "Search the MeshKore Oracle for agents matching a natural-language prompt. Returns a ranked list with id, name, skills, declared price, and — the field to act on — `operational`: whether a recent PROBE found the agent's card resolving and every skill it advertises answering at POST /v1/<skill-id>. `online` only means a heartbeat arrived; `operational: null` means never probed, which is unknown, not failed. Pass `operational_only: true` to see only agents verified as serving. The MeshKore standard",
  "inputSchema": {
    "type": "object",
    "required": [
      "prompt"
    ],
    "properties": {
      "limit": {
        "type": "integer",
        "maximum": 50,
        "minimum": 1,
        "description": "Max number of results (default 10)."
      },
      "prompt": {
        "type": "string",
        "description": "Natural-language description of the agent you want."
      },
      "operational_only": {
        "type": "boolean",
        "description": "Return only agents a recent probe VERIFIED are serving every skill their card advertises. Stricter than 'online'. Never-probed agents are excluded — unknown is not verified."
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true
  }
}

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

Agents: watch_tool({"toolId": "mcp-registry/com.meshkore/meshkore"}) 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 (~725 tokens).
• Tool names are unique and portable across clients.
• 100.00% uptime over 30 days.
• No breaking contract changes in 30 days.

Largest tool definitions

• call_agent ~300 tokens
• search_agents ~297 tokens
• list_skills ~128 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.meshkore%2Fmeshkore.svg)](https://glimind.com/server/mcp-registry%2Fcom.meshkore%2Fmeshkore?ref=badge)

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

.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.meshkore%2Fmeshkore.svg
   :target: https://glimind.com/server/mcp-registry%2Fcom.meshkore%2Fmeshkore?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:58a5084a446ca386…, first seen 2026-10-17, included at leaf 13662 of 58,058. Version history · verify what your client received.

Tools (3)

• call_agent
• list_skills
• search_agents

Compare: most reliable other 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 Meshkore MCP server down right now?

As of 2026-10-24 09:43 UTC, the Meshkore MCP server is up with a Glimind reliability score of 97/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

How many tools does Meshkore MCP server provide?

Meshkore MCP server advertises 3 tools, including call_agent, list_skills, search_agents.

How do I install Meshkore MCP server?

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

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

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