{"id":"dejo1307-archmcp","name":"archmcp","homepage":null,"repo_url":"https://github.com/dejo1307/archmcp","category":"devtools","subcategories":[],"tags":["mcp","architecture-snapshot","code-analysis","static-analysis","graph","repo-discovery","agent-tools","go"],"what_it_does":"archmcp is a local MCP (Model Context Protocol) server that scans repositories and produces compact architectural snapshots (modules/symbols/dependencies/routes/architectural patterns). It runs as a stdio-based MCP server and can also generate one-shot snapshots via a CLI.","use_cases":["Provide upfront architecture context to an AI coding agent before it starts reading code","Generate cross-repo architectural context and query facts across multiple repositories (append mode)","Support architecture Q&A such as “what depends on what”, route discovery, and cycle/layer violation detection"],"not_for":["A full documentation site or visualization dashboard","Replacing code search/reading/grep when implementation details are needed","Running as a remote hosted service (it’s designed to run locally as an MCP server)"],"best_when":"You want to reduce “guessing” time for LLM-based code exploration by giving structured architectural facts up front, especially for unfamiliar or multi-language/multi-repo systems.","avoid_when":"You need a production-grade, authenticated network API for end users; this tool is intended for local developer/agent workflows.","alternatives":["Other MCP servers for codebase context (various community tools)","Static analysis/dep graph tools (e.g., language-specific graphers) combined with RAG over source","Documentation generators and architecture tools (e.g., code tour/static docs)","Custom scripts using tree-sitter/AST + graphing + LLM summarization"],"af_score":65.5,"security_score":47.5,"reliability_score":32.5,"package_type":"mcp_server","discovery_source":["github"],"priority":"high","status":"evaluated","version_evaluated":null,"last_evaluated":"2026-03-30T15:33:04.235546+00:00","interface":{"has_rest_api":false,"has_graphql":false,"has_grpc":false,"has_mcp_server":true,"mcp_server_url":null,"has_sdk":false,"sdk_languages":[],"openapi_spec_url":null,"webhooks":false},"auth":{"methods":[],"oauth":false,"scopes":false,"notes":"No authentication described in the README. As a local stdio MCP server, access is constrained to the local MCP client connection model."},"pricing":{"model":null,"free_tier_exists":false,"free_tier_limits":null,"paid_tiers":[],"requires_credit_card":false,"estimated_workload_costs":null,"notes":"No pricing information provided; repository appears to be open-source (MIT) and local-run."},"requirements":{"requires_signup":false,"requires_credit_card":false,"domain_verification":false,"data_residency":[],"compliance":[],"min_contract":null},"agent_readiness":{"af_score":65.5,"security_score":47.5,"reliability_score":32.5,"mcp_server_quality":85.0,"documentation_accuracy":75.0,"error_message_quality":0.0,"error_message_notes":null,"auth_complexity":100.0,"rate_limit_clarity":0.0,"tls_enforcement":90.0,"auth_strength":40.0,"scope_granularity":0.0,"dependency_hygiene":50.0,"secret_handling":60.0,"security_notes":"Intended as a local stdio MCP server (not a network service), so transport-layer concerns are reduced, but there’s no explicit guidance on sandboxing, filesystem access limits, or whether scanned content could include secrets. The README does not describe how credentials/secrets in scanned files are handled or redacted. Build-time/security hygiene depends on Go dependencies, but no CVE posture was provided.","uptime_documented":0.0,"version_stability":50.0,"breaking_changes_history":50.0,"error_recovery":30.0,"idempotency_support":"true","idempotency_notes":"Snapshot generation is described as producing artifacts to an output directory; regeneration after changes is recommended. Idempotency for repeated runs isn’t explicitly guaranteed, but it appears safe to rerun for the same input configuration.","pagination_style":"none","retry_guidance_documented":false,"known_agent_gotchas":["May ignore certain files by default (e.g., tests and docs, plus YAML/JSON configs). If relevant code/config is excluded, the snapshot may be incomplete.","Artifacts and caches are written to .archmcp by default; ensure paths and ignore rules match your workflow.","When doing multi-repo append mode, ensure you use consistent repo labeling and filters so queries target the right subset."]}}