MCP server · registry snapshot 2026-10-24 · last tested 2026-10-24

io.usefulapi/vintrace

Read vintrace vessels, batches, work orders, lab results, stock; assign work orders, add notes. — the publisher's description

4 of 4 record checks metRead-only · tools listed 2026-10-24version 1.0.0JavaScriptstreamable HTTP34 tools

Summary

io.usefulapi/vintrace is a remote MCP server listed in the official MCP registry at version 1.0.0. On 2026-10-24 ProtocolProbe connected to it in read-only mode and read its inventory: 34 tools, 0 resources and 1 prompt.

Record checks

4 of 4 record checks met · 4 do not apply · 1 not checked

met: Registry entry is active and says how to run it
met: Source repository link opens
met: Repository is not archived
met: Code pushed to the repository in the 90 days before our check
not checked: Repository publishes a security policy (SECURITY.md)
not applicable: Package names its licence with a standard (SPDX) identifier
not applicable: The version the registry lists can be installed and is not withdrawn
not applicable: npm package carries build provenance (attestation)
not applicable: No known critical or high advisory in the package or its dependencies

From public records, not a safety rating. Each check with its reason · Is it safe to install?

Key facts

Runs: remote (hosted by the publisher)
Transport: streamable HTTP
Sign-in: none needed to open a session
Repository: public
Tools: 34
Last tested: 2026-10-24

Add to your client

Observed fact

This server accepted a session without any credential and lists 3 tools whose name or declaration suggests they change data (vintrace_add_stock_item_note, vintrace_assign_work_order, vintrace_deactivate_booking). That is our reading of the names; we did not call them. Source: our connection, 2026-10-24.

How fresh this is

Live-tested: yes, a real session (not a text-only review)
Last tested: 2026-10-24
Mode: read-only (no tool calls)
Latest version: 1.0.0, published 2026-10-24 (registry, as of the 2026-10-24 snapshot)
First listed version: 2026-10-24 (earliest version still in the registry; older removed versions would be earlier)
Registry data: snapshot 2026-10-24
Package and repository: checked 2026-10-24
Engine: mcp-runtime-engine@0.1.0 · sdk@1.32.0

Changes since the last refresh

New in the registry: not in the list of 2026-10-23, listed on 2026-10-24 with version 1.0.0 (published 2026-10-24).

Source: the official MCP Registry list on 2026-10-23 and on 2026-10-24.

What it is

What does this server offer?

Observed inventory

34tools

0resources

1prompts

None of its 34 tools are described as changing anything. For 34 the reading was uncertain, so no mark is shown.

