Stigmer
REMOTE · STIGMER.NETWORK
Execution graph of AWS: verified contracts, least-privilege IAM policies, pre-flight authorization.
Available components
Last scanned (22 hours ago)
Scores higher than 59% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Cloud Infrastructure
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 → Why this is hard to 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 Usability72
- AI-judged instruction clarity (good).Pass
- 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
Checks we ran (12)
- TLS certificate
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation 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.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 9 Nov 26 0
- Stability: 0.97 → pass security
- 8 Nov 26 0
- Stability: pass → 0.97 functional
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 5 Sept 26 0
- Stability: 0.97 → pass security
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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 21 Nov 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 | 19 Nov 2026 | 17 Feb 2027 | ECDSA 256 | ECDSA-SHA384 | 669dc84005291ad493d474d7a2e897e2f64 |
| 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 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of stigmer.network. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| network. | DS published | 11416 | 8 | Verified |
| stigmer.network. | No DS | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
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 |
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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
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.
| 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.
| 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 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 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.
| 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.
| 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 ~101
Register a fix. Three actions: confirm (it worked), append_thread (variant worked), new_receipt (nothing matched, I fixed it).
| 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.
| 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.
How do I install the Stigmer MCP server?
Stigmer is a hosted endpoint at https://stigmer.network/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · stigmer.network
claude mcp add --transport http network-stigmer-stigmer-mcp 'https://stigmer.network/mcp'
What is the Stigmer MCP server?
Stigmer is an MCP server listed in the public MCP registry as network.stigmer/stigmer-mcp. Execution graph of AWS: verified contracts, least-privilege IAM policies, pre-flight authorization. This page covers its hosted endpoint (https://stigmer.network/mcp).
Is the Stigmer MCP server safe to use?
Stigmer scores 73 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Stigmer MCP server expose?
Stigmer exposes 8 tools: query, list_services, list_methods, policy, list_workflows, and 3 more. Their descriptions and schemas cost roughly 763 tokens of context every time the server is loaded.
Does the Stigmer MCP server require authentication?
No. We connected to Stigmer without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Stigmer MCP server still maintained?
Stigmer is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Stigmer MCP server?
VerifyMCP ran 12 checks on Stigmer, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Stigmer: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.