crewai.com WebMCP audit

Name: crewai.com WebMCP audit
Creator: ora

Rescan

audited Aug 28, 2026in 7s

57/ 100

2 tools registered. Strongest in usefulness, weakest in human experience.

WebMCP use55

Usefulness100

Human experience0

about:blank

No agent run recorded yet.

No steps recorded

Tools

fetch_blog_posts

Load recent blog posts from this site’s public JSON API (`GET /api/blog-posts`).Takes an action on the site.

pagehttps://crewai.com/

implementation

viaimperative

entry pointnavigator

registered after697ms

executepresent

api surface

limitoptional

skipoptional

annotations

read onlynot declared

destructivenot declared

idempotentnot declared

open worldnot declared

untrusted contentnot declared

titlenot declared

4 findings

failCanonical entry point

0 / 4

Every tool registers through the deprecated navigator.modelContext alias; move them to document.modelContext before the alias is removed.

fix

// Use the canonical entry point - navigator.modelContext is deprecated.
document.modelContext.provideContext({ tools: [/* ... */] });

warningSchema quality

2 / 4

1 of 2 tool schemas are harder for an agent to use than they need to be: fetch_blog_posts 2 parameters have no description (limit, skip).

fetch_blog_posts: 2 parameters have no description (limit, skip)

fix

{
  name: "fetch_blog_posts",
  inputSchema: {
    type: "object",
    properties: {
      query: { type: "string", description: "What to search for" }
    },
    required: ["query"]
  }
}

failAnnotations present

0 / 4

2 of 2 tools declare no readOnlyHint, so an agent cannot tell a read from a write without guessing from the name.

fetch_blog_posts, fetch_page_markdown

fix

{
  name: "fetch_blog_posts",
  annotations: { readOnlyHint: true, destructiveHint: false, idempotentHint: true }
}

warningHuman parity

0 / 8

2 of 2 tools run through the JavaScript API with no visible counterpart, so the person co-browsing cannot see what the agent is offered. Declarative forms (or at least a title annotation) close the gap.

fetch_blog_posts, fetch_page_markdown

fix

<!-- Give the tool a visible counterpart: a declarative form is one the person can see and use too. -->
<form toolname="fetch_blog_posts" tooldescription="...">
  <!-- the same action, as UI -->
</form>

tool json

{
  "name": "fetch_blog_posts",
  "description": "Load recent blog posts from this site’s public JSON API (`GET /api/blog-posts`).",
  "inputSchema": {
    "type": "object",
    "properties": {
      "limit": {
        "type": "number",
        "minimum": 1,
        "maximum": 24
      },
      "skip": {
        "type": "number",
        "minimum": 0
      }
    }
  },
  "annotations": {}
}

Findings

WebMCP use

55 / 100 · weight 50

passTools registered

4 / 4

2 tools registered across 1 page.

failReal-browser eligible

0 / 8

The page's code registers these tools, but a real visitor's browser does not get them yet: WebMCP needs a native modelContext or a current origin trial token, and this page has neither. The page does carry an origin-trial token, but it does not grant WebMCP on this origin.

passRegistration timing

4 / 4

Every measured tool registered within 709.5999999046326ms of navigation.

toolfetch_page_markdown

failCanonical entry point

0 / 4

Every tool registers through the deprecated navigator.modelContext alias; move them to document.modelContext before the alias is removed.

toolfetch_blog_posts

fix

// Use the canonical entry point - navigator.modelContext is deprecated.
document.modelContext.provideContext({ tools: [/* ... */] });

passSchema validity

5 / 5

All 2 tools declare a structurally valid object input schema.

warningSchema quality

2 / 4

1 of 2 tool schemas are harder for an agent to use than they need to be: fetch_blog_posts 2 parameters have no description (limit, skip).

toolfetch_blog_posts

fetch_blog_posts: 2 parameters have no description (limit, skip)

fix

{
  name: "fetch_blog_posts",
  inputSchema: {
    type: "object",
    properties: {
      query: { type: "string", description: "What to search for" }
    },
    required: ["query"]
  }
}

passStub detection

5 / 5

All 2 tools declare an execute handler.

failAnnotations present

0 / 4

2 of 2 tools declare no readOnlyHint, so an agent cannot tell a read from a write without guessing from the name.

toolfetch_blog_posts

fetch_blog_posts, fetch_page_markdown

fix

{
  name: "fetch_blog_posts",
  annotations: { readOnlyHint: true, destructiveHint: false, idempotentHint: true }
}

not applicableAnnotation mismatch

0 / 3

No tool declares a readOnlyHint, so there is no safety claim to contradict.

not applicableUntrusted content hint

0 / 2

No tool's contract suggests it returns text written by somebody other than the site, so there is nothing to flag as untrusted.

passRegistration errors

2 / 2

No tool registration threw during the capture.

warningToolchange coherence

1 / 2

2 tools were registered but the page never dispatched a toolchange event, so an agent subscribed to registry updates never learns they exist.

fix

document.modelContext.dispatchEvent(new Event("toolchange"));

not applicableInjection surface

0 / 3

The injection-surface model hop returned no usable result, so tool contracts were not reviewed for injection surface.

Usefulness

100 / 100 · weight 30

passNaming quality

2 / 2

All 2 tool names are consistent, verb-led, and within Chrome's size guidance.

not applicableDescription quality

0 / 6

The description-quality model hop returned no usable result, so descriptions were not rated.

not applicableTool selection

0 / 14

The tool-selection model hop returned no usable result.

not applicableCoverage vs. site type

0 / 8

This tool set does not place the site in a category with a known expected tool shape, so there is no coverage baseline to score it against.

Human experience

0 / 100 · weight 20

warningHuman parity

0 / 8

toolfetch_blog_posts

fetch_blog_posts, fetch_page_markdown

fix

<!-- Give the tool a visible counterpart: a declarative form is one the person can see and use too. -->
<form toolname="fetch_blog_posts" tooldescription="...">
  <!-- the same action, as UI -->
</form>

not applicablePage experience

0 / 12

The page-experience model hop returned no usable result, so the page was not graded.

Tool selection

The tool-selection model hop returned no usable result.

how this was captured

chrome: 148.0.7778.96
capture shim: v1
spec snapshot: 2026-08
mode: fast
pages: 1
tools: 2
run time: 7s
finished: Aug 28, 2026