# Stigmer (remote · stigmer.network)

Execution graph of AWS: verified contracts, least-privilege IAM policies, pre-flight authorization.

- Trust score: 54/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-09

## Components

- remote · `stigmer.network`: 54/100 (this document), [markdown](https://verifymcp.io/servers/network-stigmer-stigmer-mcp/stigmer.md), [page](https://verifymcp.io/servers/network-stigmer-stigmer-mcp/stigmer)

## Channel facts

- Endpoint: `https://stigmer.network/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.2.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-09.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 8 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 54/100
  - AI-judged instruction clarity (fair).
  - Context-footprint check failed: tool/resource definitions use about 913 tokens (~114/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 10/100
  - Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 83/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 50% of tool parameters carry a description.
- **Capabilities**: 20/100
  - Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http network-stigmer-stigmer-mcp https://stigmer.network/mcp
```

### Codex

```toml
[mcp_servers.network-stigmer-stigmer-mcp]
url = "https://stigmer.network/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "network-stigmer-stigmer-mcp": {
      "type": "remote",
      "url": "https://stigmer.network/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add network-stigmer-stigmer-mcp --url https://stigmer.network/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  network-stigmer-stigmer-mcp:
    url: "https://stigmer.network/mcp"
```

### Other

```json
{
  "mcpServers": {
    "network-stigmer-stigmer-mcp": {
      "type": "http",
      "url": "https://stigmer.network/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-08 (score 54, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-07 (score 53, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-08-06 (score 53)

First indexed and scored.

## MCP tools (8)

### `query` (~126 tokens)

Search for verified method contracts for any library. Pass any text -- library name, method, what you're building, or an error you hit.

Input parameters:

- `error_type` (string): (deprecated -- use query instead) Error type if searching by error
- `limit` (integer)
- `packages` (array)
- `query` (string): What are you looking for? A method name, a library, an error message, or what you're building. Examples: s3 put_object, auto_gptq import, pandas merge, ImportError peft.
- `sig` (string)

### `list_services` (~33 tokens)

List all libraries and services that have verified method contracts. Use this first to discover what's available, then query for specific methods.

### `list_methods` (~47 tokens)

List all methods for a given library or service. Use after list_services to drill into a specific one.

Input parameters:

- `service` (string, required): Library or service name. Get these from list_services first.

### `policy` (~126 tokens)

Generate a least-privilege IAM policy for an AWS workflow. Pass a named workflow, explicit IAM actions, or a description. Returns the exact policy with confidence tier and any unresolved operations.

Input parameters:

- `description` (string): Describe the workflow (e.g. 'upload a large file to S3 with KMS')
- `operations` (string): Explicit IAM action strings or SDK symbols, comma-separated (e.g. 's3:PutObject,s3:GetObject')
- `workflow` (string): A named workflow from list_workflows (e.g. 's3-multipart-kms')

### `list_workflows` (~24 tokens)

List the curated named workflows that can generate least-privilege IAM policies.

### `verify` (~131 tokens)

Feed a generated policy back to AWS's own policy evaluation engine (SimulateCustomPolicy) and confirm it grants exactly the intended operations and nothing extra. Returns verified (True|False|unknown), grants_all, grants_extra. Requires AWS credentials; without them verified=unknown with the reason. Wildcarded operations are expanded to concrete actions first.

Input parameters:

- `operations` (string): Intended IAM actions, comma-separated. Required if policy is provided.
- `policy` (string): Optional. A complete IAM policy JSON document to verify.
- `workflow` (string): A named workflow from list_workflows to generate and then verify

### `authorize` (~175 tokens)

Pre-flight authorization check for an AWS operation. Resolves the IAM actions the operation requires, then asks AWS's own policy simulator (SimulatePrincipalPolicy) whether the current role (or a given principal) allows them. Returns resolution (exact|partial|unresolved) and evaluation (allowed|denied|unknown) as separate fields. Requires AWS credentials; without them evaluation=unknown with the reason.

Input parameters:

- `operations` (string): IAM action strings or SDK symbols, comma-separated (e.g. 's3:PutObject' or 's3.PutObject')
- `principal_arn` (string): Optional. IAM role/user ARN to simulate against. Defaults to the current caller via sts:GetCallerIdentity.
- `workflow` (string): A named workflow from list_workflows (e.g. 's3-multipart-kms')

### `register` (~101 tokens)

Register a fix. Three actions: confirm (it worked), append_thread (variant worked), new_receipt (nothing matched, I fixed it).

Input parameters:

- `action` (string, required)
- `env` (string)
- `error` (string)
- `error_class` (string)
- `fix` (string)
- `library` (string, required)
- `receipt_sig` (string)
- `symbol` (string, required)
- `version` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/network-stigmer-stigmer-mcp/stigmer#diagnostics

## Score history

- 2026-08-09: 54
- 2026-08-08: 54
- 2026-08-07: 53
- 2026-08-06: 53

## Links

- Remote endpoint: https://stigmer.network/mcp
- Repository: https://github.com/LNSHRIVAS/stigmer
- Website: https://stigmer.network/
- Changelog RSS feed: https://verifymcp.io/servers/network-stigmer-stigmer-mcp/stigmer.xml
- Changelog JSON feed: https://verifymcp.io/servers/network-stigmer-stigmer-mcp/stigmer.json
- HTML version of this page: https://verifymcp.io/servers/network-stigmer-stigmer-mcp/stigmer