Stigmer

REMOTE · STIGMER.NETWORK · SCANNED AUG 9

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

Available components

54 54 Trust /100

Trust breakdown (6 categories)

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. How we score →

Endpoint Security57

The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
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. See how to fix → View diagnostics → Unverified
HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail

Transport & Reachability100

Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass

Schema Quality & AI Usability54

AI-judged instruction clarity (fair).Partial
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. See how to fix → Fail
Usage-examples check failed: none of the tools include examples. See how to fix → Fail

Stability & Change Management10

Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial

Tool Coverage83

100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
50% of tool parameters carry a description.Partial

Capabilities20

Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · stigmer.network

Claude Codex opencode OpenClaw Hermes Other

# add to Claude Code

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

# ~/.codex/config.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
    }
  }
}

# add to OpenClaw

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

# ~/.hermes/config.yaml

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

// mcp.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 we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

8 Aug 26 +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.
7 Aug 26 0
- Stability: unverified → 0.03 ▲ functional
6 Aug 26 53

First indexed and scored.

Show 2 earlier entries Hide earlier entries

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 9 Aug 2026 · Probed https://stigmer.network/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject	Issuer	Valid from	Valid until	Key	Signature	Serial
CN=stigmer.network	CN=YE1,O=Let's Encrypt,C=US	22 Jul 2026	20 Oct 2026	ECDSA 256	ECDSA-SHA384	5d44437810f74e3cee66ed092703724afa6
SANs: stigmer.network
CN=YE1,O=Let's Encrypt,C=US (CA)	CN=Root YE,O=ISRG,C=US	3 Sept 2025	2 Sept 2028	ECDSA 384	ECDSA-SHA384	5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA)	CN=ISRG Root X2,O=Internet Security Research Group,C=US	13 May 2026	2 Sept 2032	ECDSA 384	ECDSA-SHA384	872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA)	CN=ISRG Root X1,O=Internet Security Research Group,C=US	13 May 2026	2 Sept 2032	ECDSA 384	SHA256-RSA	6c8f1dc727c7117f7baf853ac980f9cd

DNSSEC insecure

Validation of stigmer.network. — Not signed

Zone	DS	Keys	Algorithms	Outcome
.	trust_anchor	20326, 38696	8, 8	Verified
network.	present	40414	8	Verified
stigmer.network.	absent			Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation

Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result	No authorisation required
HTTP status	200

Header	Value
x-content-type-options	nosniff
x-frame-options	DENY

Transports 2 probes

Transport	URL	Outcome	Status	Location
streamable-http	https://stigmer.network/mcp	Verified	200
http (plaintext)	http://stigmer.network/mcp	HTTPS enforced	308	https://stigmer.network/mcp

MCP tools · 8 exposed · ~763 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.

Tool Tokens

authorize ~175

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 Output Examples

Name	Type	Req	Description
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')

No output schema declared.

No examples provided.

list_methods ~47

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

Input Output Examples

Name	Type	Req	Description
service	string	yes	Library or service name. Get these from list_services first.

No output schema declared.

No examples provided.

list_services ~33

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

Input Output Examples

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_workflows ~24

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

Input Output Examples

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

policy ~126

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 Output Examples

Name	Type	Req	Description
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')

No output schema declared.

No examples provided.

query ~126

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

Input Output Examples

Name	Type	Req	Description
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	–	–

No output schema declared.

No examples provided.

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

Input Output Examples

Name	Type	Req	Description
action	string	yes	–
env	string	–	–
error	string	–	–
error_class	string	–	–
fix	string	–	–
library	string	yes	–
receipt_sig	string	–	–
symbol	string	yes	–
version	string	–	–

No output schema declared.

No examples provided.

verify ~131

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 Output Examples

Name	Type	Req	Description
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

No output schema declared.

No examples provided.

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Score history · last 30 days

6 Aug 9 Aug