What your assistant can see
One workspace, chosen by the person who connects it, and no more than that person can open in Vendorroll: vendors, their documents, questionnaires and answers, risks, contracts, requests, sign-offs and the activity trail. It does this through 15 tools, each of which only reads.
| Tool | What it returns | Who can use it |
|---|---|---|
workspace_overview | Counts for the whole workspace: vendors by risk and stage, open and overdue documents, documents expiring in 30, 60 and 90 days, pending sign-offs, open renewals and the 30-day risk trend. | Every role |
list_vendors | Vendors with risk level and score, criticality, data access, owner, onboarding date and document counts. Can be filtered. | Every role |
get_vendor | One vendor in full: risk and score history, intake answers, owner, document reviewers, sign-offs with who decided and why, and the last 20 activity entries. | Every role |
vendor_documents | Each document a vendor must provide: its state, due and expiry dates, the file name, the reviewer's reason if it was rejected, and what the AI read from it. | Every role |
read_document | The text of one vendor document, by page range. Scans and images have no text. | Every role |
vendor_questionnaires | The questionnaires assigned to a vendor: state, dates, how many questions are answered, the reviewer and their comment. | Every role |
questionnaire_answers | Every question of one questionnaire with the vendor's answer, whether it raised a risk, follow-ups and replies, and the reviewer's comment. | Every role |
question_across_vendors | How every vendor answered one question. | Admin, Support, Operations, Compliance, Security |
questionnaire_templates | The workspace's questionnaire templates, or one template's questions with their risk rules. | Admin, Support, Operations, Compliance, Security |
list_risks | The risk register: reference, title, vendor, category, scores, owner, treatment, due and review dates. Can be filtered. | Every role |
get_risk | One risk in full: scores, treatment and plan, acceptance, and its history of who changed what, when and why. | Every role |
list_contracts | Contracts: vendor, value, billing, start, end and renewal dates, notice period, auto-renewal and status. | Every role |
activity_history | The audit trail, for the workspace or for one vendor: who did what, when, and the reason or comment given. | Admin, Support, Operations, Compliance, Security; every role for one vendor |
list_requests | Requests to take on a vendor and their approval state: purpose, estimate, who raised and who decided it, and why. | Every role except Member |
pending_signoffs | Sign-offs waiting on someone: what for, which rule, who it waits on, when it is due and whether it is overdue. | Every role except Member |
Text a vendor wrote, such as an answer or the words in an uploaded document, is marked as vendor text when it is handed over, and the assistant is told to treat it as information, never as instructions.
What it can never do
- Change anything. There is no tool that creates, edits, approves, rejects, waives, sends, invites, uploads or deletes. Every read also runs inside a read-only database transaction, so a write would be refused by the database itself.
- Approve or reject a document, questionnaire, request, sign-off or risk, or delete a vendor or a person.
- See other workspaces, or anything the person who connected it could not open in Vendorroll. An assistant is refused the areas that person’s role does not show in the sidebar.
What it never receives
- Vendor portal links or invitation links.
- Tokens or keys.
- File paths or storage links. Files appear by name only.
- Workspace settings or email setup.
- People’s email addresses. Team members appear by name, and an email address that appears inside any text is replaced with “[email hidden]”.
These are checked before every result leaves. If one is found, the whole result is withheld rather than partly masked.
Who can connect
- Off by default. No role can connect an assistant until a workspace admin allows it for that role.
- One connection, one workspace. The person picks the workspace when they connect, and can move the connection to another workspace they may use.
- The same permissions as the person. The assistant reads as them, through the same database rules the app uses.
- Revocable by the person and by any admin, at any time.
- Cut off at the next request if the connection is revoked, the role is no longer allowed, or the person leaves the workspace. These are checked on every call, not only when connecting.
Limits
- Lists return at most 50 items at a time, with a way to ask for the next page.
- Reading a document returns at most 10 pages and 40,000 characters in one call. Scans and images have no text to read.
- Each connection can make 60 calls a minute and 2,000 a day.
What gets logged
- Every call is written to your workspace’s audit log as an “AI assistant query”, with the assistant, the person whose access it used, what it asked for, and when.
- Reading a document is recorded the same way as opening the file.
- Allowing or removing a role’s permission, and revoking a connection, are logged too.
- A call that is refused, such as one after a connection was revoked, is not written to the log.
Your data
What you ask about, such as vendor details, documents and answers, is sent to the AI provider whose assistant you connect. Whether that provider uses it to train models depends on your own settings with them, and Vendorroll cannot change those. The screen where you allow a connection says this before you agree.
So that an assistant can read documents, Vendorroll keeps the text it extracts from the current version of each uploaded PDF. That text is deleted when the file is replaced by a newer accepted one or rejected, or when the file or its vendor is deleted. Older versions of a document stay on record, but their text is not kept. See also the privacy policy and the security overview.
How to connect
You need an admin to have allowed your role first (Team → AI assistants). The server address is:
https://demo.vendorroll.oopsie.tech/mcp
Claude
Settings → Connectors → Add custom connector. Paste the address, then Connect. Sign in to Vendorroll and choose the workspace.
ChatGPT
Settings → Apps & Connectors → Create (developer mode). Paste the address as the MCP server with OAuth, then Connect. Sign in to Vendorroll and choose the workspace.
What signing in shares
Connecting asks for the standard sign-in permissions below. They describe you, not your workspace; no workspace data is carried in them.
openid— Lets the assistant confirm which Vendorroll account signed in.profile— Your name and profile picture, as held by your Vendorroll sign-in.email— Your own email address, as held by your Vendorroll sign-in.