Enoki

ai.enokilabsPublished by enokilabs.aiOfficial publisherv1.0.0Updated Oct 24, 2026

Test your AI agents for security and safety weaknesses, and re-verify the fixes.

VerifiedStreamable HTTPWeb executableSecurity & Monitoring

Overview

AI-generated overview

Enoki is a remote MCP server that lets an assistant test AI agents for security and safety weaknesses and re-verify fixes.

What you can do
Test AI agents for security and safety weaknesses through the connected service, then re-verify the fixes. The manifest lists no individual tools, so the exact operations are not documented here; the stated purpose is agent security and safety testing with follow-up verification. It is a hosted remote endpoint reached over streamable HTTP rather than a local package.
When to use it
Use it when you are building or maintaining AI agents and want an assistant to probe them for security and safety weaknesses and confirm that remediation actually holds.
Requirements
A remote MCP client that supports streamable HTTP, connecting to the provider's hosted endpoint. OAuth authentication is required. No environment variables, headers or local packages are declared.
Before you install
OAuth grants the server access under your account, so review the scopes requested at sign-in. Testing agents may exercise them with adversarial inputs and could trigger real actions or costs in the target agent; confirm what the tests touch before running them. No tool list is published, so verify behavior before relying on it.

Installation

In SourceWeft

  1. Open Enoki 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/ai.enokilabs%2Fenoki/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": {
    "enoki": {
      "type": "http",
      "url": "https://mcp.enokilabs.ai/mcp"
    }
  }
}

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.0LatestOct 12, 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.