Vendor Signals
NPM · @PIPEWORX/MCP-VENDOR-SIGNALS · 2 COMPONENTS
Vendor documentation and changelog change-tracking as ACCOUNT SIGNALS (fleet #545).
Available components
Last scanned (4 hours ago)
Scores higher than 62% of npm servers
Category Marketing and SEO
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 & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-vendor-signals). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 7 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability67
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 575 tokens (~191/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 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
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
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.
- 30 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 29 Oct 26 79
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 5 Nov 2026 · Analysed npm/@pipeworx/mcp-vendor-signals@0.2.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | pipeworx-io/mcp-vendor-signals |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-vendor-signals/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3560934398 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:9430c31ddadb36dc3f91b13263918a80ecddab849c9f80da665f5b51e41bc8e7795178274320b98bbc7a39d13c6547c61f103e022631fa6a83ac57985 |
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 →
vendor_coverage ~128
Which software vendors are tracked for changelog and release activity, and how healthy each feed is — the vendor name, its domain, what kind of source is watched (changelog feed vs GitHub releases), when it was last polled successfully, and how many changes are on file. Call this before concluding a vendor has been quiet: a vendor that is not on this list has no data rather than no activity. Example: vendor_coverage({}); vendor_coverage({ vendor: "stripe" }). Keyless.
| Name | Type | Req | Description |
|---|---|---|---|
| vendor | string | – | Optional — check one vendor by name or domain |
No output schema declared.
No examples provided.
vendor_recent_changes ~218
What a software vendor shipped recently — changelog entries, release notes and product announcements with the date and a link to the source. Built for account research and outreach timing: "what did Stripe ship this month", "has Vercel released anything lately", "recent changes at supabase.com". Look the vendor up by name or by domain (the domain is what a CRM or target list joins on). Returns each change with its published date, title, summary and URL. Says explicitly whether a vendor is tracked-but-quiet or not tracked at all, because those mean different things. Example: vendor_recent_changes({ vendor: "stripe", days: 30 }); vendor_recent_changes({ vendor: "vercel.com" }). Keyless.
| Name | Type | Req | Description |
|---|---|---|---|
| days | number | – | Look-back window in days (default 30, max 365) |
| limit | number | – | Max changes to return (default 20, max 100) |
| vendor | string | yes | Vendor name or domain, e.g. "stripe" or "stripe.com" |
No output schema declared.
No examples provided.
vendor_signal_sweep ~174
Recent shipping activity across every tracked software vendor at once, newest first — a single sweep for "which of these accounts have been active this week". Use for prospecting and account prioritisation rather than researching one company: it surfaces which vendors shipped, how many changes each had, and the latest headline per vendor. Optionally narrow to a set of domains to match a target list. Example: vendor_signal_sweep({ days: 7 }); vendor_signal_sweep({ domains: ["stripe.com", "twilio.com"], days: 14 }). Keyless.
| Name | Type | Req | Description |
|---|---|---|---|
| days | number | – | Look-back window in days (default 7, max 90) |
| domains | array | – | Restrict to these vendor domains |
| limit | number | – | Max vendors to return (default 25, max 100) |
No output schema declared.
No examples provided.
How do I install the Vendor Signals MCP server?
Vendor Signals runs locally as an npm package, launched with npx -y @pipeworx/mcp-vendor-signals. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @pipeworx/mcp-vendor-signals
claude mcp add pipeworx-io-vendor-signals -- npx -y @pipeworx/mcp-vendor-signals
What is the Vendor Signals MCP server?
Vendor Signals is an MCP server listed in the public MCP registry as io.github.pipeworx-io/vendor-signals. Vendor documentation and changelog change-tracking as ACCOUNT SIGNALS (fleet #545). This page covers its npm package (@pipeworx/mcp-vendor-signals).
Is the Vendor Signals MCP server safe to use?
Vendor Signals scores 79 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Vendor Signals MCP server expose?
Vendor Signals exposes 3 tools: vendor_recent_changes, vendor_signal_sweep, vendor_coverage. Their descriptions and schemas cost roughly 520 tokens of context every time the server is loaded.
Is the Vendor Signals MCP server still maintained?
Vendor Signals is still listed as active in the MCP registry. We last reached this channel on 5 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 Vendor Signals MCP server under?
Vendor Signals declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.