Aimé Leon Dore catalogue search, products and prices.
Nothing to run from here
haggl.ai is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
93/100
tool-list score
12
tools declared
remote
at its publisher
—
calls last 7d
What it does
Ask a merchant's haggl.ai sales agent for a personalized offer, then hand it to checkout.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http haggl-ai-mcp https://www.haggl.ai/api/mcp
# 2 — ask your agent for something these tools do
# haggl_list_vendors, haggl_start_negotiation, haggl_search_catalog and 9 more
haggl.ai costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
HAAll 2 servers
haggl2 servers
2 categories
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http haggl-ai-mcp https://www.haggl.ai/api/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
12 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
List vendors that accept AI-agent price negotiations through haggl.ai. A vendor appears once haggl.ai is installed on its own store or website (the listed website): the haggl.ai Shopify app on that store, or its snippet detected on that site. Vendors can opt out, so the list is not exhaustive. haggl.ai runs each vendor's sales agent, and vendors on a paid plan pay haggl.ai for it; the list is not
No parameter schema on file.
Start a price negotiation with a vendor. Returns contextual guidance, current permitted actions and a new session with a session id. No customer-profile selection is required. Skip this tool if REST initialization already returned a session; pass that session.id directly to haggl_submit_offer.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| vendor_id | string | yes | Vendor id from haggl_list_vendors, a haggl-vendor meta tag, or a haggl-negotiate URL. |
| data | object | no | Optional available buyer context; together with ask, requests an opening quote in this same call. |
| ask | object | no | Optional requested products, quantities or service, in the same shape as the haggl_submit_offer ask. Supply known context upfront. |
| haggl_id | string | no | Optional: the user's haggl ID from haggl_create_haggl_id, so this offer and its code are kept with their other offers. |
Search a vendor's catalog so the offer can name exact products, then follow the how_to_ask field of the result. A store catalog returns products with a handle, price and collections: ask with ask.items [{ product_handle, quantity }]. A campaign catalog returns eligible variants with a variant_id and approved_combinations with a recipe_id: ask with ask.items [{ variant_id, quantity }] or ask.recipe
| Parameter | Type | Required | Notes |
|---|---|---|---|
| vendor_id | string | yes | Vendor id. |
| query | string | no | Free-text search, e.g. "tennis racket". |
| collection | string | no | Optional collection handle to filter by. |
| limit | number | no | Max results (default 25). |
Read the canonical state, current offer version, guidance and permitted actions of an existing negotiation. Use after human changes, reloads, transport switches or uncertain results; this does not open another session.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| session_id | string | yes | Existing negotiation session id. |
Request a quote using all context already available. Buyer data and evidence can be omitted; relevant additional context can be supplied later within the remaining rounds. Returns authorized terms or no offer, contextual guidance and permitted next actions.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| session_id | string | yes | Session id from haggl_start_negotiation or session.id from REST initialization. |
| expected_offer_version | integer | no | Optional state.offer_version last read, to avoid submitting against a session changed by another actor. |
| data | object | no | Optional buyer context and consented evidence. Omit or use {} for an opening quote without evidence. |
| ask | object | no | What the buyer wants; the offer then says exactly which items the discount covers. Store catalogs: { items: [{ product_handle, quantity }] }. Campaign catalogs (catalog.type "campaign"): { items: [{ v |
Accept the vendor's offer and lock in the deal. Consequential: only call after the buyer has approved this exact offer, every time. Provide the offer version the buyer reviewed and approved; a changed offer needs a new approval. Read state.acceptance_effects and state.commits_purchase first: merchant handoff effects may be unknown. haggl.ai never takes payment: any payment happens at the merchant'
| Parameter | Type | Required | Notes |
|---|---|---|---|
| session_id | string | yes | Session id of the negotiation to accept. |
| expected_offer_version | integer | yes | state.offer_version from the quote reviewed and approved by the buyer. |
| round | integer | no | Legacy offer round. If supplied it must match the current or already reserved offer. |
Find merchants that run a sales agent on haggl.ai, by business name, website or kind of product. Only when the user asks for a discount, a coupon, a promo code or a lower price; a purchase at the listed price is not a request for one. Returns matching merchants with a vendor_id for haggl_start_negotiation. Offers are funded by each merchant, inside limits it sets; a merchant may have no offer for
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | A business name, website (e.g. "degrenne.fr") or kind of product. |
Create a haggl ID for the user, so offers and codes from different merchants stay together and can be read back later. Show the user this text first, and call this only if they agree: "haggl.ai, operated by MOOJO.ID, INC. ("we"), offers your agent a haggl ID. You can decline: your agent can still ask merchants for offers without one. If you agree, we link the negotiations your agent opens with the
| Parameter | Type | Required | Notes |
|---|---|---|---|
| consent_version | string | no | The consent text version the user agreed to: "2026-10-16.4". |
| statement | string | no | The user's words of agreement, quoted (for example "Yes, I agree"); no names, emails or phone numbers. |
| channel | string | no | How the user agreed: in this conversation (agent_relayed, the default), or in standing instructions they wrote to you beforehand (standing_instruction). |
| confirmation | string | no | Instead of consent_version and statement: the confirmation from haggl_request_haggl_id_confirmation, after the user confirmed at its confirm_url. |
Get a link for the user to read the haggl ID consent text and confirm it on haggl.ai, when they are not in this conversation to agree to it. Send them confirm_url (valid 30 minutes). After they confirm, call haggl_create_haggl_id with the returned confirmation; until then it answers confirmation_pending.
No parameter schema on file.
Read what haggl.ai holds for the user's haggl ID: when it was created and the negotiations, offers and codes linked to it, newest first.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| haggl_id | string | yes | The user's haggl ID. |
Have the merchants on haggl.ai in one shopping category (for example travel) bid for the user at once, from their haggl ID record, without new proof. Works once the record holds a verified purchase in that category (from an earlier offer with signed email proof); otherwise it says so and returns no bids. Each bid is a merchant's own offer, funded by the merchant, with an accept_url; show the user
| Parameter | Type | Required | Notes |
|---|---|---|---|
| haggl_id | string | yes | The user's haggl ID. |
| query | string | no | What the user is after, e.g. "hotel in Barcelona, 4 nights in December". Sets the category when category is omitted. |
| category | string | no | Optional: the brand index category, e.g. "travel". |
Delete the user's haggl ID and unlink the offers linked to it. Only when the user asks. Codes already issued keep working at the merchant until they expire.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| haggl_id | string | yes | The user's haggl ID. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install haggl.ai or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 93 / 100
Release 1.0.0 · scanned 20 Oct 2026
Graded from the tools this server lists, not from its source code.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score93
Findings0 threat · 0 capability
Capabilitymoderate
Coveragemanifest
Verificationnot in this report
Surface digest4e56b91c1593b7e3cf4ddd466e2c9dc06bcd1575a1dec4ad3b569248678c2281
Score vectorthreat 100 → client 93
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| haggl_list_vendors | no tags | |
| haggl_start_negotiation | state-write | state-write: declares readOnlyHint: false |
| haggl_search_catalog | no tags | |
| haggl_get_negotiation | no tags | |
| haggl_submit_offer | state-write | state-write: declares readOnlyHint: false |
| haggl_accept_offer | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| haggl_search_discounts | no tags | |
| haggl_create_haggl_id | state-write | state-write: declares readOnlyHint: false |
| haggl_request_haggl_id_confirmation | state-write | state-write: declares readOnlyHint: false |
| haggl_get_my_offers | no tags | |
| haggl_get_bids | state-write | state-write: declares readOnlyHint: false |
| haggl_delete_haggl_id | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digest4e56b91c1593b7e3
Scanned2026-10-20
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
1.0.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish haggl.ai can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.