mcpbeat Sign in

Vendor Signals MCP Server

by pipeworx-io Your server? Claim it
answering

Vendor Signals is answering right now. Last checked 9 min ago. Last commit 17 Sep 2026.

Vendor documentation and changelog change-tracking as ACCOUNT SIGNALS

Uptime history 42 hours of history
42 hours agonow
100.0%
Uptime 24h
91 of 91 checks
—
Tools
hidden behind auth
155 ms
Response time
average over 24h
0
Stars
last commit 17 Sep 2026

Nothing serious here today

Today is the operative word: we check Vendor Signals every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 9 min ago.

run in your terminal
claude mcp add vendor-signals --transport http https://gateway.pipeworx.io/vendor-signals/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "vendor-signals": {
      "url": "https://gateway.pipeworx.io/vendor-signals/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.vendor-signals]
url = "https://gateway.pipeworx.io/vendor-signals/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "vendor-signals": {
      "url": "https://gateway.pipeworx.io/vendor-signals/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "vendor-signals": {
      "url": "https://gateway.pipeworx.io/vendor-signals/mcp"
    }
  }
}

Endpoints

URLTransportStateLatencyChecked
https://gateway.pipeworx.io/vendor-signals/mcp streamable-http answering 95 ms 9 min ago

Alternatives to Vendor Signals

same job, measured the same way
Deprecation MCP
by tsvillain

MCP server for cross-vendor API/SDK deprecation and breaking-change tracking

39 installs/wk local only
PandaDoc MCP Server
by pandadoc-mcp

PandaDoc MCP server for creating, sending, signing, and tracking PandaDoc documents.

answering
Okdoc
by okdocai

E-signature & document automation: create, send, track and sign documents with payments. 38 tools.

answering
Vonage Documentation MCP
by vonage

MCP server for Vonage API documentation, code snippets, tutorials, and troubleshooting.

7 tools answering
Fabricate
by fabricate

Public Fabricate pricing and documentation tools.

4 tools answering
Llmref
by llmref

Versioned documentation registry and semantic search for AI tools and coding assistants.

4 tools answering
Mason
by adrianczuczka

Engineering decisions, change impact, documentation audits, and CI evidence for coding assistants.

605 installs/wk local only
Urdb MCP
by getmystadmin

Search URDB for product integrity scores, enshittification events, and change tracking.

39 installs/wk local only

Vendor Signals — questions

Answers built from our own checks of this server.

Is Vendor Signals working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 155 ms. The bar chart above shows every period we have measured.
How do I connect Vendor Signals?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Vendor Signals need an API key?
No. Vendor Signals completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. This is what we observed, not what the docs claim.
How fast is Vendor Signals?
It answers our handshake in 155 ms on average, which is faster than 75% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is Vendor Signals open source?
Yes — it is published under the MIT licence, written in TypeScript and 0 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.