Archiet Audit MCP — architecture audit server for AI agents
mcp-name: io.github.Anioko/archiet-audit
Get a procurement-grade architecture audit from inside your AI coding agent. This MCP (Model Context Protocol) server lets Claude Code, Cursor, Windsurf — any MCP-capable agent — submit architecture documents (PDF, DOCX, Markdown, plain text, HTML) to Archiet's hosted audit factory and get back a consulting-grade traceability audit at a shareable, unguessable URL:
- % can-generate / partial / cannot / custom breakdown across 22+ architecture concerns (auth, multi-tenancy, audit logging, compliance controls, integrations, …)
- Severity-ranked gaps with evidence
- 30/60/90-day adoption roadmap
- A report URL you can forward to your team or procurement
The pipeline is deterministic — no LLM reads your documents — so the same documents always produce the same audit. Typical turnaround: ~15 seconds.
# Claude Code
claude mcp add archiet-audit -- python /path/to/server.py
Then ask your agent:
"Audit our architecture doc at ./docs/architecture.md with my work email."
Tools
| Tool | What it does |
|---|---|
submit_architecture_audit |
Upload docs (or pasted text) → audit report URL |
get_audit_status |
Poll a previously created audit by token |
get_audit_limits |
File count / size limits, checked before uploading |
What gets sent where (read this)
Unlike archiet-xray — which is fully local and never touches the
network — this server uploads the documents you submit to archiet.com
(or ARCHIET_BASE_URL for self-hosted instances). The report lives at an
unguessable URL; the uploaded files themselves are never exposed publicly.
Don't submit material you may not transmit. That network boundary is exactly
why this is a separate server from X-Ray rather than another tool in it.
Requirements
- Python 3.10+ — stdlib only, no dependencies to install
- A work email (the report link is associated with it)
- Rate limit: one audit per minute per IP
FAQ
How is this different from running X-Ray on my repo? X-Ray extracts the architecture your code actually has, locally. The audit factory evaluates the architecture your documents describe — coverage, gaps, and what it would take to generate the system — and produces a shareable report suitable for procurement and architecture review boards. Use both: X-Ray for ground truth, the audit for the deliverable.
Is the audit really free? Yes. It is Archiet's lead magnet: the free audit shows the traceability breakdown; the paid platform generates the missing pieces.
Can I point it at a self-hosted Archiet?
Set ARCHIET_BASE_URL to your instance's base URL.
Part of Archiet
Built by Archiet — the architecture-to-code platform that turns architecture specifications into production-ready applications with compliance documentation (SOC 2, ISO 27001, GDPR, HIPAA, PCI-DSS, DORA, NIS2) generated alongside the code.
MIT licensed.
Metadata
Release files for archiet-audit-mcp 0.1.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| archiet_audit_mcp-0.1.2.tar.gz | 8.1 kB | Without provenance | Details for archiet_audit_mcp-0.1.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| archiet_audit_mcp-0.1.2-py3-none-any.whl | Python 3 | none | any | Details for archiet_audit_mcp-0.1.2-py3-none-any.whl |
Total release size: 15.2 kB
Release files / archiet_audit_mcp-0.1.2.tar.gz
| Download URL | archiet_audit_mcp-0.1.2.tar.gz |
|---|---|
| Size | 8.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f61d4a1653f9de5f770befc5e58c37543922e5c0c646d679599f98ebef52cc3f
|
|
BLAKE2b-256 checksum How to use checksums |
ad82121e8e250aa56730ce5de04d28a50df46f82d84dad1b492ad65e36692610
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.2
|
Release files / archiet_audit_mcp-0.1.2-py3-none-any.whl
| Download URL | archiet_audit_mcp-0.1.2-py3-none-any.whl |
|---|---|
| Size | 7.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
6c394ebcb0f5ba454564f1f0e8f36bf407abeecbadf07e95bb4075ee5f9c45cc
|
|
BLAKE2b-256 checksum How to use checksums |
9626929d681059b6a3cb2443615965a04d5f8873b06ff8abe4fcc75a94f43207
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.2
|
Security for archiet-audit-mcp 0.1.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.