io.github.CollinJ0/vendorcheck
NPM · VENDORCHECK-MCP
Check a vendor (name, domain, email) for fraud signals and sanctions before an agent pays it.
Available components
Last scanned (19 hours ago)
Scores higher than 34% of npm servers
Category Security
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency6
- Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: the license (UNLICENSED) isn't a recognized OSI-approved license. See how to fix → Fail
- Actively maintained (last published 3 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability83
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 134 tokens (~134/item across 1 items; 1 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
- Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 1 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 0 to 3. That category is still filling its 30-day observation window: 0 days of observed history at the previous scan, 1 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 64
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Analysed npm/vendorcheck-mcp@0.1.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_vendor ~134
Check whether a vendor, invoice sender, or payee is legitimate BEFORE paying it or sharing sensitive data. Checks domain age, look-alike/impersonation domains, email security, HTTPS, website, US sanctions (OFAC) and SEC public-company records. Returns verdict allow | review | block with reasons. If verdict is not allow, do not pay without human confirmation.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | – | Company website domain, e.g. acme.com |
| string | – | Email address the request or invoice came from | |
| name | string | – | Company or person name as given on the invoice or request |
No output schema declared.
No examples provided.
How do I install the io.github.CollinJ0/vendorcheck MCP server?
io.github.CollinJ0/vendorcheck runs locally as an npm package, launched with npx -y vendorcheck-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · vendorcheck-mcp
claude mcp add collinj0-vendorcheck -- npx -y vendorcheck-mcp
What is the io.github.CollinJ0/vendorcheck MCP server?
io.github.CollinJ0/vendorcheck is an MCP server listed in the public MCP registry as io.github.CollinJ0/vendorcheck. Check a vendor (name, domain, email) for fraud signals and sanctions before an agent pays it. This page covers its npm package (vendorcheck-mcp).
Is the io.github.CollinJ0/vendorcheck MCP server safe to use?
io.github.CollinJ0/vendorcheck scores 66 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.CollinJ0/vendorcheck MCP server expose?
io.github.CollinJ0/vendorcheck exposes 1 tool: check_vendor. Their descriptions and schemas cost roughly 134 tokens of context every time the server is loaded.
Is the io.github.CollinJ0/vendorcheck MCP server still maintained?
io.github.CollinJ0/vendorcheck is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.CollinJ0/vendorcheck MCP server under?
io.github.CollinJ0/vendorcheck declares the UNLICENSED licence, which is not on the OSI-approved list. Read the terms before using it at work, and note this covers the source only, not the cost of any service it calls.