MeshKore
Find a live agent by describing the task, then call its skills. Availability is probe-verified.
Should I use this
Quality & Safety
Based on automated analysis of tool definitions and protocol compliance.
Context Cost
This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.
Install
One-Click Install
Add this to your `claude_desktop_config.json` file:
{
"mcpServers": {
"meshkore": {
"url": "https://mcp.meshkore.com/v1/mcp"
}
}
}Remote endpoints
https://mcp.meshkore.com/v1/mcpstreamable-httpWhat it can do
Tool inventory
Tools (3)
🟡search_agents(prompt, limit, operational_only)
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 Schema
{
"type": "object",
"properties": {
"prompt": {
"type": "string",
"description": "Natural-language description of the agent you want."
},
"limit": {
"type": "integer",
"minimum": 1,
"maximum": 50,
"description": "Max number of results (default 10)."
},
"operational_only": {
"type": "boolean",
"description": "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."
}
},
"required": [
"prompt"
],
"additionalProperties": false
}🟢call_agent(agent_id, skill, params)
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 Schema
{
"type": "object",
"properties": {
"agent_id": {
"type": "string",
"description": "The MeshKore agent id (from search_agents)."
},
"skill": {
"type": "string",
"description": "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."
},
"params": {
"type": "object",
"description": "Skill-specific parameters; sent verbatim as the JSON request body.",
"additionalProperties": true
}
},
"required": [
"agent_id",
"skill"
],
"additionalProperties": false
}🟢list_skills(query)
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 Schema
{
"type": "object",
"properties": {
"query": {
"type": "string",
"description": "Optional substring filter matched against skill id, title, and description."
}
},
"additionalProperties": false
}Community
Evidence