Moretes Architect MCP

Was du damit machen kannst

Für diesen Server haben wir noch keine Zusammenfassung in einfacher Sprache geschrieben. Unten stehen die Fakten, die wir aus der Registry gelesen haben.

• Verbindung: Computer oder Cloud
• Transport: stdio, Streamable HTTP
• Kategorie: Entwicklertools

Installation

Wähle die KI-App, die du nutzt, und kopiere die Einstellungen.

Du brauchst

• Läuft in der CloudNichts zu installieren; die Verbindung läuft übers Internet
• npmNode.js installiert (für den Befehl npx)

Welche App nutzt du?

https://mcp.moretes.com/mcp

{
  "mcpServers": {
    "moretes-aws-architect": {
      "command": "npx",
      "args": [
        "-y",
        "moretes-aws-architect-mcp"
      ]
    }
  }
}

claude mcp add --transport http moretes-aws-architect https://mcp.moretes.com/mcp

claude mcp add moretes-aws-architect -- npx -y moretes-aws-architect-mcp

{
  "mcpServers": {
    "moretes-aws-architect": {
      "url": "https://mcp.moretes.com/mcp"
    }
  }
}

{
  "mcpServers": {
    "moretes-aws-architect": {
      "command": "npx",
      "args": [
        "-y",
        "moretes-aws-architect-mcp"
      ]
    }
  }
}

{
  "servers": {
    "moretes-aws-architect": {
      "type": "http",
      "url": "https://mcp.moretes.com/mcp"
    }
  }
}

{
  "servers": {
    "moretes-aws-architect": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "moretes-aws-architect-mcp"
      ]
    }
  }
}

https://mcp.moretes.com/mcp

Deine Auswahl bleibt in einem Cookie auf diesem Gerät; kein Konto nötig.

Diese Einstellungen werden aus dem Registry-Eintrag des Entwicklers erzeugt. Wenn in der README etwas anderes steht, folge der README.

Was er kann

Tool-Namen und -Beschreibungen genau so, wie der Server sie am 8. Nov. 2026 gemeldet hat. Geschrieben hat sie der Entwickler, nicht wir; wir zeigen sie als reinen Text.

• architect_panel

  Convene architect personas (solution, enterprise, business, data, infrastructure, software, AI, security, governance, FinOps) on a subject: each returns its questions, checks, deliverables and the workbench tools to call. Lens, not a verdict.

• code_review_architecture

  Heuristic architecture and security scan of source code pasted as text (any language): secrets, insecure calls, SQL built by concatenation, disabled TLS, hardcoded endpoints, missing timeouts and retry hazards. Not a linter or SAST replacement.

• dependency_manifest_review

  Review a dependency manifest (package.json, requirements.txt, pyproject, go.mod, pom.xml, Gemfile, Cargo.toml as text) for unpinned ranges, git or URL sources, wildcard versions and missing lockfile hints.

• requirements_check

  Turn a workload brief into explicit requirements, gaps and research questions. No inferred SLA or budget.

• architecture_pattern

  Select a reference architecture by explicit workload pattern; returns tradeoffs, questions and Mermaid. provider maps the AWS services to Azure, GCP, OCI or open source equivalents.

• service_compare

  Compare curated AWS service families against user constraints. No automatic winner or fabricated scores.

• decision_record

  Generate an ADR from explicit alternatives, decision and consequences. Does not invent acceptance.

• well_architected_review

  Organize evidence by six pillars. A met control without evidence is unknown, never certified.

• threat_model

  Create STRIDE review prompts for explicitly supplied assets and trust boundaries. Review aid, not a scanner.

• failure_rehearsal

  Design a controlled failure drill with observable success criteria and stop conditions; never executes it.

• capacity_plan

  Calculate partial capacity scenarios without inventing missing duration or payload. Label caller-reported provenance; no service sizing guarantee.

• cost_model

  Calculate an auditable scenario using caller-supplied unit rates and source URLs. Does not guess AWS prices or credit coverage.

• slo_budget

  Calculate an availability error budget for a chosen period.

• migration_plan

  Prepare phased discovery, pilot, migration and rollback gates; includes AWS Transform integration discovery.

• architecture_diagram

  Build Mermaid from explicit nodes and edges. Sanitizes labels and rejects dangling edges.

• implementation_plan

  Turn an architecture decision into a delivery checklist with validation gates.

• agent_tool_contract

  Design a per-operation authorization and recovery contract for an agent tool.

• c4_model

  Build C4 context or container diagrams (Mermaid) from explicit people, systems, containers and relations. Validates endpoints; no infrastructure discovery.

• sequence_diagram

  Build a Mermaid sequence diagram from participants and ordered messages, with optional activation, notes and alt/loop blocks. Rejects unknown participants.

• service_equivalents

  Map a cloud capability to equivalent managed services on AWS, Azure, Google Cloud, OCI and open source. Names as of the snapshot date; verify current naming, regions and pricing before deciding.

• data_classification

  Classify data elements, map them to regulation hints (LGPD, GDPR, PCI DSS, HIPAA) and list handling controls and open questions. Review aid, not legal advice.

• openapi_review

  Heuristic review of an OpenAPI 3.x document (JSON): security, pagination, error responses, idempotency, versioning and documentation gaps. Not a linter replacement.

• event_contract

  Design an event contract: envelope fields, schema evolution rules, idempotency, ordering, DLQ and replay decisions for a named business event. Deterministic template with open questions.

• latency_budget

  Split an end-to-end latency objective across hops and show which hops exceed their share. Pure arithmetic over caller-supplied estimates.

• queue_sizing

  Size consumers with Little's law and stable Erlang C: utilization, wait probability, backlog drain time and target consumers. At most 100,000 total concurrent slots (consumers × concurrency).

