Skip to main content
Glama
StealthMark MCP Server

StealthMark MCP Server

Official

StealthMark MCP Server

A Model Context Protocol server that gives AI agents access to the StealthMark API over stdio.

Tools

Tool

What it does

API call

gateway_resolve

Resolves a website's machine-readable agent manifest and its exposed actions.

GET /v1/gateway/manifest/{domain}

gateway_invoke

Invokes an action a site declares in its agent manifest, by the action's slug.

POST /v1/gateway/invoke

kya_status

Looks up one of your organization's registered agents by ID.

GET /v1/agents/{id}

Related MCP server: io.github.readyagentsdev/readyagents

Configuration

Setting

Flag

Environment variable

Default

API base URL

--api-url=<url>

STEALTHMARK_API_URL

http://localhost:3001

API key, sent as a Bearer token

--api-key=<key>

STEALTHMARK_API_KEY

none

Flags take precedence over environment variables.

Build and run

npm ci
npm run build
node dist/index.js --api-url=<your StealthMark API URL>

Example MCP client entry:

{
  "mcpServers": {
    "stealthmark": {
      "command": "node",
      "args": ["/absolute/path/to/stealthmark-mcp-server/dist/index.js"],
      "env": {
        "STEALTHMARK_API_URL": "<your StealthMark API URL>",
        "STEALTHMARK_API_KEY": "<your API key>"
      }
    }
  }
}

Development

npm run typecheck
npm test

License

Apache-2.0. See LICENSE and NOTICE.

Available Tools

3 tools
gateway_invokeC

Invoke an action a site declares in its agent manifest, through the StealthMark API.

Inputs: domain (required), action_id (required), parameters (required).

gateway_resolveC

Resolve a website's machine-readable agent manifest and its exposed actions through the StealthMark API.

Inputs: domain (required).

kya_statusA

Look up one of your organization's registered agents (name, status, protocols) through the StealthMark API.

Inputs: agent_id (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.4/5.0

    Scored across 3 tools

    Disambiguation5/5

    The three tools have clearly distinct purposes: resolving a site manifest, invoking a declared action, and looking up agent status. An agent can easily choose between discovery, execution, and identity lookup without overlap.

    Naming Consistency4/5

    All names use snake_case and are readable, but the prefixes differ in style: gateway_resolve and gateway_invoke share a gateway_ action pattern, while kya_status uses an acronym-plus-noun pattern. This is a minor deviation rather than a confusing inconsistency.

    Tool Count5/5

    Three tools is well-scoped for a focused gateway server: resolve, invoke, and status lookup each cover a distinct part of the workflow. There is no obvious tool bloat or trivial single-tool surface.

    Completeness3/5

    The core resolve-then-invoke workflow is covered, and status lookup supports agent identity checks. However, the agent lifecycle is notably incomplete: there is no way to list registered agents, register a new agent, or update agent details, which may cause dead ends for administrative tasks.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers