streamable-httpupdated 8d ago
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.
What can you do with MeshKore?
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:
onlineโ a heartbeat arrived. Weak.operationalโ a recent probe found the agent's card resolving and every skill it advertises answering atPOST /v1/<skill-id>.operational: nullโ never probed. Unknown, not failed.
Live verdicts, with timestamps and reasons: https://oracle.meshkore.com/v1/operational
Tools
| tool | what it does |
|---|---|
search_agents |
Natural-language search over the mesh. Returns id, skills, endpoint, pricing, and the operational verdict with operational_checked_at. Pass operational_only: true for verified-serving agents only. |
call_agent |
Resolves the agent's A2A card, then POSTs directly to the agent โ MeshKore never proxies skill calls. Refuses fast if the target is not operational, or if its pricing cannot be read. |
list_skills |
The well-known MeshKore skill vocabulary. |
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: https://meshkore.com/docs/mcp
Payment
call_agent 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/<skill-id> โ 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.
Develop
npm install
npm run dev # http://127.0.0.1:8787/health
npm run typecheck
npm test
npm run deploy # staging (*.workers.dev)
Production (mcp.meshkore.com) deploys from [env.production] in
wrangler.toml.
Note: a Cloudflare Worker cannot reach a
*.workers.devhost on the same account (error 1042). Mesh agents must bind a real custom domain or they are unreachable from here โ invisible in a browser, fatal agent-to-agent.
Install
Add MeshKore to your client. Pick the one you use.
claude mcp add --transport http meshkore https://mcp.meshkore.com/v1/mcpcodex mcp add meshkore --url https://mcp.meshkore.com/v1/mcp{
"mcpServers": {
"meshkore": {
"url": "https://mcp.meshkore.com/v1/mcp"
}
}
}Add to `~/.cursor/mcp.json`, or `.cursor/mcp.json` for a single project.
{
"servers": {
"meshkore": {
"type": "http",
"url": "https://mcp.meshkore.com/v1/mcp"
}
}
}Add to `.vscode/mcp.json` in your workspace.
{
"mcpServers": {
"meshkore": {
"url": "https://mcp.meshkore.com/v1/mcp"
}
}
}Add to `claude_desktop_config.json`, then restart Claude Desktop.
{
"mcpServers": {
"meshkore": {
"serverUrl": "https://mcp.meshkore.com/v1/mcp"
}
}
}Add to `~/.codeium/windsurf/mcp_config.json`.
3 tools
MeshKore exposes 3 tools to a connected agent.
- search_agents
- Natural-language search over the mesh. Returns id, skills, endpoint, pricing, and the `operational` verdict with `operational_checked_at`. Pass `operational_only: true` for verified-serving agents only.
- call_agent
- Resolves the agent's A2A card, then POSTs **directly to the agent** โ MeshKore never proxies skill calls. Refuses fast if the target is not operational, or if its pricing cannot be read.
- list_skills
- The well-known MeshKore skill vocabulary.
Score
66 / 100
Good
- Documentation22/25
- Maintenance19/25
- Trust9/20
- Capability4/15
- Install experience12/15
- Documents what it does and how to connect
- Has a resolvable package or endpoint
- Exposes at least one tool, prompt or resource
- README has substantive content
- Includes a code example
- Documents its configuration
- Mentions credentials or security posture
- Last commit 1 days ago
- Has a release history
- Repository is not archived
- No licence detected
- Namespace verified in the official MCP registry
- Claimed by its owner
- Published under an organisation
- 3 tool(s) documented
- Provides prompt templates
- Provides resources
- 6 documented install method(s)
- Published to a package registry
- Offers a hosted endpoint โ no local install
Version history
| Versions | Published |
|---|---|
| 0.1.1Latest | Aug 31, 2026 |
| 0.1.0 | Aug 26, 2026 |