mcpbeat

GPT-5.6-sol Agent MCP Server

com.llmotions.farm/gpt-5-6-sol-agent
not responding

GPT-5.6-sol Agent is listed as active in the registry but did not answer our last check. It exposes 4 tools.

Authenticated async GPT-5.6-sol Agent agent with status polling and artifact results.

Uptime history 39 hours of history · worst hour 0%
39 hours agonow
62.6%
Uptime 24h
57 of 91 checks
4
Tools
read from the server
139 ms
Response time
average over 24h
open, no key
Access
streamable-http

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 9 min ago.

run in your terminal
claude mcp add gpt-5-6-sol-agent --transport http https://farm.llmotions.com/mcp/agents/gpt-5-6-sol-agent
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "gpt-5-6-sol-agent": {
      "url": "https://farm.llmotions.com/mcp/agents/gpt-5-6-sol-agent"
    }
  }
}
~/.codex/config.toml
[mcp_servers.gpt-5-6-sol-agent]
url = "https://farm.llmotions.com/mcp/agents/gpt-5-6-sol-agent"
.cursor/mcp.json
{
  "mcpServers": {
    "gpt-5-6-sol-agent": {
      "url": "https://farm.llmotions.com/mcp/agents/gpt-5-6-sol-agent"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "gpt-5-6-sol-agent": {
      "url": "https://farm.llmotions.com/mcp/agents/gpt-5-6-sol-agent"
    }
  }
}

Available tools 4

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

agentfarm
agentfarm_agent_info
Returns this agent's identity, listed per-task price, MCP endpoint, and access URL. This metadata call does not run the model and does not require a bearer token.
agentfarm_create_run
Queues an authenticated asynchronous task. This can consume paid model capacity. Poll with agentfarm_get_run_status, then read agentfarm_get_run_result.
agentfarm_get_run_result
Returns the final summary and artifact download URLs for an authenticated run.
agentfarm_get_run_status
Returns queued, running, succeeded, or failed status for an authenticated run.

Endpoints

URLTransportStateLatencyChecked
https://farm.llmotions.com/mcp/agents/gpt-5-6-sol-agent streamable-http answering 149 ms 9 min ago

GPT-5.6-sol Agent — questions

Answers built from our own checks of this server.

What can GPT-5.6-sol Agent do?
It exposes 4 tools, read directly from the server on our last check. Among them: agentfarm_agent_info, agentfarm_create_run, agentfarm_get_run_result, agentfarm_get_run_status. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is GPT-5.6-sol Agent working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 57 of 91 checks got a reply (62.6%), average response time 139 ms. The bar chart above shows every period we have measured.
The registry lists GPT-5.6-sol Agent as active — why does it not respond?
The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.
How do I connect GPT-5.6-sol Agent?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does GPT-5.6-sol Agent need an API key?
No. GPT-5.6-sol Agent completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 4 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is GPT-5.6-sol Agent?
It answers our handshake in 139 ms on average, which is faster than 75% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.