vintrace_list_work_orders
“List winery work orders (cellar jobs such as transfers, additions, bottling) with their jobs, assignee, status and scheduled time.”
Publisher declares: read-only yes · destructive no · open-world yes
6 inputs
- scheduled_sincestring“Only work orders scheduled at or after this time (inclusive).”
- scheduled_beforestring“Only work orders scheduled at or before this time (inclusive).”
- statusstring“Work order status, or several separated by commas (for example READY,IN_PROGRESS).”
- operation_typesstring“Winery job type, or several separated by commas (for example TIRAGE,TRANSFER).”
- limitinteger“Results per page, 1-200 (vintrace default 10).”
- offsetinteger“Index of the first result (default 0).”
vintrace_list_wine_batches
“List wine batches (the named lots of wine) with volume, variety, vintage and owner.”
Publisher declares: read-only yes · destructive no · open-world yes
4 inputs
- idstring“Comma-separated vintrace batch ids to fetch.”
- includestring“Extra parts to include, comma-separated: vessels, allocations.”
- limitinteger“Results per page, 1-200 (vintrace default 10).”
- offsetinteger“Index of the first result (default 0).”
vintrace_get_vessel_details_report
“The bulk wine report: every vessel (tank, barrel, bin, press, tanker) with its contents, volume, batch, owner and winery as at a date.”
Publisher declares: read-only yes · destructive no · open-world yes
13 inputs
- as_atstring“Run the report as at this time (default now).”
- winery_idinteger“Only this winery.”
- winery_namestring“Only the winery with this exact name.”
- business_unitstring“Only this winery business unit.”
- batchstring“Only vessels holding this wine batch.”
- vesselstring“Only this vessel (by name/code).”
- vessel_idinteger“Only this vessel id.”
- product_idinteger“Only this wine/product id.”
- ownerstring“Only this owner.”
- vessel_typestring“Vessel types, comma-separated: TANK, BIN, BARREL, BARREL_GROUP, BIN_GROUP, PRESS, TANKER.”
- extra_fieldsstring“Extra fields, comma-separated: composition, allocations, liveMetrics.”
- limitinteger“Results per page, 1-200 (vintrace default 10).”
- offsetinteger“Index of the first result (default 0).”
vintrace_get_vessel
“One vessel by id: a tank, barrel, barrel group, tanker or bin, with its details, dimensions and contents.”
Publisher declares: read-only yes · destructive no · open-world yes
2 inputs, 2 required
- vessel_typestringrequired“What kind of vessel.”
- vessel_idintegerrequired“vintrace vessel id.”
vintrace_list_lab_requests
“The lab console: analysis tasks (samples to measure) with lab, template, vessel, batch, status and arrival.”
Publisher declares: read-only yes · destructive no · open-world yes
12 inputs
- statusarray“Task statuses (for example Completed to include finished tasks).”
- lab_namearray“Only tasks assigned to labs with these names.”
- analysis_template_namearray“Only tasks using these analysis templates.”
- vessel_namearray“Only tasks sampled from vessels with these names.”
- batcharray“Only tasks sampled from batches with these names.”
- work_order_numberarray“Only tasks requested by these work orders (TWL123 or 123).”
- arrival_statusstring“Only samples with this arrival status.”
- date_afterstring“Only tasks requested at or after this time.”
- date_beforestring“Only tasks requested at or before this time.”
- modified_sincestring“Only tasks modified at or after this time.”
- limitinteger“Results per page, 1-200 (vintrace default 10).”
- offsetinteger“Index of the first result (default 0).”
vintrace_list_trial_blends
“List trial blends (planned blend trials) with status and composition.”
Publisher declares: read-only yes · destructive no · open-world yes
6 inputs
- statusstring“Trial blend status, or several separated by commas.”
- composition_summary_bystring“Summarise composition by: variety, vintage, region, subRegion (comma-separated).”
- modified_sincestring“Only records modified after this time.”
- modified_beforestring“Only records modified before this time.”
- limitinteger“Results per page, 1-200 (vintrace default 10).”
- offsetinteger“Index of the first result (default 0).”
vintrace_search_transactions
“Winemaking operations completed in a date range (transfers, additions, blends, racking...) with the from/to vessels and before/after volumes.”
Publisher declares: read-only yes · destructive no · open-world yes
5 inputs
- date_fromstring“Operations completed on or after this date.”
- date_tostring“Operations completed on or before this date.”
- owner_namestring“Owner name.”
- batch_namestring“Batch name.”
- winery_namestring“Winery name.”
vintrace_list_barrel_treatments
“Barrel move shipments / barrel treatments recorded in vintrace, with barrel states and treatment types.”
Publisher declares: read-only yes · destructive no · open-world yes
5 inputs
- treatmentstring“Only this treatment.”
- modified_sincestring“Only records modified after this time.”
- modified_beforestring“Only records modified before this time.”
- limitinteger“Results per page, 1-200 (vintrace default 10).”
- offsetinteger“Index of the first result (default 0).”
vintrace_list_blocks
“List vineyard blocks (grower, vineyard, region, variety).”
Publisher declares: read-only yes · destructive no · open-world yes
5 inputs
- idstring“Comma-separated block ids.”
- vintagestring“Vintage year (needed with include).”
- includestring“Extra parts to include, for example fruitPlacements (with vintage).”
- limitinteger“Results per page, 1-200 (vintrace default 10).”
- offsetinteger“Index of the first result (default 0).”
vintrace_list_block_assessments
“List vineyard block assessments (vine and fruit assessments by the viticulture team).”
Publisher declares: read-only yes · destructive no · open-world yes
6 inputs
- assessed_bystring“Filter by assessor: a vintrace user id (123), or ext:<external id>.”
- created_sincestring“Only assessments created after this time.”
- created_beforestring“Only assessments created before this time.”
- extra_fieldsstring“Extra fields to include, comma-separated (see the BlockAssessment fields).”
- limitinteger“Results per page, 1-200 (vintrace default 10).”
- offsetinteger“Index of the first result (default 0).”
vintrace_list_bookings
“List active fruit bookings (grape deliveries planned for a vintage) for one or more wineries: grower, block, variety, expected pick time and quantity.”
Publisher declares: read-only yes · destructive no · open-world yes
11 inputs, 2 required
- vintageintegerrequired“Vintage year, e.g.”
- winery_idsarrayrequired“vintrace winery ids (see vintrace_get_vessel_details_report for winery names/ids).”
- arrival_afterstring“Arrival after this time.”
- arrival_beforestring“Arrival before this time.”
- grower_namestring“Only this grower.”
- vineyard_namestring“Only this vineyard.”
- block_namestring“Only this block.”
- booking_numberstring“A vintrace booking number.”
- modified_sincestring“Added, changed or deactivated since this time.”
- limitinteger“Results per page, 1-200 (vintrace default 10).”
- offsetinteger“Index of the first result (default 0).”
vintrace_list_bulk_intakes
“List bulk wine/juice intakes (wine bought or received in bulk) with batch, volume, owner and cost.”
Publisher declares: read-only yes · destructive no · open-world yes
5 inputs
- purchase_referencestring“Exact purchase reference (sent to vintrace as eq:<reference>).”
- modified_sincestring“Only records modified after this time.”
- modified_beforestring“Only records modified before this time.”
- limitinteger“Results per page, 1-200 (vintrace default 10).”
- offsetinteger“Index of the first result (default 0).”

