Camera compatibility test
Check whether your existing cameras are compatible with KSI, without any video leaving your network
A connector on a PC in the CCTV network tests the cameras and sends a technical report. The test is bounded, is removed by deleting a file, and every point can be verified. Your company's AI agent will be able to guide it through the KSI MCP Wizard.
Start the testThe essentials before you start
What gets installed
A single file, ksi-connector.mjs, on a PC in the CCTV network running Node.js 20 or later. It has no dependencies: the code that runs is the code you can read.
Which connections it opens
Outbound HTTPS connections (port 443) to mcp.ksivision.com only. Its local interface listens on 127.0.0.1 only. No inbound ports need to be opened.
Where passwords stay
Camera passwords are typed on the PC and never leave it. KSI never receives them.
Video and images
No video or images leave the network during the compatibility test. Camera thumbnails are shown on that PC only.
How to uninstall
Close the program and delete the file. If Node.js was installed only for the test, it can be uninstalled too. The connector's access expires after 30 days or when the account is revoked.
What does not change
Nothing is created in production before the interview. The connector works in a test environment.
How it works
- 01
Sign up with a company email
The person in charge signs up on the MCP Wizard with a company email and confirms a 6-digit code.
- 02
Connector on a PC in the CCTV network
The connector is downloaded, run on a PC that can reach the cameras, and linked to the account with a code approved in the dashboard.
- 03
Test and report
The connector tests each camera and the internet connection, then sends a report. The dashboard will show the result with traffic lights and suggested fixes, in a printable version for the IT team.
- 04
Interview
A web form completes the project context. It can be submitted without waiting for the connector.
- 05
Move to production
If the test and the interview are approved, a move to production can be requested. A member of the KSI team coordinates that step.
What leaves the network
During the test, only this data leaves the network:
- The compatibility report: the status of each test, the make, model and firmware of each camera, codec, resolution, fps, latency, upload speed and the port numbers the PC has open to the network.
- When pairing the connector: the PC name, its operating system and the connector version.
- In the speed test: up to 4 MB of random data that KSI counts and discards.
What does not leave
- Camera passwords.
- IP addresses: cameras are identified as cam-1, cam-2 and so on, and ports only by number and scope (whole network or one IP on the network).
- Video and images.
- Free text.
How to verify it
- The connector is a single JavaScript file with no dependencies: the IT team can read all of it before running it.
- The dashboard publishes the SHA-256 fingerprint of the current connector version to confirm the downloaded file is the original.
- The PC's connections can be checked with the usual operating system or firewall tools: they will only show outbound traffic on 443 to mcp.ksivision.com.
- The public technical sheet for the test is published in a format readable by people and AI agents.
For AI agents
The MCP Wizard exposes the test to an MCP-compatible AI agent. The agent connects with OAuth authorization from the person in charge and its tools are read-only: it can check the status, the report and the next steps, but it cannot request the move to production on its own.
- MCP Wizard URL
https://mcp.ksivision.com/api/wizard/mcp- Canonical technical sheet (JSON)
- https://mcp.ksivision.com/wizard/spec.json
The technical sheet is the current reference; if it differs from this page, the sheet prevails.
What happens next
With the report and the interview, the KSI team will review the case. If approved, the person in charge will be able to request the move to production from the dashboard, and the KSI team will coordinate it. If the report shows red cameras, the dashboard will indicate what to fix before continuing.
A bounded test before any decision
No new hardware, no inbound ports and no video leaving the network.
Start the test