mcp.hubspot.com agentic web readiness
C Manifest validity: 0 manifests published (0 errors, 4 warnings) · Surface score 20 (coverage 20 + breadth 0 + conformance 0). 2 standards observed across 2 of 9 steps; 0 manifests present, 0 errors, 4 warnings. Checked 2026-10-25 23:47:04 UTC. This grades the agent-facing files published at mcp.hubspot.com, not the organisation's products.
Coverage by step
Manifests
| Manifest | Result | Findings |
|---|---|---|
Agentic Resource Discovery/.well-known/ard.json | absent HTTP 404 | |
AI Catalog well-known file/.well-known/ai-catalog.json | absent HTTP 404 | |
MCP Server Cards (SEP-2127)/mcp/server-card | absent HTTP 404 | |
Agent2Agent Protocol/.well-known/agent-card.json | absent HTTP 404 | |
llms.txt/llms.txt | absent HTTP 404 | |
AGENTS.md/AGENTS.md | absent HTTP 404 | |
Agent Skills/.well-known/agent-skills/index.json | absent HTTP 404 | |
api-catalog: A Well-Known URI and Link Relation to Help Discovery of APIs/.well-known/api-catalog | absent HTTP 404 | |
AI Crawler User-Agent Tokens in robots.txt/robots.txt | no AI tokens |
|
security.txt (RFC 9116)/.well-known/security.txt | absent HTTP 404 | |
auth.md/auth.md | absent HTTP 404 | |
Open Knowledge Format/okf/index.md | absent HTTP 404 |
What an agent can call
- MCP endpoint
https://mcp.hubspot.com(streamable-http) — from/.well-known/oauth-protected-resource - robots.txt AI policy: no AI crawler tokens named; unlisted crawlers allowed on public paths (subpaths disallowed under User-agent: *)
- OAuth protected resource
https://mcp.hubspot.com, authorization servers: https://mcp.hubspot.com
Standards observed
- OAuth Protected Resource and Authorization Server Metadata (as used for agent authorization) https://mcp.hubspot.com/.well-known/oauth-protected-resource
- Model Context Protocol
Cheapest next steps
- llms.txt: one Markdown index file; the most widely read agent-facing file
Generate starter
/llms.txtfor mcp.hubspot.com# Mcp > Mcp and what it offers to agents Short notes an agent should know before using the site: what it is for, who runs it, how to cite it. ## Docs - [Getting started](https://mcp.hubspot.com/docs/getting-started): the first page to read - [API reference](https://mcp.hubspot.com/openapi.json): OpenAPI description ## Optional - [Changelog](https://mcp.hubspot.com/changelog): what changed, newest first
- Agentic Resource Discovery: a catalog at /.well-known/ard.json lets agents discover your APIs, MCP servers and data in one fetch
- AGENTS.md: instructions for coding agents working on or with the site
Generate starter
/AGENTS.mdfor mcp.hubspot.com# Mcp for agents Mcp and what it offers to agents ## Read the data, not the HTML - Index: https://mcp.hubspot.com/llms.txt - API description: https://mcp.hubspot.com/openapi.json - Discovery catalog: https://mcp.hubspot.com/.well-known/ard.json ## Calling - MCP server (Streamable HTTP): https://mcp.hubspot.com/mcp - Rate limits and authentication: describe them here ## Conventions - How to cite or attribute content - What not to do (no scraping of /account/, no automated sign-ups, etc.) Contact: security@mcp.hubspot.com
Agent pre-flight & practical readiness
Preferred mode: mcp. Call the MCP endpoint at https://mcp.hubspot.com first. Do not scrape the HTML when a tool can answer.
Fetch: POST https://mcp.hubspot.com POST a JSON-RPC tools/list, or server/discover on the 2026-07-28 revision, before reading HTML.
Practical readability: exa_parsable no, markdown negotiation no, render none, HTML quality none.
AI crawler posture: open_to_all · Assistant access: OpenAI partial, Anthropic partial, Google partial, Perplexity partial, Exa partial.
Readiness subscores: reach 20/20, readability 0/30, capabilities 14/35, conformance 0/15, total 34/100, grade C.
How the grade is made
+10 per lifecycle step with a standard observed, counting manifests that validate or that the probe rule for the standard recognises (a valid MCP server card counts for MCP; max 90); +3 per observed standard beyond the first two (max 15); conformance +15 (+10 with one manifest) minus 5 per agent-facing manifest with errors, never below 0 (security.txt is reported, not scored). Lifecycle grade: A+ >= 60, A >= 45, B >= 30, C >= 20, D >= 10. Strict 100-point composite (subscores.total_100 / subscores.grade_100): reach_and_policy (20) + readability (30) + capabilities (35) + conformance (15), where A+ >= 80, A >= 65, B >= 45, C >= 28, D >= 15. Errors are specification violations; warnings are best-practice gaps. Only public paths are fetched, without credentials, so standards that need a login (skipped in the probe) are not counted either way. The same report is the validate_manifest tool on the MCP server.
JSON · Markdown · probe rules