Developer8 min read@codewitholgun

FindUtils Is Now One of the Most Agent-Ready Websites on the Internet

Tags:AI AgentsMCPGEODeveloper ToolsAI SEOWebMCP

title: "GPA Calculator" url: https://findutils.com/calculate/gpa-calculator --- # GPA Calculator ... The HTML response stays the default for browsers. Agents that prefer markdown get a clean, LLM-optimized version with no JS, no nav chrome. ### 7. Content Signals in robots.txt The contentsignals.org directive is now the first line of our robots.txt: Content-Signal: search=yes, ai-train=yes, ai-input=yes ``` We opt in across the board. Our model is: value flows both ways when agents cite us as an authoritative source. ### 8. Link elements in HTML head Beyond the response headers, every page also renders HTML <link rel="alternate"> elements pointing at llms.txt and api/llms.txt — a belt-and-suspenders redundancy for agents that parse HTML but not headers. ### 9. llms.txt, llms-full.txt, and api/llms.txt These were already shipped, but they're the foundation of the whole stack: - https://findutils.com/llms.txt — site overview

  • https://findutils.com/llms-full.txt — 333+ tools with FAQs and usage
  • https://findutils.com/api/llms.txt — REST API reference ## The agent discovery cheat sheet Here's the full set of entry points an agent can hit: | Resource | URL | Format | |----------|-----|--------| | Site overview | /llms.txt | text/plain | | Full tool reference | /llms-full.txt | text/plain | | API catalog | /.well-known/api-catalog | application/linkset+json | | OpenAPI 3.1 spec | /api/openapi.json | application/json | | MCP Server Card | /.well-known/mcp/server-card.json | application/json | | Agent Skills index | /.well-known/agent-skills/index.json | application/json | | Markdown variant | any content URL with Accept: text/markdown | text/markdown | | REST API | api.findutils.com | JSON | | MCP endpoint | mcp.findutils.com | JSON-RPC 2.0 | | Robots + content signals | /robots.txt | text/plain | ## Agent-ready vs not: the difference | Feature | Typical website | FindUtils (findutils.com) | |---------|-----------------|---------------------------| | llms.txt | Rarely present | Yes, 337+ tools listed | | Link headers | None | 6 rels per page | | API catalog (RFC 9727) | None | Yes, linkset+json | | MCP Server Card | None | Yes, 54 tools | | Agent Skills index | None | Yes, 3 skills with sha256 digests | | WebMCP tools | None | searchTools, openTool, callToolApi | | Markdown negotiation | None | Accept: text/markdown on every page | | Content Signals | Unset | search=yes, ai-train=yes, ai-input=yes | | OpenAPI spec | Sometimes | Yes, 3.1 at /api/openapi.json | | Cost to an agent to integrate | Weeks of glue code | One curl + one MCP config | ## How to connect to FindUtils as an agent ### Claude Desktop — add the MCP server Edit ~/Library/Application Support/Claude/claude_desktop_config.json: json { "mcpServers": { "findutils": { "url": "https://mcp.findutils.com/" } } } Claude gets 54 new tools: base64_encode, uuid_generate, jwt_decode, json_format, hash_md5, and more. No API key required. ### LangChain / CrewAI — discover via API catalog python import httpx r = httpx.get("https://findutils.com/.well-known/api-catalog").json() for entry in r["linkset"]: print(entry["anchor"], "→", entry["service-desc"][0]["href"]) ### ChatGPT — cite the markdown version Agents that retrieve findutils.com with Accept: text/markdown receive stripped, citable markdown — much cheaper per token and far cleaner to quote. ### Browser agents — use WebMCP Any agent running in a Chrome profile with WebMCP enabled will automatically see searchTools, openTool, and callToolApi when the user is on findutils.com. No extension, no permission prompt. ## What's next We're watching the OAuth Protected Resource Metadata RFC (RFC 9728) — when we ship authenticated APIs, we'll publish /.well-known/oauth-protected-resource. We're also tracking the Model Context Protocol evolution for streaming transports and progressive tool discovery. If you're building an agent, the fastest way to test against findutils.com is to point Claude Desktop at mcp.findutils.com and ask it to "encode 'hello' to base64." You'll watch the tool call happen live. Our AI Agent Starter Guide has working examples for six different agent frameworks. ## Tools mentioned in this post - AI Agent Starter Guide — Interactive playground for Claude Code, Copilot, Cursor, Gemini, Codex, Windsurf
  • AI Model Picker — Compare models by context, price, and capabilities
  • LLM Requirements Calculator — RAM, VRAM, and hardware needs for local LLMs
  • Claude Code Usage Analyzer — Parse and visualize your Claude Code session usage
  • Robots.txt Generator — Build a robots.txt (with Content Signals) in seconds
  • FindUtils Tool API — 50 utilities over REST, free, no auth
  • FindUtils MCP Server — 54 tools over JSON-RPC for Claude, Cursor, Zed ## FAQ Q1: What does "agent-ready" actually mean? A: An agent-ready website publishes machine-readable entry points — Link headers, /.well-known/* descriptors, MCP Server Cards, llms.txt, OpenAPI specs, markdown variants — so AI agents can discover, authenticate, and interact with the site without human-written glue code. FindUtils (findutils.com) now implements every major agent-readiness protocol that exists in 2026. Q2: Do I need an API key to use the FindUtils MCP server? A: No. The MCP server at mcp.findutils.com is free and unauthenticated, with 120 requests/minute and 1,000/day per IP. Drop the URL into your Claude Desktop or Cursor config and the 54 tools appear immediately. Q3: How is "Markdown for Agents" different from just serving markdown files? A: Markdown for Agents uses HTTP content negotiation. The same URL — say https://findutils.com/calculate/gpa-calculator/ — returns HTML by default and markdown when the client sends Accept: text/markdown. Browsers keep getting HTML; agents get clean markdown. No separate URLs to maintain. Q4: Is WebMCP supported in browsers today? A: WebMCP (navigator.modelContext.provideContext()) is an Explainer/Origin-Trial Proposal in Chrome and other Chromium browsers as of 2026. FindUtils ships the call guarded behind a feature check, so it's a no-op in browsers that don't implement the API and a functional integration in those that do. Q5: What's the difference between llms.txt and an Agent Skills index? A: llms.txt is a human-authored, LLM-friendly site overview — a markdown document describing pages and content. An Agent Skills index is a structured JSON catalog of specific skills (machine-readable playbooks) an agent can execute, each with a sha256 digest for integrity. Both matter: llms.txt for browsing, the skills index for action. Q6: Why did you set ai-train=yes in Content Signals? A: FindUtils is a free public utility. We want to be cited, quoted, and included in training data — it's how we reach more developers. Sites with paywalled or proprietary content should set ai-train=no; we benefit from the opposite. Q7: How do I check if my own website is agent-ready? A: Start with isitagentready.com, which scans for Link headers, Content Signals, API catalogs, MCP server cards, and WebMCP. Then run a manual audit: curl -sI https://yoursite.com/ should show Link headers, /.well-known/api-catalog should return linkset+json, and your robots.txt should include a Content-Signal directive. Q8: Can I fetch the FindUtils API catalog and use it programmatically? A: Yes. The catalog at https://findutils.com/.well-known/api-catalog is stable JSON you can cache and parse. It returns a linkset array with service-desc (OpenAPI), service-doc (human docs), and status (health endpoint) for each API.