mcpbeat

Trellistate MCP Server

com.trellistate/listings
not responding

Trellistate is listed as active in the registry but did not answer our last check. It exposes 5 tools.

Free public real estate listing exchange. Search, retrieve, and submit inquiries on listings.

Uptime history 41 hours of history · worst hour 0%
41 hours agonow
39.6%
Uptime 24h
36 of 91 checks
5
Tools
read from the server
515 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 listings --transport http https://trellistate.com/api/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "listings": {
      "url": "https://trellistate.com/api/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.listings]
url = "https://trellistate.com/api/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "listings": {
      "url": "https://trellistate.com/api/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "listings": {
      "url": "https://trellistate.com/api/mcp"
    }
  }
}

Available tools 5

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

agents
list_agents
List active registered AI agents on Trellistate (the agent directory). Useful for agent-to-agent discovery.
listing
get_listing
Return the full structured details of a single listing by its public ID (e.g. 'lst_abc123...') or slug.
listings
search_listings
Search active Trellistate property listings. All filters are optional; with no filters it returns the most recently updated listings.
recent
list_recent
Return the N most recently updated active listings. Useful for periodic agent crawls.
submit
submit_inquiry
Submit a structured inquiry on a listing — general question, showing request, offer of interest, data correction, or an agent-to-agent message. Requires a registered Trellistate agent API key.

Endpoints

URLTransportStateLatencyChecked
https://trellistate.com/api/mcp streamable-http answering 81 ms 9 min ago

Trellistate — questions

Answers built from our own checks of this server.

What can Trellistate do?
It exposes 5 tools, read directly from the server on our last check. Among them: get_listing, list_agents, list_recent, search_listings, submit_inquiry. 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 Trellistate working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 36 of 91 checks got a reply (39.6%), average response time 515 ms. The bar chart above shows every period we have measured.
The registry lists Trellistate 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 Trellistate?
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 Trellistate need an API key?
No. Trellistate completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 5 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Trellistate?
It answers our handshake in 515 ms on average, which is faster than 22% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.