Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

MeshKore

REMOTE · MCP.MESHKORE.COM

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

Available components

0 this week 71 Trust /100

Last scanned (16 hours ago)

Scores higher than 56% of remote servers

Reachable. Last reached 21 Nov 2026.

Category AI and Machine Learning

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security46
Transport & Reachability100
Schema Quality & AI Usability76
  • AI-judged instruction clarity (excellent).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
  • Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
What we tested

Checks we ran (12)

  • TLS certificate
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation 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.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 11 Nov 26 +1
    • Stability: 0.97 → pass security
  • 10 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 8 Nov 26 +1
    • Stability: 0.97 → pass security
  • 7 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 6 Sept 26 0
    • Tool “list_skills” rewrote its description, which is the text the model reads security
    • Server version: 0.1.0 → 0.2.0 functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://mcp.meshkore.com/v1/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=meshkore.com CN=YE1,O=Let's Encrypt,C=US 9 Oct 2026 7 Jan 2027 ECDSA 256 ECDSA-SHA384 62b63d781e68cd3f2851f96a193201c5bf5
SANs: *.meshkore.com, meshkore.com
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.meshkore.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
meshkore.com. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.meshkore.com/v1/mcp Verified 200
http (plaintext) http://mcp.meshkore.com/v1/mcp Served over HTTP 200
MCP tools · 3 exposed · ~543 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
call_agent ~244

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.

NameTypeReqDescription
agent_idstringyesThe MeshKore agent id (from search_agents).
paramsobject–Skill-specific parameters; sent verbatim as the JSON request body.
skillstringyesThe 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.

No output schema declared.

No examples provided.

list_skills ~80

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.

NameTypeReqDescription
querystring–Optional substring filter matched against skill id, title, and description.

No output schema declared.

No examples provided.

search_agents ~219

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.

NameTypeReqDescription
limitinteger–Max number of results (default 10).
operational_onlyboolean–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.
promptstringyesNatural-language description of the agent you want.

No output schema declared.

No examples provided.

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.

remote · mcp.meshkore.com

# add to Claude Code
claude mcp add --transport http com-meshkore-meshkore 'https://mcp.meshkore.com/v1/mcp'
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 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the MeshKore MCP server?

VerifyMCP ran 12 checks on MeshKore, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about MeshKore: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.