AutEng MCP - Markdown Publishing & Document Share Links

REMOTE · AUTENG.AI · SCANNED AUG 3

Publish markdown documents as public share links with mermaid diagrams. Built by AutEng.ai

Available components

+6 this week 59 59 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 7 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 Usability49

AI-judged instruction clarity (fair).Partial
Context-footprint check failed: tool/resource definitions use about 1289 tokens (~184/item across 7 items; 7 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 Management27

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

Tool Coverage71

100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
0% of tool parameters carry a description.Fail
Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass

Capabilities100

Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

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 · auteng.ai

Claude Codex opencode OpenClaw Hermes Other

# add to Claude Code

claude mcp add --transport http ai-auteng-mcp https://auteng.ai/mcp

# ~/.codex/config.toml

[mcp_servers.ai-auteng-mcp]
url = "https://auteng.ai/mcp"

// opencode.json

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

# add to OpenClaw

openclaw mcp add ai-auteng-mcp --url https://auteng.ai/mcp --transport streamable-http

# ~/.hermes/config.yaml

mcp_servers:
  ai-auteng-mcp:
    url: "https://auteng.ai/mcp"

// mcp.json

{
  "mcpServers": {
    "ai-auteng-mcp": {
      "type": "http",
      "url": "https://auteng.ai/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.

3 Aug 26 +1

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

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
31 Jul 26 +2
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
30 Jul 26 +1

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
28 Jul 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.
27 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
26 Jul 26 52

First indexed and scored.

Show 6 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 3 Aug 2026 · Probed https://auteng.ai/mcp/docs · Declared URL https://auteng.ai/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject	Issuer	Valid from	Valid until	Key	Signature	Serial
CN=auteng.ai	CN=Amazon RSA 2048 M01,O=Amazon,C=US	16 Dec 2025	14 Jan 2027	RSA 2048	SHA256-RSA	d27ee2aa0bd26ae0b433f6837bc0340
SANs: auteng.ai
CN=Amazon RSA 2048 M01,O=Amazon,C=US (CA)	CN=Amazon Root CA 1,O=Amazon,C=US	23 Aug 2022	23 Aug 2030	RSA 2048	SHA256-RSA	77312380b9d6688a33b1ed9bf9ccda68e0e0f
CN=Amazon Root CA 1,O=Amazon,C=US (CA)	CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US	25 May 2015	31 Dec 2037	RSA 2048	SHA256-RSA	67f944a2a27cdf3fac2ae2b01f908eeb9c4c6

DNSSEC insecure

Validation of auteng.ai. — Not signed

Zone	DS	Keys	Algorithms	Outcome
.	trust_anchor	20326, 38696	8, 8	Verified
ai.	present	3799	8	Verified
auteng.ai.	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

Transports 3 probes

Transport	URL	Outcome	Status	Location
streamable-http	https://auteng.ai/mcp	Redirected	308	/mcp/docs
streamable-http · followed	https://auteng.ai/mcp/docs	Verified	200
http (plaintext)	http://auteng.ai/mcp	HTTPS enforced	301	https://auteng.ai/mcp

MCP tools — 7 exposed · ~1,109 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

auteng_docs_create ~241

Create a document in the agent's workspace. Requires EIP-191 wallet signature auth. Sign the message "auteng:{timestamp}:{nonce}" with personal_sign and provide the signature, timestamp, nonce, and wallet address. Args: wallet_address: 0x... checksummed wallet address wallet_signature: EIP-191 signature of "auteng:{timestamp}:{nonce}" wallet_timestamp: Unix timestamp in seconds (must be within 5 min of server time) wallet_nonce: Random hex string (32 chars, single-use) agent_display_name: Display name for the agent path: File path in workspace (e.g. "reports/q1.md"). Must end with extension. content: Markdown content (max 100 KB) title: Optional display title (derived from path if omitted)

Input Output Examples

Name	Type	Req	Description
agent_display_name	string	yes	—
content	string	yes	—
path	string	yes	—
title	—	—	—
wallet_address	string	yes	—
wallet_nonce	string	yes	—
wallet_signature	string	yes	—
wallet_timestamp	string	yes	—