Performance marketing for agentic commerce. A shopper's agent asks a merchant's haggl.ai sales agent for an offer made for that customer, inside the budget and max discount the merchant caps, then hands the approved offer to the merchant's checkout. How to use it: find a participating merchant (haggl_search_discounts or haggl_list_vendors), start with haggl_start_negotiation, request a quote with haggl_submit_offer (the products, plus any context your user consents to share), show the offer to your user, and call haggl_accept_offer only after they approve that exact offer. haggl.ai never takes payment: it happens at the merchant's own checkout. No authentication. Protocol docs: https://www.haggl.ai/protocol

MCP readiness

B · 88/100

Readiness is how fully this listing follows its protocol and how it behaved in our probes over 30 days. It is shown for reference and does not move it in search. Search order and leaderboards use the separate quality grade (here C+, 70.0/100), which weighs availability, conformance, p95 speed and descriptor. How the two differ

Valid MCP handshake	10/10	initialize and tools/list both answered.
Live MCP endpoint	23/25	Endpoint answers the MCP initialize handshake (5525 ms); very slow response -2.
Protocol revision	10/10	Speaks the current MCP revision 2026-07-28.
Signed descriptor	n/a	No MCP standard defines a signed server descriptor.
Uptime (30 days)	15/15	28/28 probes succeeded over 30 days (100%).
Tool declaration	10/10	Lists 17 tool(s) with descriptions.
Verified identity	5/10	Publisher declared (repository, package or homepage); claim this listing to verify domain control.
Freshness + modern flags	4/5	seen in a source within 7 days.
Auth declaration	2/5	Declares credential scheme: smithery_api_key.

Applicable criteria total 90 points, scaled to 100.

Responsiveness: Very slow (5525 ms; bands ≤2.5 s, ≤5 s, ≤8 s, slower; penalty only).

Measured 2026-11-11.

Nine criteria, the same as the A2A readiness score, read from our daily MCP probe (initialize + tools/list) and 30-day probe history. No MCP standard defines a signed server descriptor, so that criterion is n/a and the other 90 points are scaled to 100. Grades: A>=90, B>=75, C>=60, D>=40, F<40. Display only: search order uses the quality grade.

Compared with peers

Against 53,039 reachable MCP servers in our daily snapshot (2026-11-12 06:46 UTC). Display only; it does not change search order.

Readiness: Higher than 95% of peers; This listing 88 · peer median 81
Latency: Faster than 44% of peers; This listing 372 ms · peer median 326 ms

Where it loses the most points, and how to win them back

Verified identity −5 — Claim the listing and prove control of its domain.
Now: Publisher declared (repository, package or homepage); claim this listing to verify domain control.
Auth declaration −3 — State how to authenticate (an auth scheme, or that none is needed).
Now: Declares credential scheme: smithery_api_key.
Live MCP endpoint −2 — Answer initialize and tools/list at the declared endpoint.
Now: Endpoint answers the MCP initialize handshake (5525 ms); very slow response -2.

How many agent tools actually work · All statistics

Listed in

Directories this entry was found in.

smithery since 2026-10-16 ↗

How to connect

MCP endpoint (streamable-http)

https://server.smithery.ai/haggl/haggl/mcp

JSON-RPC initialize probe

curl -X POST https://server.smithery.ai/haggl/haggl/mcp \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}'

Homepage

https://www.haggl.ai

Listed at (smithery)

https://www.haggl.ai