Skip to content
Hagglyai logo

Hagglyai MCP server

Which MCP servers are Hagglyai'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-27

← Back to Hagglyai

Whose server it is
  • Registry namecom.hagglyai/hagglyverified in the MCP registry

The registry name sits under hagglyai.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-27
  • Stateanswerschecked 2026-10-27
  • Tools5
  • Server calls itselfhaggly
  • Server version0.1.0
  • Protocol version2025-06-18

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

Should an agent connect itNot proven either way yet
  • Whether its tools do the product's job has not been judged yet.
  • Checked on 1 of the 7 days it takes to judge reliability.

Once connected

  • Parameters are untyped or undescribed in 2 of 5 tools: check arguments before calling.

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: 1, the first on 2026-10-27
  • INITE MCP scoreafter a weeka score needs 7 daily checks: 1 so far
  • Answeredmeasuring1 of the 7 daily checks it takes to print a share
  • Median first answer328 ms
  • Space in an agent's context≈ 1,083 tokensthe definitions of all its tools (5), which an agent carries on every turn
  • Tool definitionsA · 93 of 100
  • Typed results0 of 5 toolsdeclared outputSchema: results come typed, read once
  • Parameters without a description: in 2 of 5

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 offers5 tools · read 2026-10-27
  • find_best

    Given a plain-language task (e.g. 'web search', 'scrape a page to markdown', 'BTC price'), returns the recommended paid API endpoint and ranked alternatives with price per call, reliability score and real usage. Use before paying for an…

  • compare_category

    Full ranked comparison of paid endpoints in one category. Call list_categories for valid ids.

  • most_popular

    The 3 paid endpoints in one category with the most paying wallets in the last 30 days: "Most popular" first, then "Popular", the same as the site's stickers. Endpoints with warnings are held back and named. Call list_categories for valid…

  • check_endpoint

    Returns the score, stored probe history, price and usage for an exact endpoint URL in Hagglyai's catalogue. Does not call the supplied URL. Hagglyai API documentation: https://hagglyai.com/openapi.json

  • list_categories

    Categories Hagglyai compares, with endpoint counts, the cheapest price per call, and each category's sub-categories (platform and task ids for compare_category).

How to connect

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

{
  "mcpServers": {
    "haggly": {
      "type": "http",
      "url": "https://hagglyai.com/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http hagglyai https://hagglyai.com/mcp

Add to CursorAdd to VS Code

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

OpenAPI spec

4 paths, read 2026-10-27. Open the spec ↗

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.