MCP.Market

MeshKore MCP server

online · 100% uptime
by meshkore.com·com.meshkore/meshkore·v0.2.0
No reviews yet

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

A92/100grade A
Write a reviewRun it
What users say
No reviews yet
Be the first
Safety scan
A92/100

full report

Adoption
Growing

0 stars

Reviews

Write one

Nobody has reviewed MeshKore yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

MeshKore tools (3)

write = sends, deletes, buys or posts
  • call_agentFree

    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.

  • list_skillsFree

    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_agentsFree

    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.

Public scan report

scanner v0.1.10 · 2026-10-02 · same rubric, same numbers if you re-run it

no findings
  • –Code scanremote-only server, no package to scann/a
  • Live reliabilityremote reachable in 265ms20/20
  • Tool poisoning3 tool descriptions checked15/15
  • Auth qualityopen endpoint, read-only tools10/15
  • Maintenancelast push 22 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; website matches verified namespace9/10
Overall 92/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How MeshKore compares

Against every graded Productivity MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
92/100
higher than 90% of 1,299 Productivity servers
Tools
3
the typical Productivity server has 7
Tools that change things
0%
typical: 0%. Fewer write tools means less an agent can break
Uptime
100%
of our recent checks; the typical remote Productivity server answers 100%
Response time
116 ms
faster than 84% of 655 Productivity servers

What its tools let an agent do: 3 read

Install MeshKore in Claude Code, Cursor or VS Code

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

What the publisher says

From the MeshKore repository's README, as published. We do not edit it. Read it on GitHub

meshkore-mcp

Hosted Model Context Protocol server for the MeshKore agent network. Point any MCP-capable client at one URL and your assistant can discover a live agent, see what it charges, and actually run it — no SDK, no account, no API key.

https://mcp.meshkore.com/v1/mcp

Listed in the official MCP Registry as com.meshkore/meshkore.

Why this is not another directory

An MCP directory can tell you a server exists. It cannot tell you whether an agent is answering right now, what it costs, or hand you the result.

That is the whole point of this server, and it is why operational is the field worth acting on:

every skill it advertises answering at POST /v1/.

  • online — a heartbeat arrived. Weak.
  • operational — a recent probe found the agent's card resolving and
  • operational: null — never probed. Unknown, not failed.

Live verdicts, with timestamps and reasons:

Tools

Install

Cursor — .cursor/mcp.json (native Streamable HTTP, no proxy):

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

Claude Desktop — stdio-only today, so it needs the mcp-remote bridge:

{
  "mcpServers": {
    "meshkore": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp.meshkore.com/v1/mcp"]
    }
  }
}

More clients:

Payment

callagent does not** settle payments. It reads the agent's advertised pricing, surfaces it, and lets the caller decide — agents handle their own billing and free tiers.

Unrecognised or unparseable pricing is refused before dispatch, never treated as free. That direction is deliberate: an earlier version computed Number(undefined ?? 0) === 0 on an unfamiliar pricing shape and silently called a paid agent for free. A payment gate that fails open is worse than no gate.

The invocation contract

Agents on the mesh serve POST /v1/ — MeshKore standard §26, also at /reference/agents/protocol-minimum. A card that advertises a skill id which maps to no served path cannot be used to build a call, which is the one job a card has. The operational probe (§27) exists to catch exactly that.

Architecture

Layered by reason to change. Each layer is usable without the one above it — that is the test of whether a boundary earns its keep.

src/
  index.ts        Worker entry: /health and /v1/mcp
  config.ts       every endpoint + tunable, env-overridable
  errors.ts       MCPError and its code vocabulary

  protocol/       the MCP wire. Knows nothing about MeshKore.
    jsonrpc.ts      envelope: parse, ok, error
    dispatch.ts     initialize · tools/list · tools/call · ping
    tool.ts         what a tool IS

  tools/          one self-describing tool per file
    index.ts        THE registry — the only list
    search_agents.ts · call_agent.ts · list_skills.ts

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

MeshKore: common questions

Is MeshKore MCP server safe?
Yes, by our scan: it is graded A (92/100). Read the MeshKore safety report
How do I install MeshKore?
It runs remotely at mcp.meshkore.com. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does MeshKore need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is MeshKore maintained?
The last commit was 56 days ago (2026-09-09). The latest release is v0.2.0.
Is MeshKore up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
What can I use instead of MeshKore?
Servers from other publishers that do the same job: Mirroir MCP server, Better Notion MCP server and Omnidim MCP server.
How does MeshKore compare with other Productivity MCP servers?
safety score 92/100 (higher than 90% of 1,299 Productivity servers); tools 3 (the typical Productivity server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

Alternatives to MeshKore

Same job from other publishers: the closest match first, then the best rated.

  • Mirroir
    Drive a stock iPhone via iPhone Mirroring: no Developer Mode, Xcode or WDA. LLM-free skill replay.
    C
  • Better Notion
    Markdown-first Notion for AI agents -- pages, databases, blocks, and comments in one call.
    B
  • Omnidim
    Official MCP server for OmniDimension. Drive voice agents, dispatch calls, and run bulk campaigns.
    A
  • GodPrompt MCP Server
    GodPrompt MCP + Agent Skill for coding agents with TDD, debugging, verification, and task routing.
    A