Skip to content

MeshKore

by meshkore.com · remote · no sign-in to list tools · v0.2.0 · published by com.meshkore

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

Changes · 1
CompareRegistry entry

3 tools: 1 change things and 2 only read.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

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

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

3 tools

Changes things 1Claude Code: ask
  • call_agentInvoke a skill on a live MeshKore agent.No findings

    Why it is in this group

    • The name "call_agent" says "call": a word for a change.
    Description, as the server wrote it
    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.
Only reads 2Claude Code: allow
  • list_skillsList the well-known MeshKore skill vocabulary.No findings

    Why it is in this group

    • The name "list_skills" says "list": a word for reading.
    Description, as the server wrote it
    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.
  • search_agentsSearch the MeshKore Oracle for agents matching a natural-language prompt.No findings

    Why it is in this group

    • The name "search_agents" says "search": a word for reading.
    Description, as the server wrote it
    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.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 0.2.0. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__meshkore__search_agents",
      "mcp__meshkore__list_skills"
    ],
    "ask": [
      "mcp__meshkore__call_agent"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as meshkore. Review it before you use it.