AutEng MCP - Markdown Publishing & Document Share Links

The materials explicitly state that no keys or environment variables are required. No API token, account password, or other sensitive credential is requested, so the direct credential exposure and misuse surface appears low.

The tool connects to auteng.ai, and its core function is to publish Markdown documents as public share links. This implies user document content is sent to a remote service as part of normal operation and may become shareable. The egress is consistent with the stated purpose, but users should treat it as data leaving the local environment.

The system checks indicate that this tool executes code or starts a local process. For an MCP tool this is a normal capability, and the provided materials do not show requests for unusually broad system control unrelated to publishing Markdown, so this is caution rather than high risk.

By function, the tool likely needs to read Markdown documents to be published and may process embedded Mermaid diagram content; after publishing, that content becomes available via public links. The materials do not specify the access scope, local write behavior, or whether directory-level access is used, so data boundaries are not fully transparent, but there is no explicit over-permission red flag in the provided facts.

Positive signals include its presence in the official registry, official-source status, and updates within the last year, all of which reduce risk. Negative factors are the absence of an open-source repository, no declared license, no README, and near-zero community adoption, which limit auditability and transparency; however, the available facts are still insufficient to classify it as high risk.