Publisher · domain
MCP servers published by vibgrate.com
2 servers in the official MCP Registry are published under the namespace com.vibgrate/ and have a page in this directory: 1 remote, reached by URL, and 1 run locally from a package. First published 2026-09-21; latest update 2026-10-02.
What this publisher publishes
Names under com.vibgrate/ can only be published by someone who has proved control of the domain vibgrate.com to the MCP Registry, through a DNS record or a file served over HTTP. The name shows who controls that domain; it does not show that the servers were reviewed.
- Namespace
com.vibgrate- Servers with a page
- 2
- Categories
- developer (1), productivity (1)
- Transports
- stdio (local process) (1), Streamable HTTP (1)
- Package registries
- npm (1)
- Remote servers declaring a header
- 0 of 1
- Packages declaring environment variables
- 0 of 1
- Websites stated
- vibgrate.com (2)
- First published
- 2026-09-21
- Latest update
- 2026-10-02
Source repositories
All 1 servers that state a repository name the same one.
| Repository | Servers |
|---|---|
| github.com/vibgrate/cli | 1 |
All 2 servers, A to Z
| Server | Runs |
|---|---|
| Ai ContextLocal-first MCP server: version-correct library docs, code map, and offline drift for your repo. | Local · stdio |
| vibgrate.comQuery your team's drift, vulnerability, and upgrade data from any AI assistant. OAuth 2.1, 51 tools. | Remote · HTTP |
Grouped by registry namespace, as the MCP Registry states it. A page here is not an endorsement and nobody pays to be listed: editorial policy · Before you connect a server