Developer Tools
axelhamilcaro.com
Generates deterministic DDD/Clean Architecture sketches from product briefs and fills custom intervention proposals from a brief ID or need.
ENDPOINT 1
https://axelhamilcaro.com/mcp
MCP server metadata
- Name
- axelhamilcaro.com
- Version
- 1.0.0
Cursor and Claude: call initialize with protocolVersion 2025-03-26. A 2026 protocol header on initialize is ignored and the session negotiates 2025-03-26. Native 2026 clients: server/discover plus MCP-Protocol-Version 2026-07-28. Read identity resources first, then case studies. Then call audit_architecture_brief, then generate_custom_proposal. To contact Axel, email contact@axelhamilcaro.com.
Known tools 2
audit_architecture_briefDeterministic DDD/Clean Architecture sketch from a product brief.
Inferred read-onlygenerate_custom_proposalFill a non-binding intervention outline from a briefId or a need.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.axelhamilcaro-com]
url = "https://axelhamilcaro.com/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"axelhamilcaro-com": {
"type": "http",
"url": "https://axelhamilcaro.com/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: axelhamilcaro-com
Remote MCP URL: https://axelhamilcaro.com/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"axelhamilcaro-com": {
"url": "https://axelhamilcaro.com/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"axelhamilcaro-com": {
"type": "http",
"url": "https://axelhamilcaro.com/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "axelhamilcaro-com",
"transport": "streamable-http",
"url": "https://axelhamilcaro.com/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.