Browser Tools
vendorvigilance.net
An MCP server that provides site search and navigation tools for the VendorVigilance clinical trial vendor management website, including demo request access.
ENDPOINT 1
https://vendorvigilance.net
MCP server metadata
- Name
- WebMCP
Known tools 3
search-siteSearch VendorVigilance site content for information about clinical trial vendor management features, compliance, and use cases
Inferred read-onlynavigate-to-pageNavigate to a page on VendorVigilance. Available pages: /, /product, /about, /compliance, /contact, /blog, /use-cases/quality-assurance, /use-cases/clinical-operations, /use-cases/rd-sourcing, /use-cases/vendor-alliance-management, /use-cases/executive-leadership
Inferred read-onlyrequest-demoNavigate to the contact/demo request page for VendorVigilance clinical trial vendor management platform
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.webmcp]
url = "https://vendorvigilance.net"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"webmcp": {
"type": "http",
"url": "https://vendorvigilance.net"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: webmcp
Remote MCP URL: https://vendorvigilance.net
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"webmcp": {
"url": "https://vendorvigilance.net"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"webmcp": {
"type": "http",
"url": "https://vendorvigilance.net"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "webmcp",
"transport": "streamable-http",
"url": "https://vendorvigilance.net"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.