io.github.Anioko/archiet-audit
PYPI · ARCHIET-AUDIT-MCP · SCANNED SEP 20
Submit architecture docs, get a consulting-grade traceability audit at a shareable URL
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs setuptools.build_meta at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 100 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability79
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 295 tokens (~98/item across 3 items; 3 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
- Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 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
How do I install the io.github.Anioko/archiet-audit MCP server?
io.github.Anioko/archiet-audit runs locally as a PyPI package, launched with uvx archiet-audit-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · archiet-audit-mcp
claude mcp add anioko-archiet-audit -- uvx archiet-audit-mcp
{
"mcpServers": {
"anioko-archiet-audit": {
"command": "uvx",
"args": [
"archiet-audit-mcp"
]
}
}
} {
"servers": {
"anioko-archiet-audit": {
"command": "uvx",
"args": [
"archiet-audit-mcp"
]
}
}
} codex mcp add anioko-archiet-audit -- uvx archiet-audit-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"anioko-archiet-audit": {
"type": "local",
"command": [
"uvx",
"archiet-audit-mcp"
],
"enabled": true
}
}
} openclaw mcp add anioko-archiet-audit --command uvx --arg archiet-audit-mcp
mcp_servers:
anioko-archiet-audit:
command: "uvx"
args: ["archiet-audit-mcp"] {
"McpServers": {
"anioko-archiet-audit": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"archiet-audit-mcp"
]
}
}
} assistant mcp add anioko-archiet-audit -t stdio -c uvx -a archiet-audit-mcp
{
"mcpServers": {
"anioko-archiet-audit": {
"command": "uvx",
"args": [
"archiet-audit-mcp"
]
}
}
} 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.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 −3
- Stability: pass → 0.80 functional
- 15 Sept 26 0
- Stability: 0.97 → pass security
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 −3
- Stability: pass → 0.80 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 20 Sept 2026 · Analysed pypi/archiet-audit-mcp@0.1.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | setuptools.build_meta |
Background: Why install scripts are a supply-chain risk →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
get_audit_limits ~34
Upload limits for the audit endpoint (max files, per-file and total size) — check before submitting large document sets.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_audit_status ~41
Fetch a previously submitted audit request by its token — status, inferred customer profile, and the report URLs.
| Name | Type | Req | Description |
|---|---|---|---|
| token | string | yes | audit request token |
No output schema declared.
No examples provided.
submit_architecture_audit ~220
Submit architecture documents to Archiet's audit factory and get back a consulting-grade traceability audit: a % can-generate / partial / cannot / custom breakdown across 22+ architecture concerns, severity-ranked gaps, and a 30/60/90-day adoption roadmap, at a shareable unguessable URL. Provide either local file paths (pdf/docx/md/txt/html) or pasted architecture text. NOTE: this uploads the documents to archiet.com for processing — the pipeline is deterministic (no LLM reads your docs) and the files are never exposed publicly, but do not submit material you may not transmit. Rate limit: one audit per minute per IP.
| Name | Type | Req | Description |
|---|---|---|---|
| company_name | string | – | optional — appears as the audit subject |
| string | yes | work email — the report link is associated with it | |
| files | array | – | local paths to architecture docs (pdf, docx, md, txt, html) |
| text | string | – | pasted architecture description (markdown), used when no files are given |
No output schema declared.
No examples provided.
What is the io.github.Anioko/archiet-audit MCP server?
io.github.Anioko/archiet-audit is an MCP server listed in the public MCP registry as io.github.Anioko/archiet-audit. Submit architecture docs, get a consulting-grade traceability audit at a shareable URL. This page covers its PyPI package (archiet-audit-mcp).
Is the io.github.Anioko/archiet-audit MCP server safe to use?
io.github.Anioko/archiet-audit scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. 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 io.github.Anioko/archiet-audit MCP server expose?
io.github.Anioko/archiet-audit exposes 3 tools: submit_architecture_audit, get_audit_status, get_audit_limits. Their descriptions and schemas cost roughly 295 tokens of context every time the server is loaded.
Is the io.github.Anioko/archiet-audit MCP server still maintained?
io.github.Anioko/archiet-audit is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.Anioko/archiet-audit MCP server under?
io.github.Anioko/archiet-audit declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.