webmcp-tool

Agent Readiness Check

www.itseasy.co

Checked 2026-09-08 06:43 UTC

90 / 100
grade A

This site is agent-ready

An agent can reach, read and operate this site. What is left is depth: tools it can call, protocols other systems can discover.

Fitness60 / 65Does the site work for agents today?
Adoption30 / 35Which 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?
Actionability20 / 25Can it finish the job?
Integration15 / 15Can another system find and call your capabilities?
Identity & Commerce5 / 10Can an agent prove who it is, and pay you?
WebMCP Implementation10 / 10Are 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.

01Honest annotations on tools

+5 pts

Tools are registered without annotations, so an agent cannot tell reads from writes.

How to fix it Set readOnlyHint on every tool that only reads. Set untrustedContentHint where a tool returns text written by other users. Put a confirmation step in front of anything that spends money or changes state.

Specification — tool annotations

02Forms an agent can fill

+3.5 pts

Fields are partly described — an agent will guess at the rest.

How to fix it Give every field a <label for>, a meaningful name, the right input type, and an autocomplete token from the HTML standard.

<label for="email">Work email</label>
<input id="email" name="email" type="email"
       autocomplete="email" required
       aria-describedby="email-hint">
<p id="email-hint">We reply within one business day.</p>

HTML standard — autofill tokens

03Agentic payment rails

+3 pts

This is a shop, and no agent-payable rail is advertised.

How to fix it Evaluate x402, the Agentic Commerce Protocol and the Universal Commerce Protocol against your payment provider, then publish the discovery document for whichever you adopt.

Your first WebMCP tool, matched to this page

The crawl found a a shop on this site, so the example below registers that as a tool an agent can call. Paste it, point it at your own endpoint, 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: "search_products",
  description: "Search the product catalogue by free text. Returns name, price and a link per match.",
  inputSchema: {
    type: "object",
    properties: { query: { type: "string", description: "Free-text search term" } },
    required: ["query"],
  },
  annotations: { readOnlyHint: true },
  execute: async ({ query }, { signal }) => {
    const res = await fetch(`/api/products?q=${encodeURIComponent(query)}`, { signal });
    return { content: [{ type: "text", text: JSON.stringify(await res.json()) }] };
  },
});

.well-known/webmcp

{
  "name": "www.itseasy.co",
  "description": "Return a short summary of this site and links to its main sections.",
  "tools": [
    {
      "name": "search_products",
      "description": "Search the product catalogue by free text. Returns name, price and a link per match."
    }
  ],
  "pages": [
    "https://www.itseasy.co/"
  ]
}

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

# Easy — Lower fees. Faster payments. Real rewards.

> Easy is the payment provider that lets you keep full control. Lower fees, instant access, and rewards on every dollar sitting in your account.

## Main pages
- [Start](https://www.itseasy.co/)
- [About](https://www.itseasy.co/about)
- [Contact](https://www.itseasy.co/contact)

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

Share this result

This address is public and stays current. The preview card carries the score.

Share on XShare on LinkedIn

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.

Agent Readiness Score for www.itseasy.co: grade A, 90 out of 100 — measured by webmcp-tool.com
<a href="https://webmcp-tool.com/check/www.itseasy.co" target="_blank" rel="noopener">
  <img src="https://webmcp-tool.com/badge/www.itseasy.co.svg"
       alt="Agent Readiness Score for www.itseasy.co: grade A, 90 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.

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="www.itseasy.co" src="https://agenttracking.co/agent.js"></script>

Open the dashboardHow 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 reportSee 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.