# MeshKore (remote · mcp.meshkore.com)

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

- Trust score: 71/100 (medium)
- Change this week: +2
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-28

## Components

- remote · `mcp.meshkore.com`: 71/100 (this document), [markdown](https://verifymcp.io/servers/com-meshkore-meshkore/v1-mcp.md), [page](https://verifymcp.io/servers/com-meshkore-meshkore/v1-mcp)

## Channel facts

- Endpoint: `https://mcp.meshkore.com/v1/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.2.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-28.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS check failed: the endpoint is reachable over plaintext HTTP.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 76/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 543 tokens (~181/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 20/100
  - Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28.

## Install

### How do I install the MeshKore MCP server?

MeshKore is a hosted endpoint at https://mcp.meshkore.com/v1/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http com-meshkore-meshkore 'https://mcp.meshkore.com/v1/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-meshkore-meshkore": {
      "url": "https://mcp.meshkore.com/v1/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-meshkore-meshkore": {
      "type": "http",
      "url": "https://mcp.meshkore.com/v1/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-meshkore-meshkore]
url = "https://mcp.meshkore.com/v1/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-meshkore-meshkore": {
      "type": "remote",
      "url": "https://mcp.meshkore.com/v1/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-meshkore-meshkore --url 'https://mcp.meshkore.com/v1/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-meshkore-meshkore:
    url: "https://mcp.meshkore.com/v1/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-meshkore-meshkore": {
      "Transport": "http",
      "Url": "https://mcp.meshkore.com/v1/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-meshkore-meshkore -t streamable-http -u 'https://mcp.meshkore.com/v1/mcp'
```

### Other

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

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-28 (score 71, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-25 (score 71, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-23 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-20 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-18 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-16 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-14 (score 66, +1)

No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-12 (score 65, +1)

No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (3)

### `search_agents` (~219 tokens)

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 is router-not-broker: this tool never proxies skill calls, it points at agents you then invoke via call_agent.

Input parameters:

- `limit` (integer): Max number of results (default 10).
- `operational_only` (boolean): 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.
- `prompt` (string, required): Natural-language description of the agent you want.

### `call_agent` (~244 tokens)

Invoke a skill on a live MeshKore agent. Reads the agent's A2A card (/.well-known/agent.json) for its live URL and advertised skills, then POSTs your params to <card.url>/v1/<skill-id> — MeshKore routes, it never proxies the call. Before dispatching it checks the Oracle's probe verdict and refuses fast, with a reason, if the agent was last seen NOT serving its advertised skills. Payment: this tool does NOT pay on your behalf and settles nothing. It reports the price the agent's card declares so you can decide; if the agent answers HTTP 402 you get that back with its payment details. Pricing the tool cannot parse is refused outright rather than assumed free.

Input parameters:

- `agent_id` (string, required): The MeshKore agent id (from search_agents).
- `params` (object): Skill-specific parameters; sent verbatim as the JSON request body.
- `skill` (string, required): The skill id to invoke, exactly as the agent's card advertises it (e.g. 'search-hotels', 'generate-tweet'). See list_skills or the `skills` field of search_agents.

### `list_skills` (~80 tokens)

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.

Input parameters:

- `query` (string): Optional substring filter matched against skill id, title, and description.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-meshkore-meshkore/v1-mcp#diagnostics

## Score history

- 2026-09-28: 71
- 2026-09-27: 71
- 2026-09-26: 71
- 2026-09-25: 71
- 2026-09-24: 70
- 2026-09-23: 70
- 2026-09-22: 69
- 2026-09-21: 69
- 2026-09-20: 69
- 2026-09-19: 68
- 2026-09-18: 68
- 2026-09-17: 67
- 2026-09-16: 67
- 2026-09-15: 66
- 2026-09-14: 66
- 2026-09-13: 65
- 2026-09-12: 65
- 2026-09-11: 64
- 2026-09-10: 64
- 2026-09-09: 63
- 2026-09-08: 63
- 2026-09-07: 62
- 2026-09-06: 62
- 2026-09-05: 62
- 2026-09-04: 61
- 2026-09-03: 61
- 2026-09-02: 60
- 2026-09-01: 60
- 2026-08-31: 59
- 2026-08-30: 59

## Common questions

### What is the MeshKore MCP server?

MeshKore is an MCP server listed in the public MCP registry as com.meshkore/meshkore. Find a live agent by describing the task, then call its skills. Availability is probe-verified. This page covers its hosted endpoint (https://mcp.meshkore.com/v1/mcp).

### Is the MeshKore MCP server safe to use?

MeshKore scores 71 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the MeshKore MCP server expose?

MeshKore exposes 3 tools: search_agents, call_agent, list_skills. Their descriptions and schemas cost roughly 543 tokens of context every time the server is loaded.

### Does the MeshKore MCP server require authentication?

No. We connected to MeshKore without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the MeshKore MCP server still maintained?

MeshKore is still listed as active in the MCP registry. We last reached this channel on 28 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://mcp.meshkore.com/v1/mcp
- Repository: https://github.com/meshkore/mcp
- Website: https://meshkore.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-meshkore-meshkore/v1-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-meshkore-meshkore/v1-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-meshkore-meshkore/v1-mcp