Enigma Mcp Server

com.enigmaPublished by enigma.comOfficial publisherv1.0.1Updated Oct 24, 2026

An MCP server that provides access to trusted data about business identity and activity

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

A remote MCP server that gives an assistant access to trusted data about business identity and activity from Enigma.

What you can do
Look up trusted data about business identity and activity through Enigma's data service. The manifest lists no individual tools, so the exact operations are not documented here. Access is authenticated with an Enigma API key or an OAuth login.
When to use it
Useful when an assistant needs to check or enrich information about businesses, such as verifying a company's identity or activity, without leaving the conversation.
Requirements
A remote streamable HTTP endpoint at mcp.enigma.com. An Enigma account and either OAuth authentication or an Enigma API key supplied in the x-api-key header. Network access to the endpoint.
Before you install
The server requires an Enigma API key or OAuth login; treat the key as a secret and avoid exposing it in shared configurations or logs. Queries send business lookup details to Enigma's service, a third party. No write, payment or deletion behavior is documented.

Installation

In SourceWeft

  1. Open Enigma Mcp Server in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. 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.enigma%2Fenigma-mcp-server/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. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "enigma": {
      "type": "http",
      "url": "https://mcp.enigma.com/http"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.1LatestSep 16, 2026

Score

67% 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 listed15 pts

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

  • DescriptionRequired15 pts
  • Logo10 pts
  • 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.