Show 22 more tools

vintrace_search_fruit_intakes
“Fruit intake operations (grape deliveries weighed in at the winery): weights, grower, block, vineyard, vintage, docket numbers and metrics.”
Publisher declares: read-only yes · destructive no · open-world yes
13 inputs
- vintagestring“Vintage year.”
- grower_namestring“Grower name.”
- vineyard_namestring“Vineyard name.”
- block_namestring“Block name.”
- owner_namestring“Fruit owner name.”
- winery_namestring“Winery name.”
- delivery_docketstring“Delivery docket number.”
- intake_docketstring“Intake docket number.”
- recorded_afterstring“Recorded at or after this time.”
- recorded_beforestring“Recorded at or before this time.”
- modified_sincestring“Modified since this time.”
- max_resultsinteger“Results per page, 1-200.”
- first_resultinteger“Start index of the page (default 0; vintrace "first").”
vintrace_list_stock_dispatches
“List stock dispatch actions (bottled goods and dry goods sent out) with routes, items and shipping information.”
Publisher declares: read-only yes · destructive no · open-world yes
2 inputs
- limitinteger“Results per page, 1-200 (vintrace default 10).”
- offsetinteger“Index of the first result (default 0).”
vintrace_list_shipments
“List shipments created by Bulk Dispatch and inter-winery dispatch operations, with destination and wine details.”
Publisher declares: read-only yes · destructive no · open-world yes
8 inputs
- typestring“Operation type.”
- dispatch_typestring“Dispatch type name.”
- freight_codestring“Freight code name.”
- includestring“Extra wine details to include: allocations, metrics, composition, cost (comma-separated).”
- modified_sincestring“Only records modified after this time.”
- modified_beforestring“Only records modified before this time.”
- limitinteger“Results per page, 1-200 (vintrace default 10).”
- offsetinteger“Index of the first result (default 0).”
vintrace_list_cost_transactions
“Bulk wine cost movements between two times (cost of wine moved between batches and wineries), optionally for one winery or business unit.”
Publisher declares: read-only yes · destructive no · open-world yes
7 inputs, 2 required
- startstringrequired“Start of the period (required).”
- endstringrequired“End of the period (required).”
- winery_idinteger“Only this winery.”
- winery_namestring“Only the winery with this exact name.”
- business_unitstring“Only this business unit.”
- limitinteger“Results per page, 1-200 (vintrace default 10).”
- offsetinteger“Index of the first result (default 0).”
vintrace_list_brand_allocations
“List brand allocations of bulk wine (how much of a wine is promised to which brand), by status and vintage.”
Publisher declares: read-only yes · destructive no · open-world yes
5 inputs
- statusstring“Allocation status.”
- vintageinteger“Vintage year.”
- modified_sincestring“Only records modified after this time.”
- limitinteger“Results per page, 1-200 (vintrace default 10).”
- offsetinteger“Index of the first result (default 0).”
vintrace_get_purchase_order
“One purchase order with its lines, state and fulfilment.”
Publisher declares: read-only yes · destructive no · open-world yes
1 input, 1 required
- purchase_order_idstringrequired“vintrace purchase order id.”
vintrace_list_inventory
“Stock on hand (bottled wine, dry goods, additives) up to a date: quantity, committed, on order and available per item, location, owner, tax class.”
Publisher declares: read-only yes · destructive no · open-world yes
6 inputs
- datestring“Report stock up to this date, excluding later changes.”
- stock_typestring“Stock type, for example Wine batch, Additive, Closure, Glass/Container, Case x12.”
- owner_namestring“Only this owner's stock.”
- breakout_costingboolean“Break out each item's costs by category (needs the permission).”
- maxinteger“Results per page, 1-200 (sent as vintrace's "max").”
- firstinteger“Start index of the page (default 0; vintrace "first").”
vintrace_lookup_stock_item
“Find one stock item by code (matched against the start of the code) or by id: type, unit, owner, accounts, tax class and sub-components.”
Publisher declares: read-only yes · destructive no · open-world yes
2 inputs
- codestring“Stock item code (start of code).”
- idinteger“Stock item id.”
vintrace_get_stock_item
“One stock item by id with optional detail parts: expand=fields,distributions,notes,historyItems,rawComponents,bulkInfo.”
Publisher declares: read-only yes · destructive no · open-world yes
2 inputs, 1 required
- stock_item_idintegerrequired“vintrace stock item id (from vintrace_lookup_stock_item or vintrace_list_inventory).”
- expandstring“Comma-separated parts to expand: fields, distributions, notes, historyItems, rawComponents, bulkInfo.”
vintrace_list_stock_item_notes
“The notes recorded on a stock item.”
Publisher declares: read-only yes · destructive no · open-world yes
3 inputs, 1 required
- stock_item_idintegerrequired“vintrace stock item id.”
- first_resultinteger“Start index of the page (default 0; vintrace "first").”
- max_resultinteger“Notes per page, 1-200.”
vintrace_list_products
“List wine products as they sit in vessels: batch code, vessel, volume, colour, state and the latest lab metrics (TSO2, pH, Brix...).”
Publisher declares: read-only yes · destructive no · open-world yes
4 inputs
- barcodestring“A vessel code or asset id.”
- skip_metricsboolean“Leave out the metric measurements.”
- maxinteger“Results per page, 1-200 (sent as vintrace's "max").”
- firstinteger“Start index of the page (default 0; vintrace "first").”
vintrace_get_product
“One wine product by id (or by vessel barcode) with its vessel, volume and metrics.”
Publisher declares: read-only yes · destructive no · open-world yes
2 inputs, 1 required
- product_idintegerrequired“vintrace product id.”
- barcodestring“A vessel code or asset id.”
vintrace_list_sales_orders
“List sales orders with customer, status, price list, line items, totals and invoice date.”
Publisher declares: read-only yes · destructive no · open-world yes
10 inputs
- statusstring“Sales order status.”
- customer_namestring“Customer name.”
- starts_withstring“Order name starts with this.”
- start_datestring“Orders on or after this date.”
- end_datestring“Orders on or before this date.”
- invoice_start_datestring“Invoiced on or after this date.”
- invoice_end_datestring“Invoiced on or before this date.”
- external_transaction_idstring“External transaction id linked to the order.”
- maxinteger“Results per page, 1-200 (sent as vintrace's "max").”
- firstinteger“Start index of the page (default 0; vintrace "first").”
vintrace_get_sales_order
“One sales order by id, or by order code (for example VSO20): customer, items, prices, taxes and status.”
Publisher declares: read-only yes · destructive no · open-world yes
2 inputs
- sales_order_idinteger“vintrace sales order id.”
- codestring“Sales order code, e.g.”
vintrace_list_parties
“List parties: customers, growers, suppliers and owners, individuals or organisations, with address, phone and email.”
Publisher declares: read-only yes · destructive no · open-world yes
4 inputs
- starts_withstring“Surname (individuals) or company name starts with this.”
- categorystring“Party category (default All).”
- maxinteger“Results per page, 1-200 (sent as vintrace's "max").”
- firstinteger“Start index of the page (default 0; vintrace "first").”
vintrace_get_party
“One party (customer, grower, supplier, owner) by id, or by exact name.”
Publisher declares: read-only yes · destructive no · open-world yes
2 inputs
- party_idinteger“vintrace party id.”
- namestring“Exact party name.”
vintrace_get_work_order
“One work order by id: every job with its steps, summary text, status and assignee.”
Publisher declares: read-only yes · destructive no · open-world yes
1 input, 1 required
- work_order_idintegerrequired“vintrace work order id (the number, not the TWL code).”
vintrace_list_work_orders_v6
“Work orders from the operator's point of view (what is waiting for me / unassigned), with job counts, status and scheduled dates.”
Publisher declares: read-only yes · destructive no · open-world yes
8 inputs
- assigned_tostring“Assignment filter (default AVAILABLE_TO_ME).”
- statestring“Status filter (default ANY).”
- from_datestring“Scheduled on or after this date.”
- to_datestring“Scheduled on or before this date.”
- starts_withstring“Work order name starts with this.”
- winery_idinteger“Only this winery.”
- maxinteger“Results per page, 1-200 (sent as vintrace's "max").”
- firstinteger“Start index of the page (default 0; vintrace "first").”
vintrace_search_items
“Look up names and ids of one kind of item: growers, owners, blocks, varietals, vintages, regions, programs, batches, products, tanks, barrels, bins and more.”
Publisher declares: read-only yes · destructive no · open-world yes
4 inputs, 1 required
- typestringrequired“The kind of item to list.”
- starts_withstring“Name starts with this.”
- exact_matchboolean“True: the name must equal starts_with (default is a like match).”
- firstinteger“Start index of the page (default 0; vintrace "first").”
vintrace_add_stock_item_note
“WRITE: adds a new note to a vintrace stock item (visible to everyone in the winery, recorded under the token's user).”
Publisher declares: read-only no · destructive no · idempotent no · open-world yes
3 inputs, 2 required
- stock_item_idintegerrequired“vintrace stock item id.”
- detailstringrequired“The note text.”
- subjectstring“Optional subject line.”
vintrace_assign_work_order
“WRITE: assigns a work order to the token's own vintrace user (or to assign_operator_id), so it shows up in that operator's list.”
Publisher declares: read-only no · destructive yes · idempotent yes · open-world yes
4 inputs, 1 required
- work_order_idintegerrequired“vintrace work order id.”
- job_idinteger“Only this job of the work order.”
- assign_operator_idinteger“vintrace user id to assign to (default: the token's user).”
- reassignboolean“Reassign even if it is already assigned to another operator (default false).”
vintrace_deactivate_booking
“WRITE: deactivates a fruit booking so it no longer counts as an active booking (the record is kept; it is not deleted).”
Publisher declares: read-only no · destructive yes · idempotent yes · open-world yes
1 input, 1 required
- booking_idstringrequired“vintrace booking id.”

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-10-24.

How well are its tools described?

Features #4 and #5

How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.

Descriptions

AI reading of each description

No AI reading was available for this server's tools (the two runs did not agree, or the listing was not reviewed).

Counted from the listing

Parameters with a description: 100% of 174
Tools with a description: 100% of 34
Typical description length: 194 characters

The tool set

Counted from the listing

Tools: 34
Size of the list: about 9,689 tokens for an agent to load (characters ÷ 4)
Naming: 34 of 34 names use snake_case

AI reading: easy to mix up

No pair found.

The AI items cover 0 of 34 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.

How do I add it to my client?

Config from the registry entry

From the remote endpoint (Streamable HTTP)

We connected to this URL on 2026-10-24 (a read-only session: no tool was called).

Add to CursorAn install link in the format Cursor documents, holding the Cursor config below.

Claude Desktop or claude.ai

Settings → Connectors → Add custom connector, then paste:
https://vintrace.usefulapi.io/mcp

Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json

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

VS Code · .vscode/mcp.json

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

VS Code (command line) · Bash or zsh terminal (macOS, Linux)

code --add-mcp '{"name":"vintrace","type":"http","url":"https://vintrace.usefulapi.io/mcp"}'

Claude Code

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

Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+

npx @modelcontextprotocol/inspector@2.11.0 --server-url https://vintrace.usefulapi.io/mcp --transport http

The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

Does the registry listing match what we found?

Feature #6

The registry verifies a package once, when it is published, and does not re-check it. A difference below is about the listing, not a judgement of the publisher.

Registry says	We found	Result	Source · date
Remote endpoint vintrace.usefulapi.io/mcp	Session opened	matches	our test · 2026-10-24
No credential declared as required	Opened a session without any credential	matches	our test · 2026-10-24
Repository github.com/m190/usefulapi-mcp	Opens publicly	matches	api.github.com · 2026-10-24

Who made it?

Feature #7 · lineage

Facts about the publisher. We do not turn them into a trust score.

Namespace: io.usefulapi · 409 servers
GitHub owner: a personal account (m190)

Repository: github.com/m190/usefulapi-mcp
Stars: 0
Repository age: 91–180 days
Last push: 0–30 days ago
Archived: no

Source: the registry entry and api.github.com · 2026-10-24.

Publish this server? Run these checks against it yourself before release, from your own machine: a server the command starts, or your own server at its URL after a one-time proof that you control it: npx protocolprobe-selftest.

Choosing

Record checks

Public records · not a safety rating

4 of 4 record checks met · 4 do not apply · 1 not checked

MetRegistry entry is active and says how to run itActive, with a package or a remote address.
MetSource repository link opensThe linked GitHub repository is public.
MetRepository is not archivedNot archived.
MetCode pushed to the repository in the 90 days before our checkLast push 0-30 days before our check.
Not checkedRepository publishes a security policy (SECURITY.md)We did not read this repository's security policy.
Does not applyPackage names its licence with a standard (SPDX) identifierRemote server: it ships no package.
Does not applyThe version the registry lists can be installed and is not withdrawnRemote server: it ships no package.
Does not applynpm package carries build provenance (attestation)Remote server: it ships no package.
Does not applyNo known critical or high advisory in the package or its dependenciesRemote server: it ships no package.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-10-24. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating. How each check works · Leaderboards

Common questions about io.usefulapi/vintrace

Answered from the data above

Is io.usefulapi/vintrace safe to install?

We do not rate servers as safe or unsafe. 4 of its 4 applicable record checks are met (facts from public records, each listed on this page). What the records show: Its source repository opens publicly. Its repository had a push in the last 90 days. These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.

Does io.usefulapi/vintrace need an API key or sign-in?

It opened a session without any credential on 2026-10-24. The registry entry declares no required credential; no declaration is not a guarantee.

Has io.usefulapi/vintrace been security tested?

Partly. 3 of the 16 checks that apply to it were exercised. It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. No security verdict is published before verification.

Where is the source code of io.usefulapi/vintrace?

In github.com/m190/usefulapi-mcp, which opens publicly.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

What did we test, and what did we leave out?

18 checks · features #1, #2

Open without sign-in

It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. No security score is given; a check we did not run is never counted as passed.

The 18 checks at a glanceour test · 2026-10-24

Inventory: exercised
Hidden instructions: exercised
Real execution: not run · our policy
Secret leak: not run · nothing to check it against
Internal addresses: not run · our policy
Unconfirmed changes: not run · our policy
Bad input: not run · our policy
Model requests: not run · nothing to check it against
Sensitive questions: not run · nothing to check it against
Folder boundary: not run · our policy
Log leaks: not run · nothing to check it against
Hidden content: not run · nothing to check it against
Fake assistant turns: not run · an error was returned
Token passthrough: not applicable
Token audience: not applicable
Sign-in redirect: not run · our policy
Consent handling: not testable from outside
Sign-in metadata: exercised

3 exercised13 not run (reason given)2 not applicable

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 3 of the 16 checks that apply to it were exercised. We do not publish security-check outcomes for named servers.

Exercised · 3

1Inventory
tool-listReads the declared tools, resources and prompts.exercised
2Hidden instructions
description-poisoningLooks for hidden instructions in tool descriptions.exercised
18Sign-in metadata
oauth-url-schemeChecks the published sign-in metadata for unsafe URLs.exercised

Not run, with the reason · 13

3Real execution
real-executionCalls a tool and checks what really happens.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
4Secret leak
canary-leakPlants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
5Internal addresses
ssrfChecks whether a tool can be steered to internal addresses.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
6Unconfirmed changes
write-without-confirmationChecks whether tools that change data act without asking.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
7Bad input
error-handlingSends bad input and watches how the server answers.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
8Model requests
samplingChecks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
9Sensitive questions
elicitation-sensitive-dataChecks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
10Folder boundary
root-boundaryChecks whether the server reaches outside the folders it was given.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
11Log leaks
logging-side-channelChecks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
12Hidden content
audience-hidingChecks resources that hide content from the user.This check needs content the server returns, and nothing was read or called.not run · nothing to check it against
13Fake assistant turns
fake-assistant-turnChecks prompts that pose as the assistant's own words.The server returned an error when its prompts were read.not run · an error was returned
16Sign-in redirect
open-redirectChecks the sign-in redirect for abuse.Testing the sign-in redirect means sending probes to the operator's sign-in service, which we do not do.not run · our policy
17Consent handling
confused-deputyChecks consent handling when one service acts for another.Depends on the operator's own consent screen, which differs per server and cannot be tested from outside.not testable from outside

Does not apply to this server · 2

14Token passthrough
token-passthroughChecks whether the server forwards a user's token to other services.The server opened a session without sign-in, so there is no token flow to check.not applicable
15Token audience
token-audience-validationChecks whether tokens meant for another service are accepted.The server opened a session without sign-in, so there is no token flow to check.not applicable

Source: our own test, 2026-10-24, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.

What happened during the test?

Feature #8

The steps in order, as the test record holds them.

0 msStarted a read-only session with the server's remote endpoint
359 msConnected after 0 redirects. No credential was sent or needed.
Read the inventory: 34 tools, 0 resources, 1 prompt.
1,231 msFinished: 3 checks exercised.

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified

pending: added in the weekly update

listed 2026-10-24; not classified yet

Pricing modelAI-classified

pending: added in the weekly update

the website is not read yet

Programming language

JavaScript

api.github.com · 2026-10-24

Hosting type

remote (hosted by the publisher)

registry · 2026-10-24

MCP capability

prompts, tools

our test · 2026-10-24

Transport

streamable HTTP

registry · 2026-10-24

Required credentials

none declared

registry · no declaration is not a guarantee

Package registry

does not apply

remote-only server: no package is shipped, so there is no package registry

Freshness

0–30 days

registry updatedAt · 2026-10-24

Lifecycle status

active

registry · 2026-10-24

License class

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Integrity hash

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Signature / provenance

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Dependency advisories

does not apply

ships no package, so there are no dependencies to audit

Popularity

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Publisher signals

owner: a personal account · repository age: 91–180 days · stars: 0–9

api.github.com · 2026-10-24

Maintenance

active

api.github.com · 2026-10-24

Environment

the publisher's infrastructure

where it runs, from the hosting type

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “io.usefulapi/vintrace: MCP server record.” Data checked 2026-10-24. https://protocolprobe.com/mcp/servers/io.usefulapi/vintrace

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/io.usefulapi/vintrace)](https://protocolprobe.com/mcp/servers/io.usefulapi/vintrace)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here.

Write to hello@protocolprobe.com · corrections log · methodology