Agent Readiness Check

piszczek.pl

Checked 2026-09-18 05:37 UTC

81 / 100

grade B

Agents can partly use this site

An agent can read this site and get some way through it, with friction. The points still on the table are listed below, largest first.

Fitness47.5 / 55Does the site work for agents today?

Adoption19.5 / 28Which agent protocols are in place?

Agent Access20 / 20Can an agent reach the page at all?

Machine Readability20 / 20Can it understand what is on the page?

Actionability7.5 / 15Can it finish the job?

Integration12 / 15Can another system find and call your capabilities?

Identity & Commerce1.5 / 7Can an agent prove who it is, and pay you?

WebMCP Implementation6 / 6Are there tools an agent can call in the page?

Three fixes worth doing first

Ordered by the points still on the table. Each one comes from a documented check and, where it exists, with the code that fixes it.

01A primary action is discoverable

+5 pts

Nothing on this page can be completed by an agent.

How to fix it Make the main action part of the served HTML: a real form, a search input, or a link to the booking or cart route. A button that only exists after hydration does not count.

02Agent-facing authentication

+4 pts

You expose machine capabilities but no documented way to authenticate against them.

How to fix it Publish OAuth discovery metadata, or an auth.md describing how machine clients obtain access.

RFC 8414 — OAuth authorization server metadata RFC 9728 — OAuth protected resource metadata

03An agent card other agents can read

+3 pts

No agent card or skills document responds.

How to fix it Publish an A2A agent card at /.well-known/agent-card.json, and keep serving /.well-known/agent.json while older clients are still in circulation.

A2A — agent discovery

Your first WebMCP tool, matched to this page

The crawl found no search, shop, booking flow or form on this page, so the example below registers the one tool every site can ship in an hour: a read-only summary an agent can call instead of scraping. Paste it and the page stops being guessed at and starts being called.

registerTool

// Register the first tool an agent can call on this page.
// Works today with the polyfill: npm install @mcp-b/global
await document.modelContext.registerTool({
  name: "get_page_summary",
  description: "Return a short summary of the current page and links to its main sections.",
  inputSchema: { type: "object", properties: {} },
  annotations: { readOnlyHint: true },
  execute: async (_args, { signal }) => {
    const text = document.querySelector("main")?.innerText.slice(0, 2000) ?? document.title;
    return { content: [{ type: "text", text }] };
  },
});

.well-known/webmcp

{
  "name": "piszczek.pl",
  "description": "Return a short summary of this site and links to its main sections.",
  "tools": [
    {
      "name": "get_page_summary",
      "description": "Return a short summary of the current page and links to its main sections."
    }
  ],
  "pages": [
    "https://piszczek.pl/"
  ]
}

The manifest at /.well-known/webmcp is the convention ChatGPT Desktop reads to list site tools. It is not part of the score yet; the registered tool above is.

llms.txt

# Michał Piszczek - CTO, Founder & AI Systems Builder

> Michał Piszczek: ex-hacker, CTO of Archdesk, founder of Lextron.ai, Inclify, Rejsomat.pl and Robotero (acquired), author of Joule Wars on energy-efficient AI.

## Main pages
- [Start](https://piszczek.pl/)
- [About](https://piszczek.pl/about)
- [Contact](https://piszczek.pl/contact)

Built from this page's own title and description. Replace the three links with your canonical pages.

Put the live badge on the site

The image is served from here and re-scores on its own. Every embed links back to this page.

<a href="https://webmcp-tool.com/check/piszczek.pl" target="_blank" rel="noopener">
  <img src="https://webmcp-tool.com/badge/piszczek.pl.svg"
       alt="Agent Readiness Score for piszczek.pl: grade B, 81 out of 100 — measured by webmcp-tool.com"
       width="208" height="40" loading="lazy" decoding="async">
</a>

Agent Readiness Check

The full report, plus a re-check in 30 days

Every check with the evidence it was judged on and the code that fixes it, sent as a link that always re-scans. In 30 days we scan again and tell you what moved.

All checks, pass by pass, with the exact header, count or path behind each verdict
Copy-paste fixes generated from your own markup
A re-check in 30 days with the difference, confirmed by you with one click

One email with the report, one re-check after you confirm it, and nothing else unless you ask. No account. Five reports per company per day. What we do with the address.

Not ready? We build it.

The MCP server for this site, at a fixed price

Up to eight tools over your API or your site, OAuth 2.0, hosted, monitored, and prepared for the Claude Connectors and ChatGPT Apps review. Ten business days, code handed over. From the people who run this check.

See the packages at mcp-tool.comBuild $4,900 · Listing Sprint $1,900 · Care $390/month

Agent Tracking

You know whether agents can read this site. Want to know what they do with it?

One line of script records which assistants send visitors, which pages they fetch, which WebMCP tools they call and whether they finish. No cookies, no personal data, hosted in Germany. The check score shows up in the dashboard and is re-scanned monthly.

<script defer data-domain="piszczek.pl" src="https://agenttracking.co/agent.js"></script>

Open the dashboard How it works

Compare with another site

A competitor, a client, the site you are about to ship. Two checks side by side, on one shareable address.

Open the full report See the best-scoring sites

Reports re-scan at most once an hour. Change something and open this address again.

Check another site

One request, about 20 seconds. No sign-up, no email. The result gets a shareable address.