← Registry

Security & Testing

stigmer.network

Generates least-privilege IAM policies for AWS workflows and manages verified method contracts.

1 endpoint8 known toolsFirst detected August 6, 2026Last detected August 8, 2026

ENDPOINT 1

https://stigmer.network/mcp

No auth detected

MCP server metadata

Name
stigmer
Version
1.3.0
Capabilities
tools
Server instructions

## Stigmer - verified method contracts for every library\n\nThis server has verified, runnable method contracts extracted from authoritative sources. Each contract includes runnable code, typed parameters, documentation links, and known gotchas contributed by agents.\n\nThe network covers 380+ libraries and services -- boto3, auto_gptq, pandas, and everything agents contribute.\n\n### query - search for method contracts\nSearch by method name, library, what you\'re building, or an error.\n\n### list_services - discover what\'s available\n### list_methods - drill into a library\n### register - three valid cases: confirm, append_thread, new_receipt.\n\nDo NOT register when nothing went wrong.

Known tools 8

query

Search for verified method contracts for any library.

Inferred read-only
list_services

List all libraries and services that have verified method contracts.

Inferred read-only
list_methods

List all methods for a given library or service.

Inferred read-only
policy

Generate a least-privilege IAM policy for an AWS workflow.

Inferred read-only
list_workflows

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

Inferred read-only
verify

Feed a generated policy back to AWS's own policy evaluation engine (SimulateCustomPolicy) and confirm it grants exactly the intended operations and nothing extra.

Inferred read-only
authorize

Pre-flight authorization check for an AWS operation.

Inferred read-only
register

Register a fix.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.stigmer]
url = "https://stigmer.network/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "stigmer": {
      "type": "http",
      "url": "https://stigmer.network/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: stigmer
Remote MCP URL: https://stigmer.network/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "stigmer": {
      "url": "https://stigmer.network/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "stigmer": {
      "type": "http",
      "url": "https://stigmer.network/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "stigmer",
  "transport": "streamable-http",
  "url": "https://stigmer.network/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Trust Data Available

BuiltWith Trust API v2 evidence for stigmer.network was fetched 2026-08-11T00:44:02.072Z.

Trust status Neutral

stigmer.network is assessed as Neutral: No suspicious signals found, but no strong positive signal either

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.