InnoVint MCP by usefulapi

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

• Connection: Runs in the cloud
• Transport: Streamable HTTP
• Category: Other

Install

Pick the AI app you use, then copy the settings.

You need

• Runs in the cloudNothing to install; it connects over the internet

Which app do you use?

https://innovint.usefulapi.io/mcp

claude mcp add --transport http innovint https://innovint.usefulapi.io/mcp

{
  "mcpServers": {
    "innovint": {
      "url": "https://innovint.usefulapi.io/mcp"
    }
  }
}

{
  "servers": {
    "innovint": {
      "type": "http",
      "url": "https://innovint.usefulapi.io/mcp"
    }
  }
}

https://innovint.usefulapi.io/mcp

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Tool names and descriptions exactly as the server reported them on Nov 6, 2026. The maker wrote them, not us; we show them as plain text.

• innovint_list_wineries

  List the connected winery with id, name and the user's permissions. Hosted connections and scoped stdio return only the selected winery; unscoped stdio lists all accessible wineries. GET /api/v1/wineries or /api/v1/wineries/{wineryId}.

• innovint_get_winery

  One winery by id: name, internal id and the token user's permissions there. GET /api/v1/wineries/{wineryId}.

• innovint_list_lots

  List the winery's lots (wine, juice, fruit or case-goods batches) with code, name, stage, color, type, tax class, volume, weight, bottles on hand and tags. Filter by search term, code, id, bond, archived state or last update. GET /api/v1/wineries/{wineryId}/lots.

• innovint_get_lot

  One lot by id with its stage, volume, weight, bottles on hand, tags and links to related data. GET /api/v1/wineries/{wineryId}/lots/{id}.

• innovint_get_lot_composition

  The lot's makeup composition (what it is made of), now or right after a given action. GET /api/v1/wineries/{wineryId}/lots/{lotId}/makeupComposition.

• innovint_get_lot_components_summary

  A summary of the lot's components. GET /api/v1/wineries/{wineryId}/lots/{lotId}/componentsSummary.

• innovint_list_lot_analyses

  Lab and in-house analysis results recorded on a lot (pH, TA, free SO2, Brix, VA, ...). Filter by analysis type slug, vessel or date range. GET /api/v1/wineries/{wineryId}/lots/{lotId}/analyses.

• innovint_list_lot_additives

  Additives that have been added to a lot. GET /api/v1/wineries/{wineryId}/lots/{lotId}/additives.

• innovint_list_lot_costs

  Cost data per lot as of a date. Filter by lot code or id. GET /api/v1/wineries/{wineryId}/lotCosts.

• innovint_list_vessels

  List tanks, barrels and other vessels with their codes and current contents. Filter by search term, code, id, lot or archived state. GET /api/v1/wineries/{wineryId}/vessels.

• innovint_list_vessels_at_point_in_time

  Preview (vendor contract may change): What every vessel held at a past date-time (history of cellar contents). GET /api/v1/wineries/{wineryId}/vesselsAtPointInTime.

• innovint_list_actions

  The winery's work history across all action types (additions, analyses, transfers, racking, blending, bottling, fruit receiving, ...), filterable by type, state, reference number and dates. Each record has the action type, effective date and the lots and vessels involved; use the

• innovint_list_analysis_actions

  Analysis actions: the lab and in-house results entered in the winery, with the analyses (type, value, unit) and the lots and vessels they were taken on. GET /api/v1/wineries/{wineryId}/actions/analysisActions.

• innovint_list_addition_actions

  Addition actions: what additives were added to which lots and vessels, and when. GET /api/v1/wineries/{wineryId}/additionActions.

• innovint_list_transfer_actions

  Transfer actions: racking, filtering, topping off, barrel-down and other transfers between vessels. GET /api/v1/wineries/{wineryId}/transferActions.

• innovint_list_adjustment_actions

  Adjustment actions: volume or weight changes, water adds and makeup changes. GET /api/v1/wineries/{wineryId}/actions/adjustmentActions.

• innovint_list_receive_fruit_actions

  Fruit receiving actions (harvest intake) with the fruit received and the lots created. GET /api/v1/wineries/{wineryId}/actions/receiveFruitActions.

• innovint_list_analysis_types

  The analysis types InnoVint knows (pH, TA, free SO2, Brix, ...), with the slug that innovint_create_analysis_action and the analysis filters need. GET /api/v1/analysisTypes.

• innovint_list_additives

  The winery's additive products and their batches. GET /api/v1/wineries/{wineryId}/additives.

• innovint_list_vineyards

  The winery's vineyards (grower sources). GET /api/v1/wineries/{wineryId}/vineyards.

• innovint_list_blocks

  Vineyard blocks of the winery's vineyards. Filter by vineyard. GET /api/v1/wineries/{wineryId}/blocks.

• innovint_list_growers

  The growers the winery buys fruit from. GET /api/v1/wineries/{wineryId}/growers.

• innovint_list_grower_receipts

  Fruit receipts from growers for one vintage (year). GET /api/v1/wineries/{wineryId}/growerReceipts/{vintage}.

• innovint_list_vendors

  The winery's vendors (suppliers of additives, dry goods, services). GET /api/v1/wineries/{wineryId}/vendors.

• innovint_list_bonds

  The winery's bonded premises (TTB bonds), whose ids lots belong to. GET /api/v1/wineries/{wineryId}/bonds.

• innovint_create_analysis_action

  WRITE: records analysis results (e.g. pH 3.45, free SO2 28 mg/L) as a new analysis action in the winery's InnoVint records, effective at the given time. Each result needs an analysis type slug (innovint_list_analysis_types), a value and a unit, and a lot (add a vessel for a vesse

• innovint_create_vendor

  WRITE: adds a new vendor (supplier) by name to the winery's InnoVint records. Check innovint_list_vendors first to avoid a duplicate. POST /api/v1/wineries/{wineryId}/vendors.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026

• ✓ Pass

  Maker matches the repo

  The registry name was verified against the domain usefulapi.io (the registry checks domain ownership)

• … Not checked yet

  Still maintained

  We have not read this repo from GitHub yet

• … Not checked yet

  Has a licence

  We have not read this repo from GitHub yet

• ✓ Pass

  Endpoint responds

  Responded in 57 ms (HTTP 200)

• – Not applicable

  Sign-in with OAuth

  No sign-in needed

• ✓ Pass

  No hidden instructions in tool descriptions

  Read 27 tool descriptions and found no hidden instructions to the AI

Compared with others in Otheri

• More stars than 0% of the other 32433 servers in this category
• Published to the registry more recently than 97% of the other 32433 servers in this category
• Basic checks equal to or better than 100% of the other 32433 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

README from the maker

{