mtt.engineer
partial
Claude Code
intent

What does mtt.engineer do and who is it for? Explain it back to me.

11steps
48.5sduration
$0.5644cost
66,644tokens
15 steps4 reasoning steps5 searches
home
search
/posts
docs
docs
search
search
search
/mtt87
search
docs
100%
on-site discovery
33%
reliability
67%
link following
path origin
  • previous resource67%
  • prior knowledge33%
insight

The agent could not fully satisfy the task because mtt.engineer is a personal portfolio site, not a commercial product or service. The agent correctly identified this by fetching the homepage (step [1]) and Mattia Asti's GitHub profile (step [12]), but the site itself provided almost no navigable content—no pricing page, blog listing, or clear positioning—forcing reliance on external profiles (LinkedIn, GitHub) to construct even a partial picture. The agent had to bridge the gap between what the task assumed (a business offering) and what the site actually is (a personal portfolio with minimal exposition).

  • ›Step [1] returned only a minimal homepage with no substantive content about services, pricing, or business model. The homepage structure offered no navigation to deeper pages and no value proposition statement.
  • ›Steps [3]–[7] reveal a broken information architecture: the agent attempted /posts, /blog, /about, and /pricing routes based on reasonable assumptions and search hints, but all returned 404s, indicating either poor site structure or minimal content.
  • ›Steps [9] and [12] show the agent had to leave the domain entirely to understand who Mattia Asti is. The site itself surfaced no content; prior knowledge and external profiles (LinkedIn, GitHub) became the primary evidence.
  • ›Web searches (steps [8], [10], [13]) returned unrelated MTT companies and organizations, demonstrating that mtt.engineer has no public discoverability and no SEO-friendly positioning statement that would help an agent or search engine understand its purpose.
  • ›The agent had to infer that the domain is a personal blog based on external context, but could not access blog content from the site itself—the only blog post reference (Tailscale article, step [3]) could not be fetched.

Help the next agent finish on mtt.engineer

Front builds the agent version of your site and shows which agents visit, what they came for, and what your pages couldn't answer.

or talk to us about agent readiness →