Skip to content
Flathead Trades logo

Flathead Trades MCP server

Which MCP servers are Flathead Trades's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-29

← Back to Flathead Trades

Whose server it is
  • Registry namecom.flatheadtrades/directoryverified in the MCP registry

The registry name sits under flatheadtrades.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-29
  • Stateanswerschecked 2026-10-29
  • Tools3
  • Server calls itselfflathead-trades
  • Server version1.0.0
  • Protocol version2025-06-18

On 2026-10-29 the server answered initialize and tools/list without a sign-in. First answer in 118 ms.

Should an agent connect itNot proven either way yet
  • Its tools do browse valley trade businesses by trade and town, but not take live job offers as a tradesperson.
  • Checked on 6 of the 7 days it takes to judge reliability.

Once connected

  • For "browse valley trade businesses by trade and town", the likely first call is find_pros.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 6, the first on 2026-10-29
  • INITE MCP scoreafter a weeka score needs 7 daily checks: 6 so far
  • What an agent can do with it1 of 2 use cases
  • Answeredmeasuring6 of the 7 daily checks it takes to print a share
  • Median first answer146 ms
  • Space in an agent's context≈ 378 tokensthe definitions of all its tools (3), which an agent carries on every turn
  • Tool definitionsA · 100 of 100
  • Typed results0 of 3 toolsdeclared outputSchema: results come typed, read once
  • Every tool passes all six checks.

What an agent can do with it

  • not sure · post a home repair job to a local pro
  • cannot · take live job offers as a tradesperson
  • can do · browse valley trade businesses by trade and town

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

Worth a look

None of the five warning signs in these definitions.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers3 tools · read 2026-10-29
  • find_pros

    List the businesses in the Flathead Trades directory for a kind of work, optionally in one town, with phone numbers, websites and a link to each listing. Covers Whitefish, Columbia Falls, Evergreen, Kalispell, Somers, Bigfork, Lakeside…

  • list_trades_and_towns

    The trades and towns the Flathead Trades directory covers, with how many businesses each has.

  • start_quote

    Make a link that opens the Flathead Trades quote form already filled with the work, the town and the description. The person finishes it and agrees to be contacted themselves; the request is then offered live to one local pro at a time…

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "directory": {
      "type": "http",
      "url": "https://flatheadtrades.com/api/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http flatheadtrades https://flatheadtrades.com/api/mcp

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://flatheadtrades.com/api/mcp as a custom connector in the settings.

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.