Ibis Gear connector

An MCP server over the https://ibis.net.ua catalogue — fishing, outdoor clothing, camping and travel gear, knives and lights, hunting and sport shooting.

https://mcp.ibis-gear.shop/mcp

The connector is read-only. It answers questions about the catalogue: what is available, what it costs, how the price has moved, what customers wrote about it, and what suits a given shooting discipline. It cannot place an order, take a payment or change anything in the shop — when a customer has decided, it links them to the product page on https://ibis.net.ua.

What it is for

Outdoor equipment is bought on specifications. A rod has a length, a casting weight and an action; a sleeping bag has a comfort rating; a jacket has a membrane and a seam construction; a scope has magnification, objective diameter and a reticle. Which one is right depends on what the buyer actually does with it, and that is a conversation, not a filter.

The connector lets someone ask in their own words — "a spinning rod for perch up to 2,500 ₴", "a two-person tent that survives real wind", "boots warm enough for a January sit" — and get answers grounded in the live catalogue instead of guesses.

Typical use:

Data

Source
The public catalogue of https://ibis.net.ua, operated by Ibis.
Coverage
Around 132,000 product variants across 71,000 products, 1,300+ brands and 1,000+ categories.
Range
Fishing (~52k variants), clothing and footwear (~38k), camping and outdoor gear (~20k), firearms with optics and ammunition (~13k), military kit (~9k), knives and lights (~8k), gifts (~2k).
Freshness
Prices and availability for the in-stock range refresh daily from the shop's product feed; the wider catalogue refreshes on a slower cycle.
Currency
All prices are Ukrainian hryvnia (UAH).
Language
Product names, descriptions and reviews are in Ukrainian, as published by the shop.

The catalogue is a snapshot, not a live till. Availability and prices can lag behind the shop by up to a day. The server states this in its own instructions, so the model warns the user when the question turns on being current. Always confirm on https://ibis.net.ua before relying on a price.

Tools

All tools are read-only, and every one of them is annotated as such (readOnlyHint, non-destructive, idempotent, closed-world), so a client can reason about them without calling them.

search_products catalog:read

Search the ibis.net.ua catalogue by name, brand, category and availability. Returns name, price in hryvnia, availability, brand and a link to the product page, together with the total number of matches.

get_product catalog:read

Full product card by id: description, specifications, category path, rating and a couple of photos.

get_price_history prices:read

Price history of a product over the given period: observation points, the minimum, the maximum and the current value.

list_categories catalog:read

The shop's category tree with the number of products at each node. An empty parent returns the roots.

list_brands catalog:read

The shop's brands with the number of items each carries. The optional query filters by name.

get_reviews reviews:read

Customer reviews of a product together with the shop's replies: rating, text, date, reply threads.

get_product_images images:read

Product photos: temporary signed URLs valid for about an hour, and the images themselves as image content blocks.

get_sport_profile catalog:read

The shop's equipment profile for a shooting discipline: selection rules (magnification, reticle, objective), ready-made filter values and a list of related guides. An empty sport returns the list of known disciplines.

Prompts

Resources

The catalogue can also be read as documents rather than called as tools:

In-chat product card

The server ships an MCP Apps UI resource, ui://ibis/product-card, which renders a product inside the conversation with its photos and price, and can call back for the price history. Clients that do not support MCP Apps fall back to plain structured content and lose nothing but the layout.

Authentication

No sign-in required. The connector publishes a product catalogue — the same information anyone can read on the website — so there is no account to create and no key to paste. Connect it and ask.

Callers get read-only scopes (catalog:read, prices:read, reviews:read, images:read) and a per-address request limit. There is no write scope to grant: nothing in the server can change anything.

Because no sign-in is needed, the server does not advertise an authorization server: the OAuth discovery documents and /oauth/* endpoints answer 404 in this configuration, so a client connects directly rather than being sent through a consent flow it does not need. An OAuth 2.1 implementation exists behind that switch — protected-resource metadata (RFC 9728), authorization-server metadata (RFC 8414), Dynamic Client Registration (RFC 7591), PKCE S256, refresh tokens, resource indicators and revocation (RFC 7009) — and will be turned on if the connector ever carries anything belonging to an individual user. An organisation that wants a named credential with its own rate limit today can ask for a static API key.

Enterprise setup

Administrators rolling this out for an organisation need nothing beyond the endpoint above: there is no sign-in, so there is no per-tenant key to provision, no OAuth client to register and no allowlist to maintain.

Points a review usually turns on:

If your organisation needs a dedicated credential, a different rate limit or a signed agreement, write to ibisarms@pm.me.

Limits

Support

Questions, bug reports and access requests: support.