Home / MCP registry index / io.github.fernando-moretes/moretes-aws-architect-mcp

Moretes Architect MCP

io.github.fernando-moretes/moretes-aws-architect-mcp in the official MCP registry. Endpoint https://mcp.moretes.com/mcp. Source: github.com/fernando-moretes/moretes-aws-architect-mcp.

The registry describes it as: Evidence-first architecture workbench: 48 deterministic tools, 10 architect personas, any cloud

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

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

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

code --add-mcp '{"name":"moretes-aws-architect-mcp","type":"http","url":"https://mcp.moretes.com/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which.

Let Claude Code check servers as it adds them

With the free lazaretto-guard plugin installed, when Claude Code adds a server for you or writes one into an MCP config, the plugin reads the server's tools first and asks you if one of our rules matches. Install it, restart Claude Code, then ask it to run the command above.

claude plugin marketplace add jamesdfinance-dev/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-plugins

Tools it advertises

architect_panel code_review_architecture dependency_manifest_review requirements_check architecture_pattern service_compare decision_record well_architected_review threat_model failure_rehearsal capacity_plan cost_model slo_budget migration_plan architecture_diagram implementation_plan agent_tool_contract c4_model sequence_diagram service_equivalents data_classification openapi_review event_contract latency_budget queue_sizing dr_strategy retry_policy storage_growth finops_unit_economics postmortem runbook agent_eval_plan prompt_injection_checklist rag_pipeline_plan mcp_server_review mcp_config_review iam_policy_review cloudformation_review terraform_plan_review kubernetes_manifest_review aws_knowledge_search aws_knowledge_read aws_regions aws_regional_availability aws_skill integration_catalog integration_config github_public_repository

Tool changes

We compare every full read of this server with the one before. No change in what its tools say has been seen since we started keeping this record on 2026-10-30.

Fingerprint of its tools at our last full read (2026-10-31): 138d6fa79fd223cb. A client can hash the tools it is served the same way and compare; the full value and a hash per tool are in this page as JSON.

Run this server? Show the check in your README

The badge reflects the latest weekly read:

[![MCP tool check](https://lazaretto.dev/mcp-registry/io-github-fernando-moretes-moretes-aws-architect-mcp/badge.svg)](https://lazaretto.dev/mcp-registry/io-github-fernando-moretes-moretes-aws-architect-mcp)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.

Related

AWS MCP servers