Developer · Remote MCP server
VULK
Generate, edit, and deploy immersive 3D/WebGL web projects from any MCP assistant.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.devjoaocastro/vulk-mcp-server- Version
- 1.1.1
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP, stdio (local process)
- Package
- npm
- Published
- 2026-05-25
- Updated
- 2026-05-25
- Publisher
- devjoaocastro (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/devjoaocastro) · how
- Repository
- github.com/VULK-dev/vulk-mcp-server
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://mcp.vulk.dev/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 403)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 403
- Checked on
- 2026-10-05
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | vulk-mcp-server | 1.1.0 | stdio |
How to connect VULK
VULK is a remote MCP server: there is nothing to install. Its endpoint is https://mcp.vulk.dev/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
It can also run locally from a Node.js package published to the npm registry: vulk-mcp-server version 1.1.0. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y vulk-mcp-server@1.1.0. It reads the environment variable VULK_API_KEY (required, secret); set it in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"vulk-mcp-server": {
"command": "npx",
"args": [
"-y",
"vulk-mcp-server@1.1.0"
],
"env": {
"VULK_API_KEY": "<secret>"
}
}
}
}Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| VPS GuardianSecure SSH bridge for AI agents to observe and safely administer Linux VPSs. | Local · stdio |
| VPS OpsStdio MCP server that inspects and (with confirmation) mutates one VPS over SSH. | Local · stdio |
| Vsix Publish LintFind the package.json lines that stop vsce before you run the release build. | Local · stdio |
| VulcanusA validated Markdown memory vault your coding agent can recall, project by project. | Local · stdio |
| vuln-intelHosted CVE + bug-bounty-mechanic MCP: exploitation-first ranking, CVE fact-check, mechanic transfer. | Remote · HTTPLive check: sign-in required |
| VulnCheckVulnCheck exploit intelligence - CVE research, exploit data, advisories, and threat analysis. | Local · stdio |
| Vulnerability Intel MCPDefensive vulnerability intelligence search across public CVE/NVD and GitHub advisory APIs with CVSS. | Remote · HTTPLive check: sign-in required |
| Vulnerability ScannerTriggers GuardBee scans, queries findings, AI-assisted remediation guidance. | Local · stdio |