Agentfit

io.github.CloudCorpRecordsPublished by GitHub account CloudCorpRecordsv0.1.0Updated Nov 7, 2026

Is your website ready for AI agents? Free preview: 0-100 score, A-F grade and category scores.

VerifiedSTDIODesktop onlyWeb Search & ScrapingDeveloper Tools

Overview

AI-generated overview

Scores a website's readiness for AI agents via the AgentReady free preview, returning a 0-100 score, A-F grade and category scores.

What you can do
  • Audit a website: submit a URL and get the AgentReady free preview back — a 0-100 score, an A-F grade and category scores covering agent access, readable content, discovery and agent interfaces.
  • The upstream response body is passed through unchanged; nothing is computed, trimmed or summarised locally.
  • Failures surface as plain error text, such as an HTTP status for bad, private, unresolvable or rate-limited URLs, or an unreachable message on timeout.
When to use it
Useful when you want a quick, read-only check of how well a site is set up for AI agents, for example while reviewing a site you own or comparing candidate sites. It is a single-purpose preview tool, not a full audit.
Requirements
Runs as a local process via npx (Node.js) or the published Docker image; no account, API key or auth header is needed. Network access to the AgentReady API is required; the base URL can be overridden with AGENTREADY_API_URL and the per-request timeout with AGENTREADY_TIMEOUT_MS (default 30000 ms).
Before you install
The URL you submit is sent to a third-party service (AgentReady) for scoring, so avoid private or internal addresses. The free preview is rate-limited upstream to 10 requests per minute per IP. This build omits the paid x402 routes and wallet-key mode entirely and reads no payment or wallet variables.

Installation

In SourceWeft

  1. Open Agentfit in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

agentfit

Is your website ready for AI agents? agentfit asks the AgentReady service for its free preview of a site: a 0-100 score, an A-F grade and category scores covering things like agent access, readable content, discovery and agent interfaces. The score is the upstream's — nothing is computed, trimmed, renamed or summarised locally; the response body comes back exactly as the service returned it.

Free tier only — the paid surface is omitted

AgentReady also offers x402-paid routes (/v1/lite at $0.005 and /v1/audit at $0.03, paid in USDC), and its original stdio server pays for the full audit per call when a wallet private key is supplied through AGENTREADY_X402_PRIVATE_KEY. This rebuild implements none of that. It calls only the documented free route, GET /v1/preview?url=, which is the original server's own default behaviour without the key. The paid routes and the wallet-key mode are omitted entirely: this build holds no payment instrument, never reads AGENTREADY_X402_PRIVATE_KEY or any other wallet or payment environment variable, and never sends an Authorization header.

The free preview is limited upstream to 10 requests per minute per IP; a 429 (like any other non-2xx reply) surfaces as agentready error: HTTP 429.

Configuration

Two environment variables control the client (both are this rebuild's own, labelled):

  • AGENTREADY_API_URL (optional) — API base URL. Defaults to https://api.youraitools.co/agentready; a trailing slash is stripped.
  • AGENTREADY_TIMEOUT_MS (optional) — per-request timeout in milliseconds, enforced with an AbortController. Defaults to 30000.

Tools

  • audit_website — is this website ready for AI agents? Returns the free preview: a 0-100 score, an A-F grade and category scores. Takes one required argument, url (the documented REST parameter; the MCP-layer argument name is a labelled reconstruction, because the hosted MCP endpoint did not answer during spec capture).

An upstream non-2xx reply fails with agentready error: HTTP <status> — that is how the upstream's 400 (bad, private or internal URL), 422 (unresolvable host) and 429 (preview rate limit) answers surface. An unreachable service, including a timeout, fails with agentready unreachable.

CLI

The tool is a subcommand taking one JSON argument string:

bash
npx @reneturcios/agentfit audit_website '{"url":"https://example.com"}'npx @reneturcios/agentfit --version

Output is the tool's result text (the upstream body on success). Exit codes: 0 on success, 1 on a runtime error, 2 on a usage error.

MCP server

bash
npx -y @reneturcios/agentfit mcp

MCP client config:

json
{  "mcpServers": {    "agentfit": {      "command": "npx",      "args": ["-y", "@reneturcios/agentfit", "mcp"]    }  }}

Docker

bash
docker run -i ghcr.io/cloudcorprecords/agentfitdocker run --rm ghcr.io/cloudcorprecords/agentfit audit_website '{"url":"https://example.com"}'

Development

bash
npm installnpm run build   # tsc -> dist/npm test        # tsx --test test/*.test.ts (fake fetch only, no network)npm run dev     # run the CLI from source

License

MIT — Copyright (c) 2026 Rene Turcios

Source: README.md at commit ba2c93c

Tools

1

audit_website

Is this website ready for AI agents? Returns the free preview: a 0-100 score, an A-F grade and category scores.

Parametersurlrequired

Version history

1
  1. v0.1.0LatestNov 4, 2026

Score

90% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts
  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts