Connect it to your agent.
Ask what I do.
A small application-brain about my work and the way I build. Point your AI client at it and ask. It answers from cited facts, and it refuses, cleanly, when the answer is not there.
https://alicantorun.com/mcp
The architecture I build for clients, pointed at myself.
Retrieval-first. It returns answers grounded in cited facts from a versioned store, with the source for each, and it declines when a question is out of its corpus. The same pattern I build into products: an agent proposes, a verifier and a human decide. A reference build, not a product.
It answers
- What I build, and the way I build it
- How I architect agentic systems, with real scenarios
- The Lab, the drill, and how I work
- How I scope, and how to start a conversation
It refuses
- Anything it cannot ground in my published material
- It says it does not know, instead of inventing an answer
- No fabricated numbers, no claims I have not shown
- The refusal is the point. It is what I build for clients
One URL. Add it to your client.
No signup. A human has to choose to add this, which is the point. If you did, you are probably who I work with.
- 1Copy the URL or config
- 2Add it in your client
- 3Ask it about me
claude mcp add --transport http --scope user alican https://alicantorun.com/mcpRun it in your terminal. --scope user makes it available in all your projects.
“would alican be a fit for what i’m building, and what would he push back on?”
A deeper layer, behind the same server.
Architecture references, starters, and build-faster workflows for agentic startups, behind a membership. Same retrieval, same refusals, more depth.
Prefer a human?
The server is the fast way to find out if a call is worth our time. When it is, let us talk.