Vega

com.thetempleofdoom.vega-mcpPublished by vega-mcp.thetempleofdoom.comOfficial publisherv1.0.0Updated Oct 24, 2026

22 developer utilities: base64, hashes, JWT, JSON tools, unit conversion. Free, keyless.

VerifiedStreamable HTTPWeb executableDeveloper Tools

Overview

AI-generated overview

A free, keyless remote MCP server offering 22 developer utilities such as base64, hashing, JWT, JSON tools, and unit conversion.

What you can do
Vega exposes a set of 22 developer utilities through a remote MCP endpoint. The listed capabilities cover base64 encoding and decoding, hashing, JWT handling, JSON tools, and unit conversion. It is described as free and keyless, so no account or API key is needed to connect.
When to use it
Useful when an assistant needs quick, self-contained developer conversions or encodings, such as decoding base64, inspecting a JWT, formatting or validating JSON, computing a hash, or converting units, without setting up a local toolchain.
Requirements
A remote MCP client that can connect to the streamable HTTP endpoint. No packages, environment variables, headers, accounts, or API keys are declared.
Before you install
The endpoint is operated by a third party, so any data sent to it, including tokens or payloads passed to the JWT, hashing, or encoding tools, leaves your machine. Avoid sending secrets or sensitive production data. No authentication is declared, so the service is not tied to a verified identity.

Installation

In SourceWeft

  1. Open Vega in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.thetempleofdoom.vega-mcp%2Fvega/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "vega": {
      "type": "http",
      "url": "https://vega-mcp.thetempleofdoom.com/mcp"
    }
  }
}

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.0.0LatestSep 23, 2026

Score

56% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.