atlan.com WebMCP audit

Name: atlan.com WebMCP audit
Creator: ora

Rescan

audited Sep 1, 2026in 13s

78/ 100100% of the applicable check weight evaluated

2 tools registered. Strongest in shared experience, weakest in trust.

Shared experience100

Task completion100

Tool quality93

Trust0

https://atlan.com

Tools

0 read, 0 write, 2 undeclared

Loading map

list_atlan_resources

List Atlan's public, machine-readable resources for AI agents: documentation, the Atlan MCP Server, the llms.txt index, and the API catalog.No behaviour hints declared. Agents should treat it as possibly state-changing.

pagehttps://atlan.com/

implementation

viaimperative

entry pointprovideContext

registered after391ms

executepresent

api surfaceTakes no parameters.

annotations

read onlynot declared

untrusted contentnot declared

titlenot declared

1 finding

failAnnotations present

weight 6

1 of 1 read-shaped tools do not declare readOnlyHint: true, so an agent has to treat them as possible writes and ask before calling. (Declaring readOnlyHint: false earns nothing - it is the default.)

list_atlan_resources

fix

{
  name: "list_atlan_resources",
  // Declare readOnlyHint: true on tools that truly have no side effects -
  // that is the claim that lets an agent relax confirmation on reads.
  // (false is the default, so declaring it adds no information.)
  annotations: { readOnlyHint: true }
}

tool json

{
  "name": "list_atlan_resources",
  "description": "List Atlan's public, machine-readable resources for AI agents: documentation, the Atlan MCP Server, the llms.txt index, and the API catalog.",
  "inputSchema": {
    "type": "object",
    "properties": {},
    "additionalProperties": false
  },
  "annotations": {}
}

Findings

Shared experience

100 / 100 · weight 30

passPage experience

weight 20

The page a person sees holds up next to the agent surface: a working interface, visible actions, readable content, nothing in the way.

passHuman parity

weight 10

The person co-browsing can see and use this page - the same page the agent's tools act on.

Task completion

100 / 100 · weight 25

passTool selection

weight 15

An agent chose an existing, callable tool and built a schema-valid call for all 2 canonical intents, each matching the kind of tool its intent needs. Nothing was executed, so this verifies selection, not outcomes.

not applicableCoverage vs. site type

weight 10

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.

Tool quality

93 / 100 · weight 25

passRegistration timing

weight 1

Every measured tool registered within 391ms of navigation.

toolgo_to_atlan_section

passCanonical entry point

weight 3

All 2 tools register on the canonical document.modelContext entry point.

passSchema validity

weight 4

All 2 declared input schemas are structurally valid object schemas.

passSchema quality

weight 4

All 1 of 2 tool schemas that declare parameters describe them (the other 1 declares no parameters), and every description stays within Chrome's size guidance.

warningNaming quality

weight 2

Tool naming makes selection harder than it needs to be: 1 name does not start with a verb (go_to_atlan_section).

toolgo_to_atlan_section

fix

{ name: "go_to_atlan_section" /* short, unique, verb-based */ }

passStub detection

weight 4

All 2 tools declare an execute handler.

passRegistration errors

weight 2

No tool registration threw during the capture.

warningDescription quality

weight 5

1 of 2 tool descriptions leave an agent guessing: go_to_atlan_section Does not say what comes back or what changes..

toolgo_to_atlan_section

go_to_atlan_section: weak

fix

{
  name: "go_to_atlan_section",
  description: "Describe what this tool does, when to use it, and what it returns."
}

Trust

0 / 100 · weight 20

failAnnotations present

weight 6

1 of 1 read-shaped tools do not declare readOnlyHint: true, so an agent has to treat them as possible writes and ask before calling. (Declaring readOnlyHint: false earns nothing - it is the default.)

toollist_atlan_resources

list_atlan_resources

fix

{
  name: "list_atlan_resources",
  // Declare readOnlyHint: true on tools that truly have no side effects -
  // that is the claim that lets an agent relax confirmation on reads.
  // (false is the default, so declaring it adds no information.)
  annotations: { readOnlyHint: true }
}

not applicableAnnotation mismatch

weight 6

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

not applicableUntrusted content hint

weight 4

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

not applicableInjection surface

weight 4

No tool's metadata carries instruction-shaped text aimed at the agent reading it. This check only ever flags; it never credits a site.

Tool selection

100% across 2 intents

I want to list atlan resources on this site.ok

choselist_atlan_resourcesexpected list atlan resourceskind matched

arguments

{}

I want to go to atlan section on this site.ok

chosego_to_atlan_sectionexpected go to atlan sectionkind matched

arguments

{
  "section": "product"
}

model: gemini-2.5-flash

Add the tools this site is missing

Our scanner reads your website and suggests the right WebMCP tools for it.

The open source webmcp plugin teaches your coding agent to audit a site, implement tools on document.modelContext, and verify them in a real browser. npx @ora-ai/webmcp-verify runs the verification on its own. No signup, no hosted service.

how this was captured

observed via: capture shim (Chromium 148.0.7778.96)
chrome: 148.0.7778.96
capture shim: v1
spec snapshot: 2026-08-26
mode: fast
pages: 1 - entry page only
tools: 2
run time: 13s
finished: Sep 1, 2026

Checked the way in-browser agents discover tools: the top-level document's modelContext registry, read after the page settles.