Publisher · GitHub account
MCP servers published by entire-vc
2 servers in the official MCP Registry are published under the namespace io.github.entire-vc/ and have a page in this directory: 2 remote, reached by URL, and 1 run locally from a package (1 offer both). First published 2026-09-23; latest update 2026-09-24.
What this publisher publishes
Names under io.github.entire-vc/ can only be published by someone who signs in to the MCP Registry as the GitHub user entire-vc, or as a member of the GitHub organisation of that name. The name shows which GitHub account published the entry; it does not show that the account belongs to the company whose product a server works with.
- Namespace
io.github.entire-vc- Servers with a page
- 2
- Categories
- developer (1), productivity (1)
- Transports
- Streamable HTTP (2), SSE (HTTP + Server-Sent Events) (1), stdio (local process) (1)
- Package registries
- MCP Bundle (.mcpb) (1), OCI image (Docker) (1)
- Remote servers declaring a header
- 2 of 2
- Packages declaring environment variables
- 1 of 1
- Websites stated
- spark.entire.vc
- First published
- 2026-09-23
- Latest update
- 2026-09-24
Source repositories
The 2 repositories these servers state, with how many servers name each.
| Repository | Servers |
|---|---|
| github.com/entire-vc/evc-mesh-mcp | 1 |
| github.com/entire-vc/evc-spark-mcp | 1 |
All 2 servers, A to Z
| Server | Runs |
|---|---|
| Evc Mesh MCPTasks, comments, shared memory and handoffs for teams of people and AI agents, over MCP. | Remote & Local · HTTP, SSE, stdio |
| Spark - AI Assets MarketplaceSearch and fetch AI agents, skills, prompts and MCP connectors from the Spark marketplace. | 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