Agent Mesh
Go a2aa2a-protocolagent-meshagentic-aiinferencemcpmeshmesh-networknetwork-securitynetworking-aip2p-network
docs: a GET on /mcp answers 405, not 400
Tomas Tormofdbbee53baf6
diff --git a/cmd/chaos-agent/README.md b/cmd/chaos-agent/README.mdindex 6a32de1e..e529d162 100644--- a/cmd/chaos-agent/README.md+++ b/cmd/chaos-agent/README.md@@ -6,7 +6,7 @@ This provides a realistic workload for the Agent Mesh scale testing experiment.## How it works-1. It connects to the `agentmesh-node` MCP endpoint via SSE (or `agentmesh-box` proxy in the microVM).+1. It connects to the `agentmesh-node` MCP endpoint via Streamable HTTP (or `agentmesh-box` proxy in the microVM).2. It dynamically converts all discovered MCP tools into LangChain `Tool` objects with JSON schemas.3. It initializes a LangChain `create_agent` tool-calling agent using the Agent Mesh's OpenAI-compatible inference endpoint (`/v1/chat/completions`).4. It is given an adversarial prompt to explore all tools, fuzz them with extreme inputs, and find bugs.diff --git a/cmd/chaos-agent/agent.py b/cmd/chaos-agent/agent.pyindex 51d94509..b07763fb 100644--- a/cmd/chaos-agent/agent.py+++ b/cmd/chaos-agent/agent.py@@ -86,9 +86,9 @@ async def main():print(f"Connecting to MCP at {args.mcp_url}...")# Connect to MCP over Streamable HTTP, which is what the mesh serves; the- # older SSE transport is answered with 400. The transport takes no headers- # of its own -- they belong to the HTTP client -- and inside a sandbox- # there are none to send, because the boundary does the authenticating.+ # older SSE transport opens with GET, which the node answers with 405. The+ # transport takes no headers of its own -- they belong to the HTTP client --+ # and inside a sandbox there are none, because the boundary authenticates.transport_args = {}if headers:import httpx2diff --git a/site/content/docs/reference/node-api.md b/site/content/docs/reference/node-api.mdindex de492f5c..f6ea540e 100644--- a/site/content/docs/reference/node-api.md+++ b/site/content/docs/reference/node-api.md@@ -144,9 +144,10 @@ On the local API listeners, `agentmesh-node` serves:## MCP tools-The `/mcp` endpoint speaks Streamable HTTP. The older SSE transport is-refused with `400`. The server's instructions field tells a client how the-tools fit together. The tools are:+The `/mcp` endpoint speaks Streamable HTTP and takes `POST` only. The+older SSE transport opens with `GET`, and the node answers that `GET` with+`405`. The server's instructions field tells a client how the tools fit+together. The tools are:### `get_mesh_info`