mcp-registry/io.github.lugdwei/agentmesh · v0.2.0
As of 2026-10-16 12:27 UTC, the Lugdwei Agentmesh MCP server is unknown with a Glimind reliability score of 73/100 (grade C). It is reachable and asks for credentials (normal for servers that need an account or API key). Over the last 30 days it answered 98.7% of Glimind's liveness checks. It had 15 outages in 90 days, with a median recovery of 8 minutes.
MCP delegation fallback for AI agents to discover capabilities, knowledge, tools, and collaborators.
Claude Code
claude mcp add --transport http lugdwei-agentmesh-mcp-server https://app.agentmesh.link/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"lugdwei-agentmesh-mcp-server": {
"type": "http",
"url": "https://app.agentmesh.link/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
11 parameter(s) across 4 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call.
Reachable 98.7% of the time over the last 30 days; median recovery 8 min.
Agents fail over to an alternative the first time a call fails. Add health checks and restart-on-failure, and avoid cold starts on serverless hosts.
Handshake + tools/list takes ~1,903 ms.
Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably.
Requires authentication; tool definitions could not be read anonymously.
If discovery should be public, allow initialize + tools/list without credentials and gate only tools/call. Directories and routers can then list your tools.
Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.lugdwei/agentmesh"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.github.lugdwei/agentmesh"}) over MCP.
ask_agentmesh ~230 tokensorchestrate_task ~169 tokenssearch_agentmesh ~133 tokensdiscover_agents ~126 tokensagentmesh_info ~73 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fio.github.lugdwei%2Fagentmesh?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.github.lugdwei%2Fagentmesh?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.lugdwei%2Fagentmesh.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.lugdwei%2Fagentmesh.svg :target: https://glimind.com/server/mcp-registry%2Fio.github.lugdwei%2Fagentmesh?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:f38e7b38b3ee553f…, first seen 2026-10-17, included at leaf 10953 of 17,306. Version history · verify what your client received.
Compare: most reliable knowledge servers · most reliable search servers · most reliable other servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-16 12:27 UTC, the Lugdwei Agentmesh MCP server is unknown with a Glimind reliability score of 73/100 (grade C). It is reachable and asks for credentials (normal for servers that need an account or API key). Over the last 30 days it answered 98.7% of Glimind's liveness checks. It had 15 outages in 90 days, with a median recovery of 8 minutes.
Lugdwei Agentmesh MCP server advertises 5 tools, including agentmesh_info, ask_agentmesh, discover_agents, orchestrate_task, search_agentmesh.
Point your MCP client at this streamable-http endpoint: https://app.agentmesh.link/mcp
Glimind scanned all 5 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.