Template
MCP server inventory template
One row per server or skill, with the columns the checker reads. Fill it in, paste it back, and get the report.
Download the CSV template Download the filled example
The file has a header and four invented rows. Replace them. Nothing in the example is a real credential or a real company.
The columns
| Column | What to put in it |
|---|---|
name | The server or skill name, as you would say it in a review. |
type | server or skill. Anything else is read as a server. |
source | The registry page, release URL or repository you checked. |
publisher | The person or organisation that publishes it. |
version | The exact version you reviewed. Not latest, not a range. |
transport | stdio, http or sse. |
url | The endpoint for a remote server. |
command | The launch command for a local server, such as npx or docker. |
args | The arguments, separated by semicolons. |
permissions_filesystem | The paths a skill may touch, separated by semicolons. |
permissions_network | The hosts a skill may reach, separated by semicolons. |
sandbox | docker, container, microvm or none. Blank means not recorded. |
identity | The agent or service identity this entry uses. |
logging | The log destination, or false. |
allowed_tools | The tools this entry may call, separated by semicolons. |
auto_approve | true or false. |
instructions | The instruction text, or a short note on what it does. |
env | KEY=value pairs, separated by semicolons. Never a live secret. |
Why a CSV
Most harnesses do not export a manifest a reviewer can read. The CSV is the common shape a team can fill in from a spreadsheet, a ticket or a pull request, and it carries the same fields the JSON formats do. The checker reads it exactly as it reads a config.
Filling it in honestly
Leave a field blank when you do not know. The checker reports a blank as not recorded rather than assuming the safe value. A row with no source is a finding, not a gap in the tool.