Skip to main content
Glama
StealthMark MCP Server

StealthMark MCP Server

Official
README.md
# StealthMark MCP Server

A [Model Context Protocol](https://modelcontextprotocol.io) 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}` |

## 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

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

Example MCP client entry:

```json
{
  "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

```bash
npm run typecheck
npm test
```

## License

Apache-2.0. See [LICENSE](LICENSE) and [NOTICE](NOTICE).

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