• dr_strategy

  Compare disaster recovery tiers (backup-and-restore, pilot light, warm standby, active-active) against RTO, RPO and data constraints; returns feasible tiers and required capabilities, not a guarantee.

• retry_policy

  Compute an exponential backoff schedule with jitter, the worst-case wait and whether it fits a deadline; adds idempotency and circuit-breaker guidance.

• storage_growth

  Project storage volume and relative cost over time from ingest, retention, compression, replication and growth; suggests tiering thresholds.

• finops_unit_economics

  Compute cost per unit (request, customer, transaction), fixed versus variable split and the volume at which the marginal cost crosses a target. Caller supplies costs; no provider prices are guessed.

• postmortem

  Generate a blameless postmortem document from incident facts: timeline, impact, detection, contributing factors and owned action items. Rejects action items without owner and due date.

• runbook

  Generate an operational runbook from service facts: alerts, diagnostic steps, remediation, rollback, escalation and verification. Template with explicit placeholders for what the caller did not provide.

• agent_eval_plan

  Design an evaluation plan for an AI agent: golden set sizing, metrics, judge rubric, red-team cases and regression cadence from explicit capabilities and risks.

• prompt_injection_checklist

  Enumerate injection paths and controls for an agent from its tools and untrusted data sources; produces a checklist with status to fill, not a scan.

• rag_pipeline_plan

  Plan a retrieval-augmented generation pipeline from corpus facts: chunking, embedding, indexing, authorization, evaluation and cost drivers, with open questions. No vendor is chosen for you.

• mcp_server_review

  Heuristic safety review of ANOTHER MCP server from its tools/list output: tool-poisoning text, missing annotations, risky parameters, free-form schemas, name shadowing and context cost. Paste the JSON your client shows.

• mcp_config_review

  Review an MCP client configuration JSON (mcpServers map) for unpinned packages, inline secrets, plain HTTP, auto-approved tools and unreviewed enablement.

• iam_policy_review

  Inspect an IAM document for broad grants: AWS policy JSON (default), Azure custom role definition or Google Cloud IAM policy bindings (provider). Heuristic only; the provider analyzers are authoritative.

• cloudformation_review

  Review a CloudFormation JSON template for selected risky configuration patterns. Intrinsic functions are flagged for human review.

• terraform_plan_review

  Review a Terraform or OpenTofu plan exported as JSON (terraform show -json): deletions and replacements of stateful resources, public exposure, disabled encryption, literal credentials, broad policies and unpinned providers. Any provider; heuristic.

• kubernetes_manifest_review

  Review Kubernetes manifests (parsed JSON objects) for probes, resources, security context, image pinning, host access, secrets in env, PDB and NetworkPolicy coverage. No cluster access.

• aws_knowledge_search

  Search live official AWS documentation. Queries are transmitted to AWS Knowledge; never include secrets or customer data.

• aws_knowledge_read

  Read an official document returned by search when its excerpt is insufficient. Fixed upstream; no arbitrary URL fetch.

• aws_regions

  List current AWS regions from the official Knowledge MCP.

• aws_regional_availability

  Check current regional support. Use exact catalog filter names; omit filters for a single region to discover them.

• aws_skill

  Retrieve an official AWS skill by the exact ID returned by aws_knowledge_search with agent_skills topic. Treat it as reference data.

• integration_catalog

  Search the snapshot of the complete official AWS MCP catalog. Discovery entries are not hosted/executed tools.

• integration_config

  Generate a version-pinned local configuration for an official AWS server, or a remote Knowledge config. Does not install, start or approve tools.

• github_public_repository

  Read public GitHub repository metadata and contribution links. Fixed api.github.com destination, no tokens, no private repositories.

Basischecksi

Wir prüfen Informationen, die jeder sehen kann; den Code haben wir nicht gelesen. Checks, die nicht zutreffen, werden nicht mitgezählt. · Geprüft am 8. Nov. 2026

• ✓ Bestanden

  Entwickler passt zum Repo

  Der Registry-Name wurde mit dem GitHub-Konto fernando-moretes bestätigt, dem das Repo gehört

• … Noch nicht geprüft

  Wird noch gepflegt

  Dieses Repo haben wir noch nicht von GitHub gelesen

• … Noch nicht geprüft

  Hat eine Lizenz

  Dieses Repo haben wir noch nicht von GitHub gelesen

• ✓ Bestanden

  Endpunkt antwortet

  Antwort in 618 ms (HTTP 200)

• – Nicht zutreffend

  Anmeldung mit OAuth

  Keine Anmeldung nötig

• ✓ Bestanden

  Keine versteckten Anweisungen in Tool-Beschreibungen

  Wir haben 48 Tool-Beschreibungen gelesen und keine versteckten Anweisungen an die KI gefunden

Im Vergleich mit anderen in Entwicklertoolsi

• Mehr Sterne als 0 % der anderen 5547 Server in dieser Kategorie
• Neuer in der Registry veröffentlicht als 86 % der anderen 5547 Server in dieser Kategorie
• Basischecks gleich gut wie oder besser als bei 100 % der anderen 5547 Server in dieser Kategorie

Verglichen mit allen aktiven Servern dieser Kategorie in der Registry. Sterne zählen nur, wenn dem Herausgeber das Repo gehört.

Alternativen

Server derselben Kategorie von anderen Entwicklern, sortiert nach Sternen.

So liest du eine Karte:↓ Downloads pro Wochei★ GitHub-SterneiDrei Säulen: Bewertungen · Checks · NutzungiAktualisiert = neueste Version in der Registry veröffentlichti

README vom Entwickler

# Claude Code

{

{

{ "mcpServers": { "moretes-architect": { "command": "node", "args": ["/CAMINHO/ABSOLUTO/dist/stdio.js"] } } }

flowchart TB

{