mcp-vendor-signals (pipeworx-io/mcp-vendor-signals) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 3 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
C
Emerging
74/100

mcp-vendor-signals

Vendor documentation and changelog change-tracking as ACCOUNT SIGNALS

→ pipeworx-io/mcp-vendor-signals· listed on github_repo_search

Emerging. No concerning findings. Grades remain capped until the project builds reputation through adoption. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

pipeworx-io

Source: github_repo_search

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

⚡ Connect GitHub for Live Monitored

Install from

GitHub

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// key findings
✅
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
✅
Open source with a license and README
Anyone can audit the code, the license is declared, and the publisher documents what it does.
// tools this server exposes3 tools

These names and descriptions are the publisher's own, read from the source code. We print them as written. Our assessment is the findings above, not this list.

vendor_recent_changes

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". Loo…

vendor_signal_sweep

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 …

vendor_coverage

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…

// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

3/3 tools missing one or more hints — vendor_recent_changes (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); vendor_signal_sweep (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); vendor_coverage (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint). OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Tests exist

No test files found

Add tests that exercise each declared tool.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 3 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Score](https://m8ven.ai/badge/mcp/pipeworx-io/mcp-vendor-signals)](https://m8ven.ai/mcp/pipeworx-io/mcp-vendor-signals)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: cf34dc9a0f75a93d514363dd9b676c7218281387
code hash: f68d1fcad22787f595c692112925dc5e888568922ee8ff9fb26d2a6394b6d9dc
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client