Plaid Docs
relative to the checks that apply to this site; global measures it against a maximally agent-ready site.
Discoverability
0 / 3/robots.txt present SHOULD MISSING
Goal: Publish robots.txt and state your crawl policy explicitly.
Result: Not found (https://docs.plaid.com/robots.txt -> 404 (status 404 not in [200]))
Fix: Publish a `robots.txt`. Declare your crawl and AI-usage policy explicitly rather than leaving it to inference. An absent `robots.txt` is ambiguous; a present one is a clear signal.
/sitemap.xml present MAY N/A
Goal: Publish sitemap.xml so agents can enumerate your content URLs.
Result: Not implemented, optional (https://docs.plaid.com/sitemap.xml -> 404 (status 404 not in [200]))
Resources: sitemaps.org · Fix skill
Homepage sends RFC 8288 Link headers pointing at agent resources SHOULD MISSING
Goal: Advertise machine surfaces in a Link response header on / for header-only discovery.
Result: Not found (https://docs.plaid.com/ -> 200 (header link no match /rel="?(service-desc|describedby|api-catalog|service-doc)"?/))
Fix: Send a `Link` response header on `/` (RFC 8288) whose `rel` points at your machine surfaces, so an agent reading only response headers finds them without parsing HTML or probing `/.well-known`. Use the RFC 8631 service trio and the RFC 9727 catalog: `rel="service-desc"` at a machine-readable description (OpenAPI, or an MCP server card), `rel="service-doc"` at the human-readable doc, `rel="service-meta"` at the service-context declaration, and `rel="api-catalog"` at your `/.well-known/api-catalog` index. Example: `Link: </.well-known/api-catalog>; rel="api-catalog", </.well-known/mcp/server-card.json>; rel="service-desc"`.
Resources: RFC 8288 (Link) · RFC 8631 (service links) · RFC 9727 (api-catalog) · Fix skill
Root HTML links to machine surfaces via <link rel> SHOULD MISSING
Goal: Point link rel elements at your machine surfaces from the root HTML head.
Result: Not found (https://docs.plaid.com/ -> 200 (body no match /rel=["'](service-desc|service-doc|alternate)["']/))
Fix: Add `<link rel>` elements in your root HTML head pointing at your machine surfaces: `rel="service-desc"` to the OpenAPI doc, `rel="service-doc"` to human docs, and `rel="alternate"` to `llms.txt` and the MCP card. An agent that lands on the HTML can then discover the structured surfaces without scraping.
Resources: RFC 8631 (service-desc/doc) · Fix skill
DNS for AI Discovery (DNS-AID) records under _agents (IETF draft) MAY N/A
Goal: Publish DNSSEC-signed SVCB records under _agents for DNS-level agent discovery.
Result: Not implemented, optional (no DNS-AID records)
Resources: DNS-AID draft · Fix skill
Content for agents
7 / 7/llms.txt present with a summary and link index SHOULD PASS
Goal: Serve /llms.txt with a title, summary, and categorized link index.
Result: Verified (https://docs.plaid.com/llms.txt -> 200)
Resources: llmstxt.org · Fix skill
/llms-full.txt present (single-fetch full corpus) MAY PASS
Goal: Serve the whole docs corpus as markdown at /llms-full.txt for one-fetch ingestion.
Result: Verified (https://docs.plaid.com/llms-full.txt -> 200)
Resources: llmstxt.org · Fix skill
Per-section llms.txt files resolve under content subdirectories MAY N/A
Goal: Serve a scoped llms.txt inside each major content section.
Result: Not implemented, optional (llms-txt-scoped -> error (no section directories in the root llms.txt or sitemap))
Resources: llmstxt.org · Fix skill
Per-section llms-full.txt files resolve under content subdirectories MAY N/A
Goal: Serve a scoped llms-full.txt corpus inside each major content section.
Result: Not implemented, optional (llms-full-txt-scoped -> error (no section directories in the root llms.txt or sitemap))
Resources: llmstxt.org · Fix skill
Root HTML has a descriptive <meta name="description"> SHOULD PASS
Goal: Add a meta description naming what the service does and its agent entry points.
Result: Verified (https://docs.plaid.com/ -> 200)
Resources: MDN meta description · Fix skill
Root HTML embeds Schema.org JSON-LD MAY PASS
Goal: Embed Schema.org JSON-LD so agents get typed facts without inference.
Result: Verified (https://docs.plaid.com/ -> 200)
Resources: Schema.org · Fix skill
Root HTML uses semantic landmarks MAY PASS
Goal: Use semantic landmarks so the HTML path is parseable structure, not div soup.
Result: Verified (https://docs.plaid.com/ -> 200)
Resources: MDN content sectioning · Fix skill
Root HTML has a <noscript> with machine entry points SHOULD PASS
Goal: Give non-JS agents a noscript block listing your machine entry points.
Result: Verified (https://docs.plaid.com/ -> 200)
Resources: MDN noscript · Fix skill
Accept text/markdown content negotiation returns markdown SHOULD PASS
Goal: Honor Accept text/markdown on content URLs with raw markdown, not HTML chrome.
Result: Verified (https://docs.plaid.com/ -> 200)
Resources: RFC 7763 (text/markdown) · Fix skill
Bot & crawl policy
0 / 0No checks in this category apply to this site.
robots.txt declares AI-crawler rules (RFC 9309) SHOULD N/A
Goal: State your AI-crawler policy in robots.txt with explicit User-agent rules.
Result: Not applicable (robots.txt not present)
robots.txt declares Content-Signal AI-usage preferences SHOULD N/A
Goal: Declare Content-Signal AI-usage preferences in robots.txt.
Result: Not applicable (robots.txt not present)
Resources: contentsignals.org · Fix skill
/.well-known/security.txt present (RFC 9116) MAY N/A
Goal: Publish security.txt with a Contact and Expires field.
Result: Not implemented, optional (https://docs.plaid.com/.well-known/security.txt -> 404 (status 404 not in [200]))
Web Bot Auth signature directory present (informational) MAY N/A
Goal: Publish an HTTP Message Signatures directory if your site sends signed bot traffic.
Result: Not implemented, optional (https://docs.plaid.com/.well-known/http-message-signatures-directory -> 404 (status 404 not in [200]))
Resources: Web Bot Auth draft · Fix skill
API
0 / 1An OpenAPI description is published MUST MISSING
Goal: Publish an OpenAPI description so non-MCP agents can call your HTTP API.
Result: Not found (https://docs.plaid.com/openapi.json -> 404 (status 404 not in [200]))
Fix: If your service exposes an HTTP/REST API (separate from any MCP endpoint), publish an OpenAPI 3.1 description of it at `/openapi.json` (or `/openapi.yaml`, or `/.well-known/openapi.json`). Non-MCP agents use it to discover endpoints, parameters, and response shapes, and to generate typed clients. A service whose only machine surface is MCP has no REST API to describe here.
Resources: OpenAPI 3.1 · Fix skill
Referenced JSON Schemas resolve as application/schema+json MAY N/A
Goal: Serve the JSON Schemas your API references so agents can validate payloads pre-flight.
Result: Not applicable (no JSON Schema references detected)
Resources: JSON Schema · Fix skill
MCP
0 / 0No checks in this category apply to this site.
initialize handshake returns serverInfo + protocolVersion MUST N/A
Goal: Answer JSON-RPC initialize with serverInfo and protocolVersion so clients can begin a session.
Result: Not applicable (no MCP endpoint discovered)
Resources: MCP lifecycle · Fix skill
initialize advertises capabilities (tools / resources / prompts) SHOULD N/A
Goal: Advertise the capability groups your MCP server implements in the initialize result.
Result: Not applicable (no MCP endpoint discovered)
Resources: MCP lifecycle · Fix skill
tools/list returns a tools array with input schemas MUST N/A
Goal: Return tools/list entries with name, description, and a JSON inputSchema.
Result: Not applicable (no MCP endpoint discovered)
unknown JSON-RPC method returns -32601 SHOULD N/A
Goal: Reject unknown JSON-RPC methods with error -32601 instead of a hang or 500.
Result: Not applicable (no MCP endpoint discovered)
Resources: JSON-RPC 2.0 · Fix skill
GET on the MCP endpoint answers fast (not a held-open hang) SHOULD N/A
Goal: Answer GET on the MCP endpoint fast (a fast-fail status or a documented surface), never a held-open hang.
Result: Not applicable (no MCP endpoint discovered)
Resources: MCP transports · Fix skill
CORS preflight (OPTIONS) succeeds with Access-Control-Allow-* headers SHOULD N/A
Goal: Answer OPTIONS preflights on the MCP endpoint with Access-Control-Allow-* headers.
Result: Not applicable (no MCP endpoint discovered)
Resources: MDN CORS preflight · Fix skill
POST response carries Access-Control-Allow-Origin SHOULD N/A
Goal: Echo Access-Control-Allow-Origin on the actual MCP POST response.
Result: Not applicable (no MCP endpoint discovered)
A .well-known MCP server card is published (SEP-1649) SHOULD N/A
Goal: Publish an MCP server card at the canonical SEP-1649 path and 301 the legacy aliases to it.
Result: Not applicable (no MCP endpoint discovered)
A human/agent usage doc for the server resolves MAY N/A
Goal: Publish a one-fetch markdown usage doc for your MCP server.
Result: Not applicable (no MCP endpoint discovered)
Resources: anc.dev example · Fix skill
Root HTML exposes WebMCP browser tools MAY N/A
Goal: Expose page tools to browser agents via WebMCP.
Result: Not implemented, optional (https://docs.plaid.com/ -> 200 (no WebMCP markers in root HTML))
Resources: WebMCP spec · Fix skill
Agent discovery & auth
0 / 0No checks in this category apply to this site.
OAuth/OIDC discovery metadata published MAY N/A
Goal: Publish OAuth/OIDC discovery metadata if agents authenticate to your service.
Result: Not applicable (no auth surface detected)
OAuth Protected Resource Metadata published (RFC 9728) MAY N/A
Goal: Publish RFC 9728 protected-resource metadata for your authenticated MCP server.
Result: Not applicable (MCP endpoint does not challenge for auth)
Agent auth/registration metadata doc published MAY N/A
Goal: Publish an auth.md telling agents how to obtain credentials.
Result: Not applicable (no auth surface detected)
Resources: anc.dev example · Fix skill
A2A Agent Card published for agent-to-agent discovery MAY N/A
Goal: Publish an A2A Agent Card for agent-to-agent discovery.
Result: Not implemented, optional (https://docs.plaid.com/.well-known/agent-card.json -> 404 (status 404 not in [200]))
Resources: A2A protocol · Fix skill
Agent-skills discovery index published MAY N/A
Goal: Publish an agent-skills discovery index so agents can enumerate your skills.
Result: Not implemented, optional (https://docs.plaid.com/.well-known/agent-skills/index.json -> 404 (status 404 not in [200]))
Resources: Agent Skills Discovery · Fix skill
This scorecard reflects the target's public agent-facing surface at audit time. Re-run the audit from anc.dev/web-audit to refresh it, or call the audit_website MCP tool.