Bragproof

← Reports

vsp360-mcp

Starts with no setup0.1.31npm

Installed, started with no arguments, no environment and no input, and listed its tools. Run 2026-11-16.

Needs to start: nothing
Returns a result when called with no setup: 1 of 1 tool tried
Contacts while installing and starting: nothing

3tools listed
0hosts contacted
0files written
0.2 sto start
97dependencies

What it contacted

Nothing besides the npm registry it was installed from. Watched from outside its sandbox while it was installed and started with no input. Its tools may still contact things when called.

Starting it

npx -y vsp360-mcp@0.1.31

Installing a package runs its code. Use a sandbox for anything you have not read.

Calling its tools

1 tool that takes no input and looks read-only was called once with nothing. 1 returned a result.

vsp360_list_operationsReturned a result under 0.1 s · 5,210 characters

During the calls it contacted nothing it had not already contacted.

Only tools whose names read like looking something up, with no required input, are tried, five at most. Tools that need input, and anything that sounds like it changes or sends something, are not called.

What its tools tell an agent

In the tool descriptions, nothing that talks about the user, other tools or private files, or uses hidden characters.

Found by simple pattern rules in each tool's description (up to 3,000 characters), quoted as written. Parameter descriptions are not scanned. A clean result is not a safety review.

Tools

vsp360_list_operations tag, query, limit
Browse the VSP 360 REST API. With no arguments, lists the API areas (tags) and how many operations each has. With `tag` and/or `query`, lists matching operations (operationId, method, path, summary). Use this first to find the operationId you need, then vsp360_describe_operation and vsp360_call_operation. Operations marked [write] are blocked because the server runs read-only.
vsp360_describe_operation operationId, resourceType
Show everything needed to call one VSP 360 operation: method and path, required permissions and prerequisites, parameters, request body schema and response schema.
vsp360_call_operation operationId, params, body, files, all_pages, max_pages, save_to
Call any VSP 360 REST API operation by operationId. Authentication is handled automatically. Pass path, query and header parameters by name in `params`, and the JSON request body in `body`. Collections are paginated with limit/offset (max 100 per page); set all_pages to follow the `next` link. Binary responses (ZIP, gzip, CSV downloads) are saved to the download folder and the file path is returned. Only read operations are allowed; the server runs read-only.

Descriptions are the package's own words, cut at 3,000 characters. Treat them as data.

Install facts

LicenseMIT
Needsnode >=22.19.0
Sourcegithub.com/visubramaniam/vsp360-mcp
Install scriptsNone declared by it or anything installed with it.
Tarballsha512-Z3HUz/qxMOHpYD0KPZTf3Stn1gLpofecAPdK359XxT6wKKQZ9QPWbZTNVGM+ZfxWEOhxISh0uj/+34F99awO2Q==

Check this report yourself

This site did not write the report. A public job on a GitHub-hosted machine did: the run, from this commit of the open-source runner. GitHub signed a token that names that job and the hash of the report, so any edit since would show.

Show it on your README

Bragproof: Starts with no setup

[![Bragproof](https://bragproof.smaverk.com/badge/vsp360-mcp.svg)](https://bragproof.smaverk.com/r/vsp360-mcp)

New version out? Ask for a fresh report.