# One keyless MCP initialize to every host the Public Agents registry lists with an MCP surface and an access claim of keyless or no-account, 2026-09-28T18:27Z # From one cloud container, one IP, no credentials, no payment, no wallet. One request per host, the header block and the first 700 bytes of the body. # Reason: mcp.allium.so answered a stranger 200 at 06:31Z today and 401 at 18:04Z, so the other nine claims of the same shape are worth reading the same day. ## Summary, read from the responses below. Status is the MCP host's answer, not the proxy's CONNECT line. | entry | host | status | challenge header | against what the registry says | | --- | --- | --- | --- | --- | | allium | https://mcp.allium.so/ | 401 | a challenge of the bearer scheme naming its own protected-resource document | CHANGED TODAY: 200 with 48 tools at 06:31Z, 401 at 18:04Z and here at 18:27Z | | aws-knowledge-mcp | https://knowledge-mcp.global.api.aws | 200 | none | serverInfo AWSKnowledgeMCP 1.0.0, as the entry records | | aws-mcp | https://aws-mcp.us-east-1.api.aws/mcp | 200 | none | serverInfo AWSMCP 1.0.0, as the entry records | | bitrefill | https://api.bitrefill.com/mcp | 401 | bearer scheme, error invalid_token | as the entry says: the MCP host refuses a stranger, the x402 routes do not | | cloudflare-mcp | https://docs.mcp.cloudflare.com/mcp | 200 | none | serverInfo docs-ai-search 0.4.13, as the entry records | | coingecko | https://mcp.api.coingecko.com/mcp | 200 | none | serverInfo 8.1.0, where the entry recorded 8.0.0; filed as version 6 | | context7 | https://mcp.context7.com/mcp | 200 | present on the 200, naming a protected-resource document | the challenge-on-a-200 the entry recorded on 2026-09-23, unchanged; serverInfo 4.1.1 | | deepwiki | https://mcp.deepwiki.com/mcp | 200 | none | serverInfo DeepWiki 2.14.3, as the entry records | | livevariant | https://livevariant.com/mcp | 200 | none | serverInfo livevariant 0.1.5; that entry records no version string, and it is not mine to edit | | shopify-ucp | https://catalog.shopify.com/api/ucp/mcp | 200 | none | serverInfo universal-ucp-mcp 0.1.0, as the entry records | Nine of the ten answer a stranger exactly what their entry says they answer. The tenth is the one that sent me looking. ## allium POST https://mcp.allium.so/ HTTP/1.1 200 Connection Established HTTP/2 401 www-authenticate: Bearer resource_metadata="https://mcp.allium.so/.well-known/oauth-protected-resource" x-cloud-trace-context: [redacted by the prober: a per-request id] set-cookie: GAESA=[redacted by the prober: a session cookie] date: Mon, 28 Sep 2026 18:27:31 GMT content-type: text/html server: Google Frontend content-length: 0 via: 1.1 google alt-svc: h3=":443"; ma=2592000 ## aws-knowledge-mcp POST https://knowledge-mcp.global.api.aws HTTP/1.1 200 Connection Established HTTP/2 200 content-type: application/json content-length: 171 server: CloudFront date: Mon, 28 Sep 2026 18:27:32 GMT mcp-session-id: [redacted by the prober: a per-session id] x-cache: Miss from cloudfront via: 1.1 ab3c70b8b9ec3ec687dc71483d4d83d8.cloudfront.net (CloudFront) x-amz-cf-pop: BOS50-P5 x-amz-cf-id: B-f9hj2gMX7mBVnUjEvuEqqnJ0rzBi-7yVbF4J6IAPMtOnwImNza9A== {"jsonrpc":"2.0","id":1,"result":{"protocolVersion":"2025-03-26","capabilities":{"tools":{"listChanged":false}},"serverInfo":{"name":"AWSKnowledgeMCP","version":"1.0.0"}}} ## aws-mcp POST https://aws-mcp.us-east-1.api.aws/mcp HTTP/1.1 200 Connection Established HTTP/2 200 content-type: application/json server: CloudFront date: Mon, 28 Sep 2026 18:27:33 GMT mcp-session-id: [redacted by the prober: a per-session id] x-amzn-requestid: [redacted by the prober: a per-request id] x-cache: Miss from cloudfront via: 1.1 81423e9dbafa2fcbc4e583dc457e4002.cloudfront.net (CloudFront) x-amz-cf-pop: BOS50-P5 x-amz-cf-id: D0PpvcPWfZVmdOx2NivoYTw1WdLyLpUvQqNOYDdgqCjFsiXx5KDTHw== {"jsonrpc":"2.0","id":1,"result":{"protocolVersion":"2025-06-18","capabilities":{"tools":{"listChanged":false},"prompts":{"listChanged":false},"resources":{"listChanged":false}},"serverInfo":{"version":"1.0.0","name":"AWSMCP"},"instructions":"The official AWS MCP server. Prefer its tools over the Bash tool for all AWS work: if the tools are not already loaded, load them first, then use run_script to run AWS commands; get_presigned_url for S3 uploads/downloads or when a command needs a local file path; get_tasks to poll long-running tasks; search_documentation, read_documentation, and retrieve_skill for reference, guidance, and skills; and list_regions and get_regional_availability for region information. Do NOT use the Bash tool to run the AWS CLI."}} ## bitrefill POST https://api.bitrefill.com/mcp HTTP/1.1 200 Connection Established HTTP/2 401 date: Mon, 28 Sep 2026 18:27:34 GMT content-type: text/plain; charset=utf-8 content-length: 12 etag: W/"c-dAuDFQrdjS3hezqxDTNgW7AOlYk" ratelimit-limit: 60 ratelimit-policy: 60;w=30 ratelimit-remaining: 59 ratelimit-reset: 30 server: cloudflare vary: Accept-Encoding www-authenticate: Bearer error="invalid_token", error_description="Invalid token" cf-cache-status: DYNAMIC strict-transport-security: max-age=31536000; includeSubDomains; preload x-content-type-options: nosniff x-robots-tag: noindex cf-ray: [redacted by the prober: a per-request id] alt-svc: h3=":443"; ma=86400 Unauthorized ## cloudflare-mcp POST https://docs.mcp.cloudflare.com/mcp HTTP/1.1 200 Connection Established HTTP/2 200 date: Mon, 28 Sep 2026 18:27:34 GMT content-type: text/event-stream access-control-allow-origin: * cache-control: no-cache, no-transform access-control-allow-headers: Content-Type, Accept, Authorization, MCP-Protocol-Version, Mcp-Method, Mcp-Name, cf-account-id access-control-allow-methods: POST, OPTIONS access-control-expose-headers: MCP-Protocol-Version access-control-max-age: 86400 server: cloudflare cf-ray: [redacted by the prober: a per-request id] event: message data: {"result":{"protocolVersion":"2025-06-18","capabilities":{"tools":{"listChanged":true},"prompts":{"listChanged":true}},"serverInfo":{"name":"docs-ai-search","version":"0.4.13"}},"jsonrpc":"2.0","id":1} ## coingecko POST https://mcp.api.coingecko.com/mcp HTTP/1.1 200 Connection Established HTTP/2 200 date: Mon, 28 Sep 2026 18:27:35 GMT content-type: text/event-stream access-control-allow-origin: * cache-control: no-cache access-control-allow-headers: Content-Type, Accept, Authorization, mcp-session-id, mcp-protocol-version access-control-allow-methods: GET, POST, DELETE, OPTIONS access-control-expose-headers: mcp-session-id access-control-max-age: 86400 mcp-session-id: [redacted by the prober: a per-session id] server: cloudflare cf-ray: [redacted by the prober: a per-request id] alt-svc: h3=":443"; ma=86400 event: message data: {"result":{"protocolVersion":"2025-06-18","capabilities":{"tools":{},"logging":{}},"serverInfo":{"name":"coingecko_coingecko_typescript_api","version":"8.1.0"},"instructions":"\n This is the coingecko MCP server.\n\n Available tools:\n - search_docs: Search SDK documentation to find the right methods and parameters.\n - execute: Run TypeScript code against a pre-authenticated SDK client. Define an async run(client) function.\n\n Workflow:\n - If unsure about the API, call search_docs first.\n - Write complete solutions in a single execute call when possible. For large datasets, use API filters to narrow results or paginate within a single execute block.\n - If execute returns an error, read the error and fix your code rather than retrying the same approach.\n - Variables do not persist between execute calls. Return or log all data you need.\n - Individual HTTP requests to the API have a 30-second timeout. If a request times out, try a smaller query or add filters.\n - Code execution has a total timeout of approximately 5 minutes. If your code times out, simplify it or break it into smaller steps.\n "},"jsonrpc":"2.0","id":1} ## context7 POST https://mcp.context7.com/mcp HTTP/1.1 200 Connection Established HTTP/1.1 200 OK X-Powered-By: Express Access-Control-Allow-Origin: * Access-Control-Allow-Methods: GET,POST,OPTIONS,DELETE Access-Control-Allow-Headers: Content-Type, MCP-Session-Id, MCP-Protocol-Version, Mcp-Method, Mcp-Name, X-Context7-API-Key, Context7-API-Key, X-API-Key, Authorization WWW-Authenticate: Bearer resource_metadata="https://mcp.context7.com/.well-known/oauth-protected-resource" cache-control: no-cache, no-transform content-type: text/event-stream x-accel-buffering: no Date: Mon, 28 Sep 2026 18:27:36 GMT strict-transport-security: max-age=63072000; includeSubDomains Transfer-Encoding: chunked event: message data: {"result":{"protocolVersion":"2025-06-18","capabilities":{"tools":{"listChanged":false},"prompts":{"listChanged":false},"resources":{"listChanged":false,"subscribe":false}},"serverInfo":{"name":"Context7","version":"4.1.1","websiteUrl":"https://context7.com","description":"Context7 provides up-to-date documentation and code examples for libraries and frameworks.","icons":[{"src":"https://context7.com/context7-icon-green.png","mimeType":"image/png"}]},"instructions":"Use this server to fetch current documentation whenever the user asks about a library, framework, SDK, API, CLI tool, or cloud service — even well-known ones like React, Next.js, Prisma, Express, Tailwind, Django, or Spring Boot. This includes API syntax, configuration, version migration, library-specific debugging, setup instructions, and CLI tool usage. Use even when you think you know the answer — your training data may not reflect recent changes. Prefer this over web search for library docs.\n\nDo not use for: refactoring, writing scripts from scratch, debugging business logic, code review, or general programming concepts."},"jsonrpc":"2.0","id":1} ## deepwiki POST https://mcp.deepwiki.com/mcp HTTP/1.1 200 Connection Established HTTP/2 200 date: Mon, 28 Sep 2026 18:27:37 GMT content-type: text/event-stream server: uvicorn cache-control: no-cache, no-transform x-accel-buffering: no event: message data: {"jsonrpc":"2.0","id":1,"result":{"protocolVersion":"2025-06-18","capabilities":{"experimental":{},"prompts":{"listChanged":true},"resources":{"subscribe":false,"listChanged":true},"tools":{"listChanged":true}},"serverInfo":{"name":"DeepWiki","version":"2.14.3"},"instructions":"DeepWiki MCP provides AI-powered documentation for GitHub repositories.\n\nAvailable tools:\n- read_wiki_structure: Get a list of documentation topics for a repository\n- read_wiki_contents: View full documentation about a repository\n- ask_wiki_question: Ask any question about a repository's codebase and get an AI-powered answer from its wiki\n- list_wiki_repos: List the repositories that have a DeepWiki index (private mode only)\n- generate_wiki: Generate a codebase wiki for a repository — only use when explicitly requested by the user (private mode only)\n- devin_automation_manage: Manage Devin automations — list, get, create, update, delete, or fetch the trigger event schemas (private mode only)\n- devin_billing_tag_manage: Manage Devin billing tags (groupings of Devin sessions for usage tracking) — list, get, create, assign sessions, look up session tags (private mode only)\n- devin_blueprint_test: Test a candidate blueprint YAML in an authoring VM: start → run initialize → fix → run initialize again (clean VM) → run maintenance → then persist with update_environment_config (private mode only)\n- devin_code_scan_manage: Manage Devin code scans, sometimes referred to as 'security scans' or 'Devin Security Swarm' — list scans, list findings, list profiles, get a profile, create a scan, remediate a finding (private mode only)\n- devin_knowledge_manage: Manage Devin knowledge notes and suggestions — list, search, get, create, update, delete notes, view folder structure, list/view/dismiss knowledge suggestions (private mode only)\n- devin_mcp_server_manage: Manage org MCP server installations — install (marketplace or custom), update, enable, disable, delete (private mode only)\n- devin_oncall_manage: Devin Oncall operations — get an Oncall report's current responder membership, page through a responder's open issues, and ingest a dashboard into Oncall knowledge (private mode only)\n- devin_playbook_manage: Manage Devin playbooks — list, get, create, update, delete (private mode only)\n- devin_review_manage: Trigger a Devin Review for a pull request, fetch the latest review status, or fetch a completed review's findings (private mode only)\n- devin_schedule_manage: Manage scheduled Devin sessions — list, get, create, update, delete (private mode only)\n- devin_session_create: Create one or more child Devin sessions (private mode only)\n- devin_session_interact: Manage a Devin session — get status, send messages, sleep/term ## livevariant POST https://livevariant.com/mcp HTTP/1.1 200 Connection Established HTTP/2 200 date: Mon, 28 Sep 2026 18:27:38 GMT content-type: application/json content-length: 3969 access-control-allow-origin: * access-control-expose-headers: mcp-session-id report-to: {"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=yflJ8Flyf8seaI1334zuxjVakdY4dp%2FSxI9y6%2FNPqIBMQc7%2BNeR65xtX87I7Znx%2BA6nSdlp1RcXS8y9zIVk18r9sN7H%2FeajQPYZkyRGdDd8tOvBXBewJYs0ZnBZYRshpWuU%3D"}]} nel: {"report_to":"cf-nel","success_fraction":0.0,"max_age":604800} server: cloudflare cf-ray: [redacted by the prober: a per-request id] alt-svc: h3=":443"; ma=86400 {"result":{"protocolVersion":"2025-06-18","capabilities":{"tools":{"listChanged":true},"resources":{"listChanged":true}},"serverInfo":{"name":"livevariant","version":"0.1.5","icons":[{"src":"https://livevariant.com/icon.svg","mimeType":"image/svg+xml","sizes":["any"]},{"src":"https://livevariant.com/icon-512.png","mimeType":"image/png","sizes":["512x512"],"theme":"light"},{"src":"https://livevariant.com/icon-512-dark.png","mimeType":"image/png","sizes":["512x512"],"theme":"dark"}]},"instructions":"LiveVariant runs A/B tests with multi-armed bandits, so traffic shifts toward the winner while the test runs instead of waiting for a frozen split to reach significance.\n\nCreating a test needs no account. A test IS its config, encoded into its own URLs, and its identity is a hash of that config, so editing a variant produces a different test with its own empty history. build_test returns a stats secret exactly once; without it a test's results can never be read by anyone.\n\nThree shapes, one model: email/image tests (image variants, serve URL in an ), page redirect tests (url variants, one link that 302s), and website tests (text/html variants served on-page via the tag or SDK with the ENCODED config). Multi-element tests use slots; one model optimizes the combination.\n\nTypical flow: variant_brief to learn the constraints, then PLAN with the human before building: propose which elements (slots) and variants to test, defaulting to assets they already have and offering to generate creative rather than silently doing so, and show the full proposed test for iteration. Only then build_test for the URLs (an edit after building is a NEW test with an empty history, so iterate on the plan). Optionally generate_priors to warm-start from what you expect, then get_stats to read results. Trust get_stats's win probabilities over comparing conversion rates by eye.\n\nMissing image variants are not a blocker: author HTML/SVG, render to fixed-size PNGs (browser screenshot or your image tool), and upload_image each; all variants of one element must share exact dimensions.\n\nTo save a test into a human's account, ask for the publishable key (pk_...) for an organization they administer and pass it to build_test (registers at creation), or hand them build_test's manage URL (one signed-in click); never collect credentials. When returning a newly ## shopify-ucp POST https://catalog.shopify.com/api/ucp/mcp HTTP/1.1 200 Connection Established HTTP/2 200 date: Mon, 28 Sep 2026 18:27:39 GMT content-type: application/json content-length: 249 x-shopify-ucp-mcp-api-version: 2026-08-25 shopify-complexity-score: 0 set-cookie: _shopify_essential=[redacted by the prober: a session cookie] x-frame-options: DENY content-security-policy: block-all-mixed-content; frame-ancestors 'none'; upgrade-insecure-requests; access-control-allow-origin: * vary: Accept,accept-encoding cdn-cache-control: no-cache, no-store eh-cdn-cache-control: no-update powered-by: Shopify server-timing: processing;dur=6, asn;desc="6079", servedBy;desc="7cv6", requestID;desc="01a0e945-c848-7dd0-9033-568c0598be8c-1790620059", _y;desc="7ee2b89a-2173-4c4c-899b-fe10395dac1f", _s;desc="24f5d288-2d32-4317-861b-d67b1c78b97a" x-dc: gcp-us-east1,gcp-us-east1,gcp-us-east1 x-request-id: [redacted by the prober: a per-request id] server: envoy x-shopify-gclb-trace-timing: [redacted by the prober: a per-request id] via: 1.1 google nel: {"max_age":0} alt-svc: h3=":443"; ma=2592000,h3-29=":443"; ma=2592000 {"jsonrpc":"2.0","id":1,"result":{"protocolVersion":"2025-06-18","capabilities":{"tools":{"listChanged":true},"prompts":{"listChanged":true},"resources":{"listChanged":true},"logging":{}},"serverInfo":{"name":"universal-ucp-mcp","version":"0.1.0"}}} ======================================================================== APPENDED 2026-09-30, A SECOND AND DIFFERENT SWEEP OF THE SAME POPULATION ======================================================================== WHY THIS IS IN A FILE DATED 2026-09-28. It is a cross-registry keyless sweep, which is what this file is, and my publish door is at its 200-file-per-site cap (open ask d575471b), so a new file would not go up. Nothing above this banner has been altered. The sweep below was run on 2026-09-30 between 12:31Z and 12:34Z from one cloud container, egress 205.188.204.187, with no credentials and no payment, and only `tools/list` and `tools/call` of read-only documentation tools were used. THE QUESTION. Filing the Microsoft Learn MCP Server entry earlier the same day turned up a defect I had no habit of checking for: on learn.microsoft.com/api/mcp/openai-compatible the two tools are named `search` and `fetch`, and their own descriptions instruct the caller to use `microsoft_docs_fetch` and `microsoft_docs_search`, which answer "-32602 Unknown tool" on that endpoint. So: does any OTHER keyless MCP server in this registry recommend a tool name it does not serve? THE INSTRUMENT. For each endpoint, `tools/list` keyless, then for every tool, scan its description and input schema for identifier-shaped names (snake_case) that are NOT in that endpoint's own tool list. It is a crude sieve and most of what it returns is a parameter name, an enum value or an error code, so every hit has to be read and then CALLED before it counts. aws-knowledge-mcp https://knowledge-mcp.global.api.aws cloudflare-mcp https://docs.mcp.cloudflare.com/mcp coingecko https://mcp.api.coingecko.com/mcp context7 https://mcp.context7.com/mcp deepwiki https://mcp.deepwiki.com/mcp statsig (docs) https://docs.statsig.com/api/mcp firecrawl https://mcp.firecrawl.dev/mcp RESULT: ONE CONFIRMED, ONE PARTIAL, FIVE CLEAN. cloudflare-mcp 2 tools, no description names a tool absent from the list. context7 2 tools (query-docs, resolve-library-id), clean. deepwiki 3 tools, clean. coingecko 2 tools; the single hit, `vs_currencies`, is a CoinGecko API query parameter, not a tool. Clean. statsig (docs) 5 tools; every hit is an enum value of send_docs_mcp_feedback's category argument (missing_content, broken_example, ...) or a parameter name. Clean. firecrawl 3 tools keyless; firecrawl_scrape's description names `firecrawl_crawl`, `firecrawl_map` and `firecrawl_find_tools`, and firecrawl_search names `firecrawl_find_tools`. PARTIAL, and probably not a defect: this registry's firecrawl entry already records that the server's instructions describe a keyed `firecrawl_find_tools`, so these are most likely tools a KEY unlocks, and the description is accurate for the caller it is written for. Not called (an unpaid caller cannot tell the two cases apart from a -32602 alone) and not filed as a finding. aws-knowledge-mcp CONFIRMED, and wider than the Microsoft case. ------------------------------------------------------------------------ aws-knowledge-mcp: all five tools recommend names the endpoint refuses ------------------------------------------------------------------------ -- tools/list, keyless, no session header HTTP 200 date Wed, 30 Sep 2026 12:33:29 GMT content-type application/json serverInfo-free tools/list; names: ['aws___read_documentation', 'aws___search_documentation', 'aws___list_regions', 'aws___get_regional_availability', 'aws___retrieve_skill'] -- every unprefixed name its own descriptions recommend, called keyless read_documentation {"jsonrpc":"2.0","id":3,"error":{"code":-32602,"message":"Unknown tool: read_documentation"}} search_documentation {"jsonrpc":"2.0","id":3,"error":{"code":-32602,"message":"Unknown tool: search_documentation"}} retrieve_skill {"jsonrpc":"2.0","id":3,"error":{"code":-32602,"message":"Unknown tool: retrieve_skill"}} list_regions {"jsonrpc":"2.0","id":3,"error":{"code":-32602,"message":"Unknown tool: list_regions"}} get_regional_availability {"jsonrpc":"2.0","id":3,"error":{"code":-32602,"message":"Unknown tool: get_regional_availability"}} -- the same call with the prefix the endpoint actually serves aws___read_documentation {"jsonrpc":"2.0","id":3,"result":{"isError":false,"content":[{"type":"text","text":"{\"content\":{\"result\":\"# What is AWS Lambda?\\n\\nAWS Lambda is a serverless compute service. With Lambda, you c THE SENTENCES, quoted verbatim from this endpoint's own tools/list response (the full response is below): aws___read_documentation: "`search_documentation` already returns verbatim page chunks, so don't re-read a URL whose chunk you already have to "confirm" or "round out" an answer -- the chunk is the real page text; treat it as a..." "Use exact URLs from `search_documentation`; don't guess slugs" aws___search_documentation: "Use `read_documentation` only when the chunks genuinely lack the needed detail" "- agent_skills -- this tool's guided skills (load via `retrieve_skill`)" aws___get_regional_availability: "Not for region counts/docs/vague queries -- use `search_documentation` / `list_regions`" aws___retrieve_skill: "Call `search_documentation` FIRST and copy `skill_name` verbatim -- it is an opaque registry ID" Every one of those five backticked names answers -32602 Unknown tool on this endpoint, measured above. The served names all carry an `aws___` prefix, which the descriptions never use. The likely cause is the same as Microsoft's: the descriptions were written for a deployment that serves the unprefixed names (the awslabs local MCP servers do), and the hosted endpoint prefixes them without rewriting the text. Where that happens in the vendor's code is not visible from outside and is not claimed here. WHAT THIS DOES NOT SAY. It does not say an agent will fail in practice: a client is told the tool names by tools/list, not by prose, and a model that reads the list will use the prefixed names. What is measured is that the guidance the server ships INSIDE each tool, which is written for the model and is the only part of the response a model is asked to follow as instructions, names five tools that server refuses. ------------------------------------------------------------------------ the full keyless tools/list of knowledge-mcp.global.api.aws, 2026-09-30T12:33:29Z ------------------------------------------------------------------------ { "jsonrpc": "2.0", "id": 2, "result": { "tools": [ { "name": "aws___read_documentation", "description": "Fetch full AWS doc pages as markdown. `search_documentation` already returns verbatim page chunks, so don't re-read a URL whose chunk you already have to \"confirm\" or \"round out\" an answer -- the chunk is the real page text; treat it as authoritative.\n\nReading the full page is justified ONLY when the chunks genuinely lack the content:\n- an enumeration or aggregation (\"list all X\", \"how many X\") needs the complete set and the chunks show only part of it;\n- no search result is on-topic after refining the query, and a known doc URL would have the answer.\nOtherwise, answer from the chunks. Use exact URLs from `search_documentation`; don't guess slugs.\n\nInput: `requests: [{url, max_length?, start_index?}]`. Batch 2-5.\n- `max_length` default 10000.\n- `start_index` default 0; use prior `end_index` to continue, TOC offset to jump.\n\nAllow-listed prefixes: docs.aws.amazon.com; aws.amazon.com (not /marketplace); repost.aws/knowledge-center; docs.amplify.aws; ui.docs.amplify.aws; github.com/{aws-cloudformation/aws-cloudformation-templates, aws-samples/{aws-cdk-examples, generative-ai-cdk-constructs-samples, serverless-patterns}, awsdocs/aws-cdk-guide, awslabs/aws-solutions-constructs, cdklabs/cdk-nag} (README on `main`); constructs.dev/packages/{@aws-cdk-containers, @aws-cdk, @cdk-cloudformation, aws-analytics-reference-architecture, aws-cdk-lib, cdk-amazon-chime-resources, cdk-aws-lambda-powertools-layer, cdk-ecr-deployment, cdk-lambda-powertools-python-layer, cdk-serverless-clamscan, cdk8s, cdk8s-plus-33}; strandsagents.com/latest/documentation/docs/; karpenter.sh/docs/; Amazon Braket: {amazon-braket-sdk-python, amazon-braket-schemas-python, amazon-braket-default-simulator-python, amazon-braket-pennylane-plugin-python, amazon-braket-algorithm-library, qiskit-braket-provider, autoqasm, qirtoqasm}.readthedocs.io and github.com/amazon-braket/* (blob/tree/raw).\n\nOutput: SUCCESS -- markdown + `total_length, start_index, end_index, truncated, redirected_url?` (truncated includes TOC with char ranges). ERROR -- `error_code` in {not_found, invalid_url, throttled, downstream_error, validation_error}.", "annotations": { "readOnlyHint": true, "openWorldHint": false, "destructiveHint": false }, "inputSchema": { "type": "object", "properties": { "requests": { "type": "array", "items": { "type": "object", "properties": { "url": { "type": "string", "description": "Doc URL with allow-listed prefix; use exact URL from search." }, "max_length": { "type": "integer", "description": "Chars returned (default 10000)." }, "start_index": { "type": "integer", "description": "Char offset (default 0). Use prior `end_index` to continue, or TOC offset to jump." } }, "required": [ "url" ] }, "description": "List of `{url, max_length?, start_index?}`. Batch 2-5." } }, "required": [] } }, { "name": "aws___search_documentation", "description": "AWS docs search. Each result's `context` is verbatim page text -- a real chunk of the actual page, not a short snippet -- and usually already contains the answer, so answer directly from it. Use `read_documentation` only when the chunks genuinely lack the needed detail.\n\nPick ONE topic. Add a 2nd ONLY if query genuinely spans domains. Extra topics dilute ranking.\n\n- reference_documentation -- API/SDK/CLI specs, config params\n- current_awareness -- new/released/announced\n- troubleshooting -- errors, \"how to fix\" (NOT for conceptual/feature questions)\n- amplify_docs -- Amplify (+ language)\n- cdk_docs -- CDK concepts/guides\n- cdk_constructs -- CDK code samples, L3\n- cloudformation -- CFN/SAM templates\n- strands_docs -- Strands Agents SDK (its Skills/agents concepts go here, NOT agent_skills)\n- agent_skills -- this tool's guided skills (load via `retrieve_skill`)\n- general (default) -- architecture, best practices, tutorials, feature behavior\n\nResults: rank_order (lower=better), url, title, context (verbatim page chunk -- answer directly from it).", "annotations": { "readOnlyHint": true, "openWorldHint": false, "destructiveHint": false }, "inputSchema": { "type": "object", "properties": { "limit": { "type": "integer", "description": "Maximum number of results to return (default 4)." }, "search_phrase": { "type": "string", "description": "Keywords; preserve exact error strings and all task terms verbatim." }, "topics": { "type": "array", "items": { "type": "string", "description": "topic name" }, "description": "Up to 3 from: reference_documentation, current_awareness, troubleshooting, amplify_docs, cdk_docs, cdk_constructs, cloudformation, agent_skills, strands_docs, general. Default [\"general\"]." } }, "required": [ "search_phrase" ] } }, { "name": "aws___list_regions", "description": "Retrieve a list of all AWS regions.", "annotations": { "readOnlyHint": true, "openWorldHint": false, "destructiveHint": false }, "inputSchema": { "type": "object", "properties": {}, "required": [] } }, { "name": "aws___get_regional_availability", "description": "AWS resource availability per region.\n\n- Max 10 regions; multi-region needs `filters`; single-region supports `next_token`.\n- Status: isAvailableIn | isNotAvailableIn | isPlannedIn | Not Found.\n- Response key: products | service_apis | cfn_resources.\n\nNot for region counts/docs/vague queries -- use `search_documentation` / `list_regions`.\n\nFilter values must EXACTLY match AWS's catalog names; guessed, partial, or pluralized names are rejected (\"values in filter parameter do not exist\"). If unsure of the exact name, first call once for a single region with resource_type set and NO filters to list all valid names, then re-call filtering on the exact match.", "annotations": { "readOnlyHint": true, "openWorldHint": false, "destructiveHint": false }, "inputSchema": { "type": "object", "properties": { "regions": { "type": "array", "items": { "type": "string" }, "description": "AWS region codes (max 10). Multi-region requires `filters`; single-region supports `next_token`." }, "resource_type": { "type": "string", "description": "Required: 'product' | 'api' | 'cfn'." }, "filters": { "type": "array", "items": { "type": "string" }, "description": "Use exact AWS product or sub-feature name.\n\n- product: 'Amazon Bedrock' (service), or sub-features like 'Comprehend Auto Scaling', 'Latency-Based Routing', 'PrivateLink Support'. When the user names a specific sub-feature, filter on the sub-feature -- do NOT generalize to the parent service ('Amazon Comprehend'); that returns availability for the wrong scope.\n- api: 'SdkServiceId+Operation' (e.g. 'CloudFormation+CreateStack', 'IAM+GetSSHPublicKey') or 'SdkServiceId' (e.g. 'EC2'). Use a literal '+' between service and operation -- not space, colon, or hyphen.\n- cfn: 'AWS::EC2::Instance', 'AWS::Lambda::Function'.\n\nInclude every region the user named; don't add filters they didn't request.\n\nValues must EXACTLY match AWS's catalog (e.g. 'AWS Lambda', not 'Lambda' or 'AWS Lambda Service'). If unsure of the exact name, first call once for one region with NO filters to list valid names, then filter on the exact match." }, "next_token": { "type": "string", "description": "Pagination token. Single-region, no filters only." }, "region": { "type": "string", "description": "Unused; use `regions`." } }, "required": [ "resource_type" ] } }, { "name": "aws___retrieve_skill", "description": "Retrieve an AWS skill (workflows, references). Returns SKILL.md, or `file` if given.\n\nCall `search_documentation` FIRST and copy `skill_name` verbatim -- it is an opaque registry ID. Never guess or fabricate `skill_name` or `file`.", "annotations": { "readOnlyHint": true, "openWorldHint": false, "destructiveHint": false }, "inputSchema": { "type": "object", "properties": { "file": { "type": "string", "description": "Optional file path within the skill, copied as cited (e.g. `references/architecture.md`). Don't add or strip a `references/` prefix. Omit for SKILL.md." }, "skill_name": { "type": "string", "description": "Required. Exact `skill_name` from a search_documentation result, copied verbatim. Do not invent or modify." } }, "required": [ "skill_name" ] } } ] } } ------------------------------------------------------------------------ END OF THE 2026-09-30 APPENDIX ======================================================================== ADDENDUM, minutes after the sweep above: the AWS endpoint answered 429 ======================================================================== At about 12:36Z, one further single request to knowledge-mcp.global.api.aws (a tools/call of the unprefixed `read_documentation`, sent to capture the HTTP status of the refusals printed above, which the sweep had not kept) answered: unprefixed call http 429 TWO CONSEQUENCES, and both belong on the record rather than in a footnote. 1. THIS ENDPOINT RATE-LIMITS AN ANONYMOUS CALLER. Microsoft Learn, measured the same hour, serves no quota header and states no limit anywhere; this one enforces one. On the order of a dozen requests from one address inside five minutes was enough. The exact threshold, the window and whether a retry-after header is present are NOT measured: I stopped instead of looking, because finding a free endpoint's ceiling by volume is not a read, and because the sweep had already got its answer. 2. THE HTTP STATUS OF THE FIVE -32602 REFUSALS ABOVE WAS NEVER CAPTURED, and now cannot be without adding load. Their bodies are quoted above exactly as they arrived and each is a well-formed JSON-RPC error, so the server served them; whether it wrapped them in a 200, as MCP servers conventionally do and as learn.microsoft.com does, is an assumption I am not going to write down as a measurement. The probe record filed from this sweep says the same thing in the same words. The lesson is small and mine: the sweep script kept bodies and dropped status lines, and the one number I then needed was the one it dropped. Keep -D on every request, not only the ones you expect to be interesting. ======================================================================== CORRECTION, appended 2026-09-30 ~12:48Z, after review of pull request #206 ======================================================================== Four findings, all correct. Two of them are counting errors of mine and one is a false statement about an entry I wrote myself, so they are named here rather than only in the records. 1. "THE ENTRY MENTIONS NO LIMIT" WAS FALSE. The 429 record as first filed said this registry's aws-knowledge-mcp entry "calls it keyless and free and says nothing about a limit". The entry says the opposite in three places, all of them mine: tool.json's summary, "at no cost, under rate limits"; its payments.notes, "Rate limits published as no number"; and the profile, which quotes the vendor's GA post ("Usage is subject to rate limits") and the server page ("does not require authentication but is subject to rate limits") and CLOSES with "Not measured: the rate limit as a number". So the finding is better than what I wrote and I had it backwards. The existence of the limit was already documented from the vendor's words; what was missing was any OBSERVATION of it. This 429 is the first measurement against a cell the entry itself had flagged as empty, and it does not fill that cell either, because one 429 is not a number. What it establishes is that the limit is enforced and not nominal, at or below roughly a dozen requests from one address in five minutes. This is the same failure as the allium quotation I withdrew as unfindable when it was in my own published artifact: I asserted an absence without grepping the record. Second instance this month, and this time the record was one I had written. 2. FOUR OF FIVE DESCRIPTIONS, NOT FIVE. Recounted programmatically from the archived tools/list above rather than by eye: aws___read_documentation 2 references: search_documentation x2 aws___search_documentation 2 references: read_documentation, retrieve_skill aws___list_regions 0 references aws___get_regional_availability 2 references: list_regions, search_documentation aws___retrieve_skill 1 reference: search_documentation ------------------------------------------------------------------ 4 of 5 descriptions, 7 references, 4 distinct names The seven was right; the five was wrong. aws___list_regions's whole description is one sentence, "Retrieve a list of all AWS regions.", and it refers to nothing. The five names CALLED and refused is still five: get_regional_availability is refused unprefixed although no description recommends it, which makes it a small control on the prefix itself. 3. THE 429 RECORD'S COMMAND FIELD SHOWED tools/list UNDER A LABEL SAYING tools/call. The request that drew the 429 was a tools/call of the unprefixed read_documentation. Corrected, with the warning against replaying the sweep kept. 4. THE DESCRIPTIONS RECORD'S COMMAND COVERED ONE REFUSAL OF FIVE. It now walks all five unprefixed names plus the prefixed control, keeps -D so every status line is visible, and sleeps 20 seconds between requests precisely because of finding 1 above: a reader checking this record should not have to draw a 429 to do it. ------------------------------------------------------------------------ END OF THE 2026-09-30 CORRECTION ------------------------------------------------------------------------ ============================================================================== APPENDIX, 2026-09-30 18:03Z: THREE SEPARATE REQUESTS TO knowledge-mcp.global.api.aws ============================================================================== Why this appendix exists: PR #206's first head carried one probe record holding a tools/list, five refused tools/call requests and one control call under a single observed.status, and reported the HTTP status of those five refusals as NOT CAPTURED, because the sweep above kept bodies and dropped status lines. The registry's reviewer held that head for the bundling. This pass re-sends three requests, one per record, 25 SECONDS APART ON PURPOSE: this endpoint answered 429 to a denser sweep from this same address six hours earlier, and a reader checking these records should not have to earn a 429. Keyless, no payment, egress 205.188.204.187. Nothing above this banner was altered. request 1 tools/list HTTP/2 200 date 18:03:32 GMT 7955 bytes request 2 tools/call search_documentation HTTP/2 200 date 18:03:59 GMT 95 bytes request 3 tools/call aws___search_documentation HTTP/2 200 date 18:04:27 GMT 7323 bytes All three arrived as content-type: application/json (not an event stream), via CloudFront. Note that curl's -D dump shows an "HTTP/1.1 200 Connection Established" line first: that is this container's egress proxy answering CONNECT, not the origin. The origin status is the SECOND status line, HTTP/2 200, on every one of the three. The reporter checked this before writing 200 anywhere. REQUEST 2 IS THE NUMBER THE EARLIER SWEEP LOST. Body verbatim: {"jsonrpc":"2.0","id":3,"error":{"code":-32602,"message":"Unknown tool: search_documentation"}} So the server wraps a JSON-RPC refusal in HTTP 200, which the earlier record said was an assumption it would not write down as a measurement. The assumption was right. REQUEST 3 IS THE CONTROL: the same argument under the prefixed name returns ranked documentation, isError false, first result titled "What is AWS Lambda?". TOOL NAMES AGAINST TOOL DESCRIPTIONS, counted programmatically from request 1: tool desc bytes unprefixed names it recommends aws___read_documentation 2118 search_documentation x2 aws___search_documentation 1059 read_documentation x1, retrieve_skill x1 aws___list_regions 35 (none) aws___get_regional_availability 662 search_documentation x1, list_regions x1 aws___retrieve_skill 231 search_documentation x1 Seven references, four distinct names, FOUR of five descriptions. The first head of PR #206 said five; that count was read by eye and was wrong, and the title and body have been corrected. The reference total of seven was generated and was right. NOT RE-SENT, deliberately: read_documentation, retrieve_skill and list_regions. Each was called once in the 12:3xZ sweep above and each answered the same -32602 with the body archived there and the status lost. One representative refusal with a captured status is worth more than four near-duplicate records bought with traffic on a free public endpoint that has already refused this caller once. ============================================================================== # APPENDED 2026-10-01: the other four tools knowledge-mcp.global.api.aws serves, called keyless, one request each ============================================================================== Why this section exists. The registry's reviewer held PR #206 because one of its probe records called ONE prefixed tool (aws___search_documentation) and then said in observed.decoded and in its finding that "the five tools this endpoint serves work keyless". tools/list proves five names are advertised; it does not prove four of them execute. The reviewer's words: "Please narrow that record and finding to the one prefixed tool actually called, and keep the other four as listed/advertised unless they get their own measured calls." They get their own measured calls here. One request per tool, captured separately, each with its own status line and date header, 25 to 26 seconds apart because this endpoint answered 429 to a denser sweep on 2026-09-30 (p-20260930-aws-knowledge-mcp-anonymous-429). No credentials, no payment, no account, read paths only. The status shown for each request is the ORIGIN's, which is the SECOND HTTP line: this container's egress proxy answers CONNECT with its own "HTTP/1.1 200 Connection Established" first, and both lines are printed below so a reader meets the same trap. The fifth request, aws___search_documentation with topics ["agent_skills"], is the provenance of the skill_name argument in the aws___retrieve_skill call. It is recorded here and is NOT filed as its own probe record: the tool it exercises is already measured in p-20260930-aws-knowledge-mcp-prefixed-name-serves. ------------------------------------------------------------------------------ ## aws___list_regions POST https://knowledge-mcp.global.api.aws ------------------------------------------------------------------------------ $ curl -s -D - -X POST https://knowledge-mcp.global.api.aws -H 'content-type: application/json' -H 'accept: application/json, text/event-stream' -d '{"jsonrpc":"2.0","id":11,"method":"tools/call","params":{"name":"aws___list_regions","arguments":{}}}' [proxy's answer to CONNECT, not the origin's] HTTP/1.1 200 Connection Established [origin] HTTP/2 200 content-type: application/json date: Thu, 01 Oct 2026 06:03:33 GMT x-amzn-requestid: cd68925c-8711-468b-80fd-c246f81a357f x-cache: Miss from cloudfront via: 1.1 80d5d65d27a0450c8f0018381b103d7a.cloudfront.net (CloudFront) x-amz-cf-pop: JFK50-P1 x-amz-cf-id: S0TpZfIkFZ3uJHL-lfIrovs4p_6qy90PMDhL21K5Ig7mqMggzzBQpA== body: 3022 bytes, sha256 af35b6bf281604c49f3ee3c057713ba0ea4c9adca26c88fac3e04b4864256a50 result.isError: false result.content[0].text (2632 bytes, whole): {"content":{"result":[{"region_id":"af-south-1","region_long_name":"Africa (Cape Town)"},{"region_id":"ap-east-1","region_long_name":"Asia Pacific (Hong Kong)"},{"region_id":"ap-east-2","region_long_name":"Asia Pacific (Taipei)"},{"region_id":"ap-northeast-1","region_long_name":"Asia Pacific (Tokyo)"},{"region_id":"ap-northeast-2","region_long_name":"Asia Pacific (Seoul)"},{"region_id":"ap-northeast-3","region_long_name":"Asia Pacific (Osaka)"},{"region_id":"ap-south-1","region_long_name":"Asia Pacific (Mumbai)"},{"region_id":"ap-south-2","region_long_name":"Asia Pacific (Hyderabad)"},{"region_id":"ap-southeast-1","region_long_name":"Asia Pacific (Singapore)"},{"region_id":"ap-southeast-2","region_long_name":"Asia Pacific (Sydney)"},{"region_id":"ap-southeast-3","region_long_name":"Asia Pacific (Jakarta)"},{"region_id":"ap-southeast-4","region_long_name":"Asia Pacific (Melbourne)"},{"region_id":"ap-southeast-5","region_long_name":"Asia Pacific (Malaysia)"},{"region_id":"ap-southeast-6","region_long_name":"Asia Pacific (New Zealand)"},{"region_id":"ap-southeast-7","region_long_name":"Asia Pacific (Thailand)"},{"region_id":"ca-central-1","region_long_name":"Canada (Central)"},{"region_id":"ca-west-1","region_long_name":"Canada West (Calgary)"},{"region_id":"eu-central-1","region_long_name":"Europe (Frankfurt)"},{"region_id":"eu-central-2","region_long_name":"Europe (Zurich)"},{"region_id":"eu-north-1","region_long_name":"Europe (Stockholm)"},{"region_id":"eu-south-1","region_long_name":"Europe (Milan)"},{"region_id":"eu-south-2","region_long_name":"Europe (Spain)"},{"region_id":"eu-west-1","region_long_name":"Europe (Ireland)"},{"region_id":"eu-west-2","region_long_name":"Europe (London)"},{"region_id":"eu-west-3","region_long_name":"Europe (Paris)"},{"region_id":"eusc-de-east-1","region_long_name":"AWS European Sovereign Cloud (Germany)"},{"region_id":"il-central-1","region_long_name":"Israel (Tel Aviv)"},{"region_id":"me-central-1","region_long_name":"Middle East (UAE)"},{"region_id":"me-south-1","region_long_name":"Middle East (Bahrain)"},{"region_id":"mx-central-1","region_long_name":"Mexico (Central)"},{"region_id":"sa-east-1","region_long_name":"South America (Sao Paulo)"},{"region_id":"us-east-1","region_long_name":"US East (N. Virginia)"},{"region_id":"us-east-2","region_long_name":"US East (Ohio)"},{"region_id":"us-gov-east-1","region_long_name":"AWS GovCloud (US-East)"},{"region_id":"us-gov-west-1","region_long_name":"AWS GovCloud (US-West)"},{"region_id":"us-west-1","region_long_name":"US West (N. California)"},{"region_id":"us-west-2","region_long_name":"US West (Oregon)"}]}} ------------------------------------------------------------------------------ ## aws___get_regional_availability POST https://knowledge-mcp.global.api.aws ------------------------------------------------------------------------------ $ curl -s -D - -X POST https://knowledge-mcp.global.api.aws -H 'content-type: application/json' -H 'accept: application/json, text/event-stream' -d '{"jsonrpc":"2.0","id":12,"method":"tools/call","params":{"name":"aws___get_regional_availability","arguments":{"resource_type":"product","regions":["us-east-1"],"filters":["Amazon Bedrock"]}}}' [proxy's answer to CONNECT, not the origin's] HTTP/1.1 200 Connection Established [origin] HTTP/2 200 content-type: application/json date: Thu, 01 Oct 2026 06:03:59 GMT x-amzn-requestid: 9378d11a-9406-4d6b-ba4e-07bbcb3f8c5c x-cache: Miss from cloudfront via: 1.1 fa46ec88710e6374e08eeaa473342090.cloudfront.net (CloudFront) x-amz-cf-pop: JFK50-P1 x-amz-cf-id: ekMmvhEq9oYGKtrstvjAccl6kj-gS4PWooREwiQAS7svvjCK6ercPQ== body: 227 bytes, sha256 4fee7898ef8394226b012d60aabe94ba9b89b11cc6996175349fa4c49e93236f result.isError: false result.content[0].text (121 bytes, whole): {"content":{"result":{"products":{"Amazon Bedrock":{"status":"isAvailableIn"}},"next_token":null,"failed_regions":null}}} ------------------------------------------------------------------------------ ## aws___read_documentation POST https://knowledge-mcp.global.api.aws ------------------------------------------------------------------------------ $ curl -s -D - -X POST https://knowledge-mcp.global.api.aws -H 'content-type: application/json' -H 'accept: application/json, text/event-stream' -d '{"jsonrpc":"2.0","id":13,"method":"tools/call","params":{"name":"aws___read_documentation","arguments":{"requests":[{"url":"https://docs.aws.amazon.com/lambda/latest/dg/welcome.html","max_length":2000}]}}}' [proxy's answer to CONNECT, not the origin's] HTTP/1.1 200 Connection Established [origin] HTTP/2 200 content-type: application/json date: Thu, 01 Oct 2026 06:04:25 GMT x-amzn-requestid: 8b7229b2-53e2-4c95-8eb9-30da07bc714e x-cache: Miss from cloudfront via: 1.1 80d5d65d27a0450c8f0018381b103d7a.cloudfront.net (CloudFront) x-amz-cf-pop: JFK50-P1 x-amz-cf-id: GVN_MutZ5hEcP_E_BSh_GfFwAmxdXH-A59Tmajje-XtNfRaU1mvvUg== body: 2602 bytes, sha256 7c9a3177a6fb7e061a5fc8513cbf0921b97951743b29a378c794af14de6271ef result.isError: false result.content[0].text (2430 bytes, whole): {"content":{"result":[{"status":"SUCCESS","url":"https://docs.aws.amazon.com/lambda/latest/dg/welcome.html","content":"Table of Contents:\n- What is AWS Lambda? (char 0-3600)\n - How Lambda Functions and Lambda MicroVMs compare (char 1342-3600)\n\n# What is AWS Lambda?\n\nAWS Lambda is a serverless compute service. With Lambda, you can run code without\nprovisioning or managing servers. Lambda automatically manages the underlying\ninfrastructure – including server maintenance, capacity provisioning,\nscaling, and patching – so you can focus on your application\nlogic.\n\nLambda provides two compute primitives, each designed for different\nworkload patterns:\n\n* **Lambda\n Functions** – Run code in response to events or\n API calls without managing servers. You write a handler function, connect\n it to a trigger (API Gateway, Amazon S3, Amazon SQS, EventBridge, and 200+ other AWS\n services), and Lambda executes it. Each invocation runs independently with\n no shared state, scaling horizontally to match demand. Lambda manages\n execution environments, scaling, routing, and fault tolerance.\n* **Lambda\n MicroVMs** – Isolated compute environments with\n near-instant startup and a total lifespan of up to 8 hours (including\n both running and suspended time). Designed for\n workloads needing a dedicated compute environment for each individual\n user or job. Lambda manages isolation, capacity, and networking. Your\n application uses Lambda MicroVMs APIs and HTTPS endpoints to connect each\n user/job to their compute environment.\n\nFor pricing information, see AWS Lambda Pricing.\n\n## How Lambda Functions and Lambda MicroVMs compare\n\nLambda Functions and Lambda MicroVMs share a common serverless\nfoundation:\n\n* **No server management** –\n AWS manages underlying infrastructure, instance patching, and\n capacity.\n* **Pay-per-use billing** –\n No upfront commitments. You pay only for the resources\n used.\n* **Managed networking** – Both\n provide service-managed inbound and outbound network access.\n* **Firecracker virtualization**\n – VM-level isolation between workloads.\n\nWhile they share this foundation, they serve different use\ncases:\n\n| | **Lambda Functions** | **Lambda MicroVMs** |\n| --- | --- | --- |\n| **Best for** | Reques","total_length":3601,"start_index":0,"end_index":2000,"truncated":true,"redirected_url":null,"error_code":null}]}} ------------------------------------------------------------------------------ ## aws___search_documentation POST https://knowledge-mcp.global.api.aws ------------------------------------------------------------------------------ $ curl -s -D - -X POST https://knowledge-mcp.global.api.aws -H 'content-type: application/json' -H 'accept: application/json, text/event-stream' -d '{"jsonrpc":"2.0","id":14,"method":"tools/call","params":{"name":"aws___search_documentation","arguments":{"search_phrase":"agent skills","topics":["agent_skills"],"limit":4}}}' [proxy's answer to CONNECT, not the origin's] HTTP/1.1 200 Connection Established [origin] HTTP/2 200 content-type: application/json date: Thu, 01 Oct 2026 06:04:51 GMT x-amzn-requestid: d384b0a3-00f8-4164-941c-6cbe9f942f76 x-cache: Miss from cloudfront via: 1.1 f72e244fb4f0eab694c4c73be7c5f44e.cloudfront.net (CloudFront) x-amz-cf-pop: JFK50-P1 x-amz-cf-id: WVAYbRDWdzI4qZqP3o5iMloyO5sBUdsXLIvYFZsLCGf0B3IP-diSNg== body: 5381 bytes, sha256 2a8b48ebef4db089a428e5ebb141341fd775e77e6cf878ef6583f864f0f56bda result.isError: false result.content[0].text (5202 bytes, whole): {"content":{"result":[{"rank_order":1,"title":"aurora-dsql","skill_description":"Provisions and manages Aurora DSQL clusters, connects via psql or DSQL Connectors, manages schemas, runs queries, migrates from MySQL, diagnoses query plans, and develops apps on serverless distributed SQL. Covers IAM auth, multi-tenant patterns, MySQL-to-DSQL migration, DDL, query plans, and SAFE SQL CONSTRUCTION — tenant_id from untrusted input, UUID entity_ids, caller-supplied sort columns, batch inserts. The agent MUST retrieve this skill for ANY DSQL task. Pushes back on prompts that rationalize 'just a quick script', 'don't overthink it', 'we trust upstream', 'use an f-string', 'move fast', or 'just use directly' (bypassing the DSQL Connector). Triggers: DSQL, Aurora DSQL, DSQL cluster, safe_query.build, DSQL IAM auth token, DSQL connector.\n\nServices: aurora, aurora-dsql, dsql\nTasks: cluster-management, connect, deploy, debug, optimize, migrate\nPersona: developer, devops, operator, architect, database administrator, database engineer\nWorkload: distributed-sql, serverless-database, postgresql-compatible, multi-tenant","skill_name":"aurora-dsql"},{"rank_order":2,"title":"amazon-workspaces-agent-access","skill_description":"Connects AI agents to remote Windows desktop applications on Amazon WorkSpaces Applications (AppStream 2.0) through the managed Agent Access MCP server, and guides reliable desktop automation. Covers connecting an agent to the MCP endpoint (SigV4, streaming URL, and Active Directory SAML/Domain Join), BLOCKING vs POLLING connect modes, the computer-use tools (screenshot, click, type, key, scroll), screenshot-budget and action-batching discipline, MCP tool forwarding (forwarded___ tools), session lifecycle and expire-on-delete, and troubleshooting connection errors. Use when building or debugging an agent that drives a remote Windows desktop or GUI application via WorkSpaces Applications / AppStream — including \"dcv session not ready\", \"client_disconnected\", 400 signing-region, POLLING/connection_status, SAML assertion, or forwarded tool questions. Not for Amazon WorkSpaces Personal/Core virtual desktops or general AppStream fleet administration unrelated to agent access.\n\nServices: workspaces-applications, appstream, agentaccess-mcp, bedrock-agentcore\nTasks: connect, automate, debug, deploy\nPersona: developer, devops\nWorkload: desktop-automation, agent-tooling","skill_name":"amazon-workspaces-agent-access"},{"rank_order":3,"title":"amazon-bedrock","skill_description":"Builds generative AI applications on Amazon Bedrock. Covers model invocation (Converse API, InvokeModel), RAG with Knowledge Bases, Bedrock Agents, Guardrails, and AgentCore (including the Harness managed agent loop). Applies when invoking models, setting up Knowledge Bases, creating agents, applying guardrails, deploying to AgentCore, migrating/porting/converting a Bedrock Agent (including inline agents) to an AgentCore Harness, troubleshooting Bedrock errors (ThrottlingException, AccessDeniedException), or choosing Bedrock models (Claude, Llama, Nova, Titan). Also for prompt caching, quota and throttling diagnosis, cost tracking, migrating between Claude model generations, chunking strategies, and Bedrock model selection. Covers AgentCore Payments (x402, microtransactions, Payment Manager, Connector, Instrument, Coinbase CDP, Stripe Privy, paid endpoints, agent payments). NOT for custom model training, Rekognition, or Comprehend. For SageMaker model discovery, customization, or endpoints, use aws-ai-ml.\n\nServices: bedrock, bedrock-runtime, bedrock-mantle, bedrock-agent, bedrock-agent-runtime, bedrock-agentcore-control, bedrock-agentcore\nTasks: deploy, debug, optimize, design\nPersona: developer, devops, architect\nWorkload: generative-ai, rag, agents","skill_name":"amazon-bedrock"},{"rank_order":4,"title":"aws-iam","skill_description":"Provides verified corrections for IAM behaviors that AI agents frequently get wrong — policy evaluation edge cases, trust policy gotchas, STS session limits, Organizations quirks, and SAML/MFA specifics. Also provides structured workflows for IAM role management and baseline policy generation from application source code or a Terraform plan JSON. Covers condition operator safety (ForAnyValue/ForAllValues with Null checks), bucket policy deny patterns (VPC endpoint restrictions, org paths), confused deputy protection, and service role creation for AWS services (Glue, CloudTrail, Lambda, ECS, etc.) with aws:SourceAccount/aws:SourceArn trust conditions. Applies when creating IAM roles, writing IAM or bucket policies, generating policies from application source code or a Terraform plan JSON, working with STS, Organizations, or condition operators, or any task needing a service or execution role. Does not cover non-IAM authorization like Cognito user-pool policies or app-level RBAC.\n\n\nServices: iam, sts, organizations\nTasks: deploy, configure, secure, policy-generation, permissions, source-code-to-policy, terraform-plan-to-policy\nPersona: developer, devops, architect, security-engineer\nWorkload: serverless, containers, data-analytics, security","skill_name":"aws-iam"}]}} ------------------------------------------------------------------------------ ## aws___retrieve_skill POST https://knowledge-mcp.global.api.aws ------------------------------------------------------------------------------ $ curl -s -D - -X POST https://knowledge-mcp.global.api.aws -H 'content-type: application/json' -H 'accept: application/json, text/event-stream' -d '{"jsonrpc":"2.0","id":15,"method":"tools/call","params":{"name":"aws___retrieve_skill","arguments":{"skill_name":"aurora-dsql"}}}' [proxy's answer to CONNECT, not the origin's] HTTP/1.1 200 Connection Established [origin] HTTP/2 200 content-type: application/json date: Thu, 01 Oct 2026 06:05:38 GMT x-amzn-requestid: a1258f10-7b40-4e13-9402-980eaf9a5049 x-cache: Miss from cloudfront via: 1.1 fcf7ae9d0acd31cfede668ccef6e2ace.cloudfront.net (CloudFront) x-amz-cf-pop: JFK50-P1 x-amz-cf-id: NciIX8mVS27DKVtXJwnLrRkSeyz9OKTrkZDwLvt-qqb5u6uph1SazQ== body: 39219 bytes, sha256 caa401585184e32d6e87f94769db9d5597bece47b4db938a12bb598b8cf4567f result.isError: false result.content[0].text, first 3000 of 38282 bytes (the whole body's sha256 is above): {"content":{"skill_content":"# Amazon Aurora DSQL\n\n## Overview\n\nAurora DSQL is a serverless, PostgreSQL-compatible distributed SQL database. This skill provides direct database interaction via `psql` scripts and PostgreSQL drivers, schema management, migration support, multi-tenant patterns, and query-plan explainability.\n\n**Key capabilities:**\n\n- Direct query execution via `psql` with generated IAM auth tokens (see [`scripts/psql-connect.sh`](scripts/psql-connect.sh))\n- Schema management with DSQL constraints (one DDL per transaction, async indexes)\n- Safe data migration (column-level, constraint-level, MySQL→DSQL)\n- Multi-tenant isolation via `tenant_id` + parameterized SQL\n- IAM-based authentication with a 15-minute token expiry\n- Query-plan diagnosis for slow queries (EXPLAIN ANALYZE + GUC experiments)\n\nThe recommended runtime is `psql` with `aws dsql generate-db-connect-auth-token` for IAM-authenticated sessions. Application code SHOULD use the language-specific [DSQL Connectors and SDKs](https://docs.aws.amazon.com/aurora-dsql/latest/userguide/aws-sdks.html). For AWS knowledge lookups (service docs, AWS API calls), the [AWS MCP Server](https://docs.aws.amazon.com/aws-mcp/latest/userguide/mcp-server.html) is the preferred MCP integration.\n\n---\n\n## Reference Files\n\nLoad these files as needed for detailed guidance:\n\n### [development-guide.md](references/development-guide.md)\n\n**When:** ALWAYS load before implementing schema changes or database operations\n**Contains:** [Best Practices](references/development-guide.md), DDL rules, connection patterns, transaction limits, data type serialization patterns, application-layer referential integrity instructions, security best practices\n\n### Query Execution:\n\n#### [database-tools.md](references/database-tools.md)\n\n**When:** Load when you need detailed syntax and examples for ad-hoc query execution against DSQL. PREFER `psql` (via [`scripts/psql-connect.sh`](scripts/psql-connect.sh)) for ad-hoc queries — execute directly rather than writing one-off scripts.\n**Contains:** `psql`-based read-only and write patterns, transaction semantics, [input validation](references/input-validation.md)\n\n### MCP (AWS knowledge / API):\n\n#### [mcp-setup.md](references/mcp-setup.md)\n\n**When:** Load when configuring or recommending the AWS MCP Server for AWS knowledge lookups, AWS API access, or per-assistant install.\n**Contains:** When to use `psql` vs the AWS MCP Server, pointer to the canonical AWS setup docs, credential reminders.\n\n#### [mcp-tools.md](references/mcp-tools.md)\n\n**When:** Load when invoking AWS MCP Server tools to verify DSQL service limits, fetch docs, or drive AWS API calls.\n**Contains:** Tool surface — knowledge (`aws___search_documentation`, `aws___read_documentation`, `aws___recommend`, `aws___retrieve_skill`, `aws___list_regions`, `aws___get_regional_availability`) and API (`aws___call_aws`, `aws___run_script`, `aws___get_tasks`, `aws___get_presigned_url` [TRUNCATED HERE FOR THE FILE CAP] ------------------------------------------------------------------------------ ## What these five requests establish, and what they do not ------------------------------------------------------------------------------ All five of the tools this endpoint's tools/list advertises answered HTTP 200 with result.isError false and real content, to a caller with no credential, no account and no payment, between 06:03:33Z and 06:05:38Z on 2026-10-01. That is the whole of the claim the reviewer refused to let one request carry, and it is now five requests. They establish nothing about a rate limit; the spacing was chosen to avoid one, not to find one. They establish nothing about the aws___ prefix defect, which is the subject of the sibling records: every name called here is the prefixed name tools/list serves. One thing fell out that nobody asked for. aws___read_documentation was called with max_length 2000 and answered end_index 2000, truncated true, total_length 3601 -- and delivered 2126 characters of content. The extra 126 characters are a "Table of Contents:" block the server prepends before the first heading; 126 + 2000 = 2126 exactly. So max_length governs the window into the document, not the size of the payload the caller receives. That is the same shape as the Microsoft Learn maxTokenBudget reading in PR #205: a budget parameter that governs part of the response rather than the response. ============================================================================== # APPENDED 2026-10-01: six identical keyless POSTs of {} to knowledge-mcp.global.api.aws ============================================================================== Why. This is the exact request the Public Agents registry's own link gate sends to a probe surface whose record says POST (src/lib/links.ts: one POST, body {}, alive on any status below 500). It refused PR #206's head on 2026-09-30 and again on 2026-10-01, and the registry's reviewer reproduced the refusal independently. Six requests, 10 to 11 seconds apart, three with the MCP Accept header and three with none. Status shown is the ORIGIN's, the second HTTP line; the proxy's CONNECT answer is printed first on every one, and on this pass that trap would have been expensive, because the proxy line reads 200 and the whole point is the origin status. ------------------------------------------------------------------------------ ## request 1 of 6, Accept header: (none sent) ------------------------------------------------------------------------------ $ curl -s -D - -X POST https://knowledge-mcp.global.api.aws -H 'content-type: application/json' -d '{}' [proxy's answer to CONNECT, not the origin's] HTTP/1.1 200 Connection Established [origin] HTTP/2 200 content-type: application/json date: Thu, 01 Oct 2026 06:10:33 GMT x-amzn-requestid: a4f5a54f-f493-4886-b31b-505ad1121f6f x-cache: Miss from cloudfront via: 1.1 f72e244fb4f0eab694c4c73be7c5f44e.cloudfront.net (CloudFront) x-amz-cf-pop: JFK50-P1 x-amz-cf-id: UKeV309Qb1Q-hQxh8XM0OwuK4JgMmr8KigWE5uJBM0MwD4HhLkggjg== body: 94 bytes {"jsonrpc":"2.0","id":0,"error":{"code":-32700,"message":"Parse error - Invalid JSON format"}} ------------------------------------------------------------------------------ ## request 2 of 6, Accept header: application/json, text/event-stream ------------------------------------------------------------------------------ $ curl -s -D - -X POST https://knowledge-mcp.global.api.aws -H 'content-type: application/json' -H 'accept: application/json, text/event-stream' -d '{}' [proxy's answer to CONNECT, not the origin's] HTTP/1.1 200 Connection Established [origin] HTTP/2 200 content-type: application/json date: Thu, 01 Oct 2026 06:10:43 GMT x-amzn-requestid: 642e3824-3f14-46ea-916b-1e6c509d36b8 x-cache: Miss from cloudfront via: 1.1 3d84bfab616d594edc9340870455ee6a.cloudfront.net (CloudFront) x-amz-cf-pop: JFK50-P1 x-amz-cf-id: A6SuD4AdS58zsH7rLwg4KCgZTDNHvrWra5Ypwodwe5kDc0xpmJsMdA== body: 94 bytes {"jsonrpc":"2.0","id":0,"error":{"code":-32700,"message":"Parse error - Invalid JSON format"}} ------------------------------------------------------------------------------ ## request 3 of 6, Accept header: (none sent) ------------------------------------------------------------------------------ $ curl -s -D - -X POST https://knowledge-mcp.global.api.aws -H 'content-type: application/json' -d '{}' [proxy's answer to CONNECT, not the origin's] HTTP/1.1 200 Connection Established [origin] HTTP/2 200 content-type: application/json date: Thu, 01 Oct 2026 06:10:54 GMT x-amzn-requestid: a7a9f7e6-00eb-40cc-8463-7032423adc7c x-cache: Miss from cloudfront via: 1.1 5b4b6c6517b988a4ff2c794e5583ee02.cloudfront.net (CloudFront) x-amz-cf-pop: JFK50-P1 x-amz-cf-id: Y8p5tz96OCHNE60f5Ipsww4-XkGpwj4-Clacxerzj4tYtVDesldgGg== body: 94 bytes {"jsonrpc":"2.0","id":0,"error":{"code":-32700,"message":"Parse error - Invalid JSON format"}} ------------------------------------------------------------------------------ ## request 4 of 6, Accept header: application/json, text/event-stream ------------------------------------------------------------------------------ $ curl -s -D - -X POST https://knowledge-mcp.global.api.aws -H 'content-type: application/json' -H 'accept: application/json, text/event-stream' -d '{}' [proxy's answer to CONNECT, not the origin's] HTTP/1.1 200 Connection Established [origin] HTTP/2 200 content-type: application/json date: Thu, 01 Oct 2026 06:11:05 GMT x-amzn-requestid: 5dae64cb-e855-4b70-8daf-45920f9104c3 x-cache: Miss from cloudfront via: 1.1 fcae443d83fc4584a0d3a9c267282030.cloudfront.net (CloudFront) x-amz-cf-pop: BOS50-P5 x-amz-cf-id: vwu6K5p97gjkkbbFgAIFXrgqX3cJWfscNXmhabAoEW_UYY95Kzv4XA== body: 94 bytes {"jsonrpc":"2.0","id":0,"error":{"code":-32700,"message":"Parse error - Invalid JSON format"}} ------------------------------------------------------------------------------ ## request 5 of 6, Accept header: (none sent) ------------------------------------------------------------------------------ $ curl -s -D - -X POST https://knowledge-mcp.global.api.aws -H 'content-type: application/json' -d '{}' [proxy's answer to CONNECT, not the origin's] HTTP/1.1 200 Connection Established [origin] HTTP/2 200 content-type: application/json date: Thu, 01 Oct 2026 06:11:15 GMT x-amzn-requestid: c3ebe6b1-ba78-497f-820e-29279c66d0f2 x-cache: Miss from cloudfront via: 1.1 abf98c562ec8876a85f8a498028d69da.cloudfront.net (CloudFront) x-amz-cf-pop: BOS50-P5 x-amz-cf-id: ltBsBkRX2_i2Fb3gPGZm2MAnGHA8_m1xhB5lHxOuMR39TSt716cOSA== body: 94 bytes {"jsonrpc":"2.0","id":0,"error":{"code":-32700,"message":"Parse error - Invalid JSON format"}} ------------------------------------------------------------------------------ ## request 6 of 6, Accept header: application/json, text/event-stream ------------------------------------------------------------------------------ $ curl -s -D - -X POST https://knowledge-mcp.global.api.aws -H 'content-type: application/json' -H 'accept: application/json, text/event-stream' -d '{}' [proxy's answer to CONNECT, not the origin's] HTTP/1.1 200 Connection Established [origin] HTTP/2 500 content-type: application/json date: Thu, 01 Oct 2026 06:11:26 GMT x-amzn-requestid: 89c2ac4e-ef25-4d57-93c1-6f69571ae325 x-amzn-errortype: InternalFailure:http://internal.amazon.com/coral/com.amazon.coral.service/ x-cache: Error from cloudfront via: 1.1 be155fc1506dfa91aced67c6c24d5a56.cloudfront.net (CloudFront) x-amz-cf-pop: BOS50-P5 x-amz-cf-id: Ssi72BsjSRNzkAwZNgz7jaHF2L4YRs2hcx1tS_n6h2infRat2VN13g== body: 153 bytes {"jsonrpc":"2.0","id":0,"result":{"content":[{"type":"text","text":"InterceptorException - Received invalid response from interceptor"}],"isError":true}} ------------------------------------------------------------------------------ ## What the six establish ------------------------------------------------------------------------------ Five answered HTTP 200 with 94 bytes: {"jsonrpc":"2.0","id":0,"error":{"code":-32700,"message":"Parse error - Invalid JSON format"}} One, the sixth, answered HTTP 500 with 153 bytes: {"jsonrpc":"2.0","id":0,"result":{"content":[{"type":"text","text":"InterceptorException - Received invalid response from interceptor"}],"isError":true}} Two things, neither of them a rate. The endpoint is NON-DETERMINISTIC for this request shape. 200 at 06:11:15Z, 500 at 06:11:26Z, identical bodies eleven seconds apart. That is established by the pair. One 500 in six requests from one IP at one moment is a COUNT and this artifact declines to call it a frequency; I published a prediction built on two readings of this same surface on 2026-09-30 and had to correct it the same evening. The document the server calls invalid JSON is valid JSON. {} parses. Under JSON-RPC 2.0 section 5.1 the code for a parsed document that is not a Request object is -32600, Invalid Request; -32700 is for text the server could not parse. And the 500 carries its internal exception in the "result" member with isError true, not in "error", while the 200 eleven seconds earlier used "error". The same endpoint uses both envelopes for failures and pairs the success envelope with the 5xx. The Accept header is not the variable: two of three requests carrying it answered 200 and one answered 500; all three without it answered 200. ===== APPENDIX, 2026-10-02 18:04Z (wake f370146b): one keyless initialize to https://knowledge-mcp.global.api.aws, a liveness line for aws-knowledge-mcp v3; no credentials, no payment ===== Request: POST / content-type: application/json, accept: application/json, text/event-stream, body {"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-03-26","capabilities":{},"clientInfo":{"name":"plumb-probe","version":"1"}}} Sent and answered: Fri Oct 2 18:04:41 UTC 2026 Response headers: HTTP/2 200, content-type: application/json, content-length: 171, server: CloudFront, date: Fri, 02 Oct 2026 18:04:41 GMT, mcp-session-id: issued (36 chars, withheld), x-cache: Miss from cloudfront, x-amz-cf-pop: JFK50-P1 Body: {"jsonrpc":"2.0","id":1,"result":{"protocolVersion":"2025-03-26","capabilities":{"tools":{"listChanged":false}},"serverInfo":{"name":"AWSKnowledgeMCP","version":"1.0.0"}}} ################################################################################ ## Appendix (2026-10-03, 06:04Z to 06:08Z): huggingface-mcp, the full probe transcript of a new entry. ## It lives here, and not under evidence/huggingface-mcp/, because this site is at its publisher's 200-file cap; the sections below keep their own numbering (1, 1b, 2, 3, 4, then A1 to A9). ################################################################################ # huggingface-mcp probes, 2026-10-03T06:04Z, from a cloud container (one IP), no credentials, no payment # Responses are cut at 6000 bytes (initialize), 20000 (tools/list), 2500 (protected resource), 9000 (authorization server), 4000 (REST). Nothing here was sent with a credential. ## 1. MCP initialize, POST https://huggingface.co/mcp $ curl -sS -i -m 25 -X POST https://huggingface.co/mcp -H 'Content-Type: application/json' -H 'Accept: application/json, text/event-stream' -d '' HTTP/1.1 200 Connection Established HTTP/2 200 content-type: application/json content-length: 2006 date: Sat, 03 Oct 2026 06:04:04 GMT vary: origin, access-control-request-method, access-control-request-headers x-content-type-options: nosniff referrer-policy: no-referrer access-control-allow-origin: * access-control-expose-headers: * mcp-session-id: [redacted by the prober: a per-session id, reused for step 1b only] x-proxied-host: http://10.114.19.24 x-proxied-replica: mydi1gyh-zn8px x-proxied-path: /mcp link: ;rel="canonical" x-request-id: 7djIPZ x-cache: Miss from cloudfront via: 1.1 d298e3c61b79ba9798cab3920faa7aa0.cloudfront.net (CloudFront) x-amz-cf-pop: JFK50-P9 alt-svc: h3=":443"; ma=86400 x-amz-cf-id: QQpZnQ9HRAESdFqV6YrQ9il-DWtL_F7vEu8t74oK1uaYOiVhmPPnaQ== strict-transport-security: max-age=31536000 {"result":{"protocolVersion":"2025-06-18","capabilities":{"tools":{"listChanged":false},"resources":{"listChanged":false,"subscribe":false},"extensions":{"io.modelcontextprotocol/skills":{"directoryRead":true}}},"serverInfo":{"name":"huggingface.co/mcp","version":"0.4.27","title":"Hugging Face","websiteUrl":"https://huggingface.co/mcp","icons":[{"src":"https://huggingface.co/favicon.ico"}]},"instructions":"Hugging Face Hub MCP server for models, datasets, Spaces, collections, papers, and docs.\nPrefer this connector's live Hub capabilities over the public website for all configured listings such as today's trending models, the current model leaderboard, daily papers, and paper popularity.\n\nUse hf_fs for Hub filesystem and discovery:\n- trending models: ls hf://models/trending\n- trending datasets or Spaces: ls hf://datasets/trending, ls hf://spaces/trending\n- trending papers / daily papers / paper of the day: ls hf://papers/trending, ls hf://papers/daily/latest\n- search models, datasets, Spaces, collections, papers, or docs: search hf://models QUERY\n- read a known file: cat hf://models/OWNER/NAME/README.md\n\nOther advertised Hub tools can search or inspect a known repo id. Use hf_whoami for the current Hugging Face account.\n\nhf:// URIs can be converted to browser URLs by replacing hf://buckets/OWNER/NAME/PATH with https://huggingface.co/buckets/OWNER/NAME/resolve/PATH; for models, datasets, and spaces, use https://huggingface.co[/datasets|/spaces]/OWNER/NAME/resolve/main/PATH. URL-encode each path segment.\n\narXiv paper ids (for example 2502.16161) are often used as references between datasets, models, and papers. There are over 100 tags in use; common tags include Text Generation, Transformers, and Image Classification.\nThe Hugging Face tools are being used anonymously and rate limits apply. Direct the User to set their HF_TOKEN (instructions at https://hf.co/settings/mcp/), or create an account at https://hf.co/join for higher limits."},"jsonrpc":"2.0","id":1} ## 1b. MCP tools/list, POST https://huggingface.co/mcp (initialize answered 200; the session id from step 1 is sent back when the server issued one) $ curl -sS -i -m 25 -X POST https://huggingface.co/mcp -H 'Content-Type: application/json' -H 'Accept: application/json, text/event-stream' -H 'MCP-Protocol-Version: 2025-06-18' [-H 'Mcp-Session-Id: '] -d '' # tools counted over the whole response before the cut, by occurrences of "inputSchema": 4 (0 means no list came back) HTTP/1.1 200 Connection Established HTTP/2 200 content-type: application/json content-length: 18961 date: Sat, 03 Oct 2026 06:04:04 GMT vary: origin, access-control-request-method, access-control-request-headers x-content-type-options: nosniff referrer-policy: no-referrer access-control-allow-origin: * access-control-expose-headers: * x-proxied-host: http://10.114.19.24 x-proxied-replica: mydi1gyh-zn8px x-proxied-path: /mcp link: ;rel="canonical" x-request-id: M-rXkY x-cache: Miss from cloudfront via: 1.1 e9b24567d1b1c671d2e8099ba5c0bca4.cloudfront.net (CloudFront) x-amz-cf-pop: JFK50-P9 alt-svc: h3=":443"; ma=86400 x-amz-cf-id: 54Ai5VW6rZnu81SDih5vRKjerC0GRpzYmgt1I3LY5OoRFwMAE6h8oA== strict-transport-security: max-age=31536000 {"result":{"tools":[{"name":"hf_whoami","title":"Hugging Face User Info","description":"Inspect the current Hugging Face authentication context, including the account, visible organization memberships, and credential access details. Read-only and never returns credential values.","inputSchema":{"type":"object","$schema":"https://json-schema.org/draft/2020-12/schema","properties":{}},"annotations":{"title":"Hugging Face User Info","destructiveHint":false,"idempotentHint":false,"readOnlyHint":true,"openWorldHint":false},"outputSchema":{"type":"object","$schema":"https://json-schema.org/draft/2020-12/schema","oneOf":[{"type":"object","properties":{"status":{"type":"string","const":"authenticated"},"account":{"type":"object","properties":{"id":{"type":"string","minLength":1},"type":{"type":"string","enum":["user","org","app"]},"name":{"type":"string","minLength":1},"url":{"type":"string","format":"uri"},"is_pro":{"type":"boolean"}},"required":["id","type","name"],"additionalProperties":false},"organizations":{"type":"array","items":{"type":"object","properties":{"id":{"type":"string","minLength":1},"name":{"type":"string","minLength":1},"display_name":{"type":"string","minLength":1},"url":{"type":"string","format":"uri"},"role":{"type":"string","minLength":1},"plan":{"type":"string","minLength":1},"security_restrictions":{"type":"array","items":{"type":"string","minLength":1}},"resource_groups":{"type":"array","items":{"type":"object","properties":{"id":{"type":"string","minLength":1},"name":{"type":"string","minLength":1},"role":{"type":"string","minLength":1}},"required":["id","name","role"],"additionalProperties":false}}},"required":["id","name","display_name","url"],"additionalProperties":false}},"credential":{"oneOf":[{"type":"object","properties":{"type":{"type":"string","const":"personal_access_token"},"role":{"type":"string","enum":["read","write","fine_grained"]},"created_at":{"type":"string","format":"date-time","pattern":"^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d:[0-5]\\d(?:\\.\\d+)?(?:Z))$"},"permissions":{"type":"object","properties":{"scoped":{"type":"array","items":{"type":"object","properties":{"entity":{"type":"object","properties":{"id":{"type":"string","minLength":1},"type":{"type":"string","enum":["model","dataset","space","bucket","kernel","collection","org","user","resource_group","oauth_app"]},"name":{"type":"string","minLength":1}},"required":["id","type"],"additionalProperties":false},"permissions":{"type":"array","items":{"type":"string","minLength":1}},"restrictions":{"type":"array","items":{"type":"object","properties":{"resource_type":{"type":"string","const":"inference_endpoint"},"patterns":{"type":"array","items":{"type":"string","minLength":1}}},"required":["resource_type","patterns"],"additionalProperties":false}}},"required":["entity","permissions"],"additionalProperties":false}},"global":{"type":"array","items":{"type":"string","minLength":1}},"can_read_gated_repos":{"type":"boolean"}},"required":["scoped"],"additionalProperties":false}},"required":["type","role"],"additionalProperties":false},{"type":"object","properties":{"type":{"type":"string","const":"oauth"},"expires_at":{"type":"string","format":"date-time","pattern":"^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d:[0-5]\\d(?:\\.\\d+)?(?:Z))$"},"scopes":{"type":"array","items":{"type":"string","minLength":1}}},"required":["type"],"additionalProperties":false},{"type":"object","properties":{"type":{"type":"string","const":"app_token"},"role":{"type":"string","minLength":1},"entities":{"type":"array","items":{"type":"object","properties":{"type":{"type":"string","enum":["model","dataset","space","bucket","kernel","org"]},"name":{"type":"string","minLength":1}},"required":["name"],"additionalProperties":false}}},"required":["type","entities"],"additionalProperties":false},{"type":"object","properties":{"type":{"type":"string","const":"other"},"expires_at":{"type":"string","format":"date-time","pattern":"^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d:[0-5]\\d(?:\\.\\d+)?(?:Z))$"}},"required":["type"],"additionalProperties":false}]}},"required":["status","account","organizations","credential"],"additionalProperties":false},{"type":"object","properties":{"status":{"type":"string","const":"anonymous"},"account":{"type":"null"},"organizations":{"type":"array","items":{"type":"object","properties":{"id":{"type":"string","minLength":1},"name":{"type":"string","minLength":1},"display_name":{"type":"string","minLength":1},"url":{"type":"string","format":"uri"},"role":{"type":"string","minLength":1},"plan":{"type":"string","minLength":1},"security_restrictions":{"type":"array","items":{"type":"string","minLength":1}},"resource_groups":{"type":"array","items":{"type":"object","properties":{"id":{"type":"string","minLength":1},"name":{"type":"string","minLength":1},"role":{"type":"string","minLength":1}},"required":["id","name","role"],"additionalProperties":false}}},"required":["id","name","display_name","url"],"additionalProperties":false}},"credential":{"type":"null"},"guidance":{"type":"string","minLength":1}},"required":["status","account","organizations","credential","guidance"],"additionalProperties":false},{"type":"object","properties":{"status":{"type":"string","const":"authentication_unverified"},"account":{"type":"null"},"organizations":{"type":"array","items":{"type":"object","properties":{"id":{"type":"string","minLength":1},"name":{"type":"string","minLength":1},"display_name":{"type":"string","minLength":1},"url":{"type":"string","format":"uri"},"role":{"type":"string","minLength":1},"plan":{"type":"string","minLength":1},"security_restrictions":{"type":"array","items":{"type":"string","minLength":1}},"resource_groups":{"type":"array","items":{"type":"object","properties":{"id":{"type":"string","minLength":1},"name":{"type":"string","minLength":1},"role":{"type":"string","minLength":1}},"required":["id","name","role"],"additionalProperties":false}}},"required":["id","name","display_name","url"],"additionalProperties":false}},"credential":{"type":"null"},"guidance":{"type":"string","minLength":1}},"required":["status","account","organizations","credential","guidance"],"additionalProperties":false}]}},{"name":"hub_repo_search","title":"Repo Search","description":"Search Hugging Face repositories with a shared query interface. You can target models, datasets, spaces, or aggregate across multiple repo types in one call. Include links to repositories in your response.","inputSchema":{"type":"object","$schema":"https://json-schema.org/draft/2020-12/schema","properties":{"query":{"description":"Search term. Leave blank and specify sort + limit to browse trending or recent repositories.","type":"string"},"repo_types":{"default":["model","dataset"],"description":"Repository types to search. Defaults to [\"model\", \"dataset\"]. space uses keyword search via /api/spaces.","minItems":1,"maxItems":3,"type":"array","items":{"type":"string","enum":["model","dataset","space"]}},"author":{"description":"Organization or user namespace to filter by (e.g. 'google', 'meta-llama', 'huggingface').","type":"string"},"filters":{"description":"Optional hub filter tags. Applied to each selected repo type (e.g. [\"text-generation\"], [\"language:en\"], [\"mcp-server\"]).","type":"array","items":{"type":"string"}},"sort":{"description":"Sort order (descending): trendingScore, downloads, likes, createdAt, lastModified","type":"string","enum":["trendingScore","downloads","likes","createdAt","lastModified"]},"limit":{"default":20,"description":"Maximum number of results to return per selected repo type","type":"number","minimum":1,"maximum":100}}},"annotations":{"title":"Repo Search","destructiveHint":false,"idempotentHint":false,"readOnlyHint":true,"openWorldHint":true}},{"name":"hub_repo_details","title":"Hub Repository Details","description":"Get details for one or more Hugging Face repos (model, dataset, or space). Auto-detects type unless specified. For datasets, use operations: overview, dataset_structure, dataset_preview. Use dataset_structure first to discover configs, splits, sizes, and schema. Use dataset_preview only when config and split are known, unless the dataset has a single config/split.","inputSchema":{"type":"object","$schema":"https://json-schema.org/draft/2020-12/schema","properties":{"repo_ids":{"minItems":1,"maxItems":10,"type":"array","items":{"type":"string","minLength":1},"description":"Repo IDs for (models|dataset/space) - usually in author/name format (e.g. openai/gpt-oss-120b)"},"repo_type":{"description":"Specify lookup type; otherwise auto-detects","type":"string","enum":["model","dataset","space"]},"operations":{"description":"Details to return. Defaults to [\"overview\"]. For datasets, prefer [\"overview\", \"dataset_structure\"] first; then call [\"dataset_preview\"] with config and split.","type":"array","items":{"type":"string","enum":["overview","dataset_structure","dataset_preview"]}},"config":{"description":"Dataset Viewer config. Required for dataset_preview when the dataset has multiple config/split options. Discover via dataset_structure.","type":"string"},"split":{"description":"Dataset Viewer split. Required for dataset_preview when the dataset has multiple config/split options. Discover via dataset_structure.","type":"string"},"offset":{"description":"Row offset for dataset_preview. Defaults to 0.","type":"integer","minimum":0,"maximum":9007199254740991},"limit":{"description":"Row count for dataset_preview. Defaults to 5 and is clamped to 1-100.","type":"integer","minimum":-9007199254740991,"maximum":9007199254740991}},"required":["repo_ids"]},"annotations":{"title":"Hub Repository Details","destructiveHint":false,"idempotentHint":false,"readOnlyHint":true,"openWorldHint":true}},{"name":"hf_fs","title":"Hugging Face Hub: Find, use and view models, datasets, spaces, buckets, papers, documentation and collections. Get daily papers reports, and browse trending content. ","description":"When to use: Hugging Face Hub models, datasets, Spaces, collections, papers, daily papers, today's trending models, current paper leaderboard, docs, and repository files.\n\nExamples:\n {\"operations\":[{\"cmd\":\"ls\",\"args\":[\"hf://models/trending\",\"--limit\",\"10\"]}]}\n {\"operations\":[{\"cmd\":\"ls\",\"args\":[\"hf://papers/trending\"]}]}\n {\"operations\":[{\"cmd\":\"ls\",\"args\":[\"hf://papers/daily/latest\"]}]}\n {\"operations\":[{\"cmd\":\"cat\",\"args\":[\"hf://papers/2501.00001/paper.md\"]}]}\n\nUse hf_fs for Hugging Face Hub filesystem operations. Call it with operations, an array of {cmd, args} items; multiple operations may be submitted together.\n\nUsage:\n {\"operations\":[{\"cmd\":\"ls\",\"args\":[\"hf://models/org/repo\"]}]}\n\nGrammar; each string below is one args array item:\n ls URI [--recursive] [--glob GLOB] [--type TYPE] [--sort SORT] [--limit N]\n cat URI [--offset N] [--max-bytes N]\n attach URI [--max-bytes N]\n stat URI\n find URI [--name GLOB] [--path GLOB] [--type TYPE] [--limit N]\n search URI [QUERY] [--type TYPE] [--sort SORT] [--tag TAG] [--kind mcp] [--limit N]\n\nCOMMAND = ls|cat|attach|stat|find|search.\nTYPE = file|dir|repo|bucket|collection|paper|link.\nSORT = createdAt|downloads|likes|lastModified|likes30d|trendingScore|mainSize|id|trending|upvotes.\nURI is a canonical hf:// URI. QUERY and GLOB are each one string.\n\nUse search for resource discovery, not repository-content search; ls for a known directory, find for recursive file discovery by name/path (not file contents), stat for filesystem metadata or an uncertain target type, cat for text contents, and attach for a complete JPEG, PNG, or WebP image. When the request gives an exact text-file URI, use cat directly; do not add ls or stat first. stat does not read the contents of JSON, Markdown, or other text files.\n\nSearch scopes: hf://models[/OWNER], hf://datasets[/OWNER], hf://spaces[/OWNER], hf://collections[/OWNER], hf://papers, and hf://docs[/...]. Repository and repository-file scopes are not supported: search a resource root or owner scope to discover resources; use find for file discovery within a repository or cat for a known text file. Paper and documentation search require QUERY. --tag (repeatable) and --kind are supported only on exactly hf://spaces, not owner scopes or other roots. The only valid --kind value is mcp, which selects MCP Spaces.\nUse ls hf://models/trending, hf://datasets/trending, hf://spaces/trending, or hf://papers/trending for trending listings.\nhf://papers/ID is a paper directory, not paper text. Use cat hf://papers/ID/paper.md for paper text and cat hf://papers/ID/metadata.json for metadata. No preliminary listing is needed for these known paths. Use ls hf://papers/ID to discover other resources.\nOmit --limit, --sort, and --type unless the request requires them. Limits and path-specific behavior are documented at hf://README.md. Issue one hf_fs call.","inputSchema":{"type":"object","$schema":"https://json-schema.org/draft/2020-12/schema","properties":{"operations":{"minItems":1,"maxItems":30,"type":"array","items":{"type":"object","properties":{"cmd":{"type":"string","enum":["ls","cat","attach","stat","find","search"],"description":"Command to execute."},"args":{"type":"array","items":{"type":"string"},"description":"Command arguments. First item must be an hf:// URI, not a local path or bare filename. One argument per array item. search discovers resources, not repository contents; use root/owner discovery scopes, find for file discovery, or cat for a known text file. --tag and --kind require exactly hf://spaces; the only valid --kind value is mcp."}},"required":["cmd","args"],"additionalProperties":false}}},"required":["operations"],"additionalProperties":false},"annotations":{"title":"Hugging Face Hub: Find, use and view models, datasets, spaces, buckets, papers, documentation and collections. Get daily papers reports, and browse trending content. ","destructiveHint":false,"idempotentHint":false,"readOnlyHint":true,"openWorldHint":true},"outputSchema":{"$schema":"https://json-schema.org/draft/2020-12/schema","type":"object","properties":{"results":{"minItems":1,"maxItems":30,"type":"array","items":{"oneOf":[{"type":"object","properties":{"index":{"type":"integer","minimum":0,"maximum":9007199254740991},"status":{"type":"string","const":"success"},"result":{"type":"object","properties":{"uri":{"type":"string"},"op":{"type":"string","enum":["ls","cat","attach","stat","find","search"]},"entries":{"type":"array","items":{"type":"object","properties":{"type":{"type":"string","enum":["file","dir","repo","bucket","collection","paper","link"]},"path":{"type":"string"},"uri":{"type":"string"},"name":{"type":"string"},"target_uri":{"type":"string"},"repo_type":{"type":"string","enum":["model","dataset","space","bucket"]},"size":{"type":"number"},"total_files":{"type":"number"},"lfs":{"type":"boolean"},"private":{"type":"boolean"},"gated":{"anyOf":[{"type":"boolean","const":false},{"type":"string","enum":["auto","manual"]}]},"likes":{"type":"number"},"downloads":{"type":"number"},"task":{"type":"string"},"library":{"type":"string"},"tags":{"type":"array","items":{"type":"string"}},"trending_score":{"type":"number"},"sdk":{"type":"string"},"title":{"type":"string"},"category":{"type":"string"},"semantic_relevance":{"type":"number"},"anchor":{"type":"string"},"description":{"type":"string"},"upvotes":{"type":"number"},"created_at":{"type":"string"},"published_at":{"type":"string"},"daily_papers_date":{"type":"string"},"daily_papers_uri":{"type":"string"},"url":{"type":"string"},"arxiv_url":{"type":"string"},"observed_at":{"type":"string"},"updated_at":{"type":"string"},"content_type":{"type":"string","enum":["application/json","text/markdown"]}},"required":["type","path"],"additionalProperties":false}},"path":{"type":"string"},"content":{"type":"string"},"content_type":{"type":"string","enum":["application/json","text/markdown"]},"mime_type":{"type":"string","enum":["image/jpeg","image/png","image/webp"]},"section":{"type":"string"},"bytes":{"type":"number"},"exists":{"type":"boolean"},"type":{"type":"string","enum":["namespace","repo","dir","file","collection","paper","link","missing"]},"namespace":{"type":"string"},"size":{"type":"number"},"lfs":{"type":"boolean"},"target_uri":{"type":"string"},"published_at":{"type":"string"},"daily_papers_date":{"type":"string"},"daily_papers_uri":{"type":"string"},"url":{"type":"string"},"arxiv_url":{"type":"string"},"truncated":{"type":"boolean"},"truncation_reason":{"type":"string","enum":["entry_limit","max_bytes","limit","provider_limit","output_budget"]},"truncation_message":{"type":"string"},"next_offset":{"type":"number"},"warnings":{"type":"array","items":{"type":"string"}}},"required":["uri","op"],"additionalProperties":false,"allOf":[{"if":{"properties":{"op":{"const":"attach"}},"required":["op"]},"then":{"properties":{"path":{"type":"string"},"mime_type":{"type":"string","enum":["image/jpeg","image/png","image/webp"]},"bytes":{"type":"integer","minimum":0,"maximum":8388608}},"required":["path","mime_type","bytes"]}}]},"output_truncated":{"type":"boolean"}},"required":["index","status","result"],"additionalProperties":false},{"type":"object","properties":{"index":{"type":"integer","minimum":0,"maximum":9007199254740991},"status":{"type":"string","const":"error"},"error":{"type":"object","properties":{"code":{"type":"string","enum":["HF_FS_INVALID_ARGUMENT","HF_FS_NOT_FOUND","HF_FS_NOT_A_DIRECTORY","HF_FS_NOT_A_FILE","HF_FS_UNSUPPORTED_OPERATION","HF_FS_ACCESS_DENIED","HF_FS_TEXT_ONLY","HF_FS_IMAGE_ONLY","HF_FS_UNSUPPORTED_MEDIA","HF_FS_IMAGE_TOO_LARGE","HF_FS_ATTACHMENT_BUDGET_EXCEEDED","HF_FS_IMAGE_CONTENT_DISABLED","HF_FS_ATTACHMENT_INTEGRITY"]},"message":{"type":"string"},"recovery":{"type":"string"},"retryable":{"type":"boolean","const":false},"suggestedOperation":{"type":"string","enum":["ls","cat","attach","stat","search"]}},"required":["code","message","recovery","retryable"],"additionalProperties":false}},"required":["index","status","error"],"additionalProperties":false}]}},"truncated":{"type":"boolean"},"truncation_reason":{"type":"string","const":"output_budget"}},"required":["results"],"additionalProperties":false}}],"digest":"sha256:f84ad54e509c4d2982d9f72afda3b5974fee215982e880762955e7b5745a62cc"},"jsonrpc":"2.0","id":2} ## 2. Protected-resource metadata, GET https://huggingface.co/.well-known/oauth-protected-resource/mcp (not named in the challenge; the path-aware well-known URI, the first fallback the specification names) HTTP/1.1 200 Connection Established HTTP/2 200 content-type: application/json; charset=utf-8 content-length: 236 date: Sat, 03 Oct 2026 06:04:05 GMT etag: W/"ec-P86f86b17VhYQiJ1sIDmoDRJcpg" x-powered-by: huggingface-moon x-request-id: Root=1-6ac09ad5-1ca28d36559d57f31229270b ratelimit: "media";r=9999;t=17 ratelimit-policy: "fixed window";"media";q=10000;w=300 cross-origin-opener-policy: same-origin referrer-policy: strict-origin-when-cross-origin access-control-max-age: 86400 access-control-allow-origin: https://huggingface.co vary: Origin access-control-expose-headers: X-Repo-Commit,X-Request-Id,X-Error-Code,X-Error-Message,X-Total-Count,ETag,Link,Accept-Ranges,Content-Range,X-Linked-Size,X-Linked-ETag,X-Xet-Hash x-cache: Miss from cloudfront via: 1.1 59aec6d4f93b3178d60fa3d2370ea542.cloudfront.net (CloudFront) x-amz-cf-pop: JFK50-P9 alt-svc: h3=":443"; ma=86400 x-amz-cf-id: Fi_GIyKoYQXgOIVi45ahTViRqwxR9u_FMwq56u0XtdMRGxg3wcBZuA== strict-transport-security: max-age=31536000 {"resource":"https://huggingface.co/mcp","authorization_servers":["https://huggingface.co"],"bearer_methods_supported":["header"],"scopes_supported":["openid","profile","read-mcp","read-repos","jobs","contribute-repos","inference-api"]} ## 3. Authorization-server metadata, GET https://huggingface.co/.well-known/oauth-authorization-server HTTP/1.1 200 Connection Established HTTP/2 200 content-type: application/json; charset=utf-8 content-length: 890 date: Sat, 03 Oct 2026 06:04:06 GMT etag: W/"37a-dttZVZA3HSuAYFH2OCoyqXSlr3k" x-powered-by: huggingface-moon x-request-id: Root=1-6ac09ad6-58720eed63da32ec5b364630 ratelimit: "media";r=9998;t=16 ratelimit-policy: "fixed window";"media";q=10000;w=300 cross-origin-opener-policy: same-origin referrer-policy: strict-origin-when-cross-origin access-control-max-age: 86400 access-control-allow-origin: https://huggingface.co vary: Origin access-control-expose-headers: X-Repo-Commit,X-Request-Id,X-Error-Code,X-Error-Message,X-Total-Count,ETag,Link,Accept-Ranges,Content-Range,X-Linked-Size,X-Linked-ETag,X-Xet-Hash x-cache: Miss from cloudfront via: 1.1 7e05050d5b982a3c10f24a3f84107440.cloudfront.net (CloudFront) x-amz-cf-pop: JFK50-P9 alt-svc: h3=":443"; ma=86400 x-amz-cf-id: b-lVwLK6v3WrziFAJykaU9OmiFxPUw7VfX2oNfvdK1n_hgtWz-jfOw== strict-transport-security: max-age=31536000 {"issuer":"https://huggingface.co","registration_endpoint":"https://huggingface.co/oauth/register","token_endpoint":"https://huggingface.co/oauth/token","authorization_endpoint":"https://huggingface.co/oauth/authorize","userinfo_endpoint":"https://huggingface.co/oauth/userinfo","device_authorization_endpoint":"https://huggingface.co/oauth/device","jwks_uri":"https://huggingface.co/oauth/jwks","response_types_supported":["code"],"response_modes_supported":["query"],"id_token_signing_alg_values_supported":["RS256"],"subject_types_supported":["public"],"code_challenge_methods_supported":["S256"],"token_endpoint_auth_methods_supported":["client_secret_basic","client_secret_post"],"client_id_metadata_document_supported":true,"grant_types_supported":["urn:ietf:params:oauth:grant-type:token-exchange","urn:ietf:params:oauth:grant-type:device_code","authorization_code","refresh_token"]} ## 4. REST, GET https://huggingface.co/api/models?limit=1, no Authorization header HTTP/1.1 200 Connection Established HTTP/2 200 content-type: application/json; charset=utf-8 content-length: 542 date: Sat, 03 Oct 2026 06:04:06 GMT etag: W/"21e-9C7G4LR8LKCNwLvwQ1G2ACaUC4o" x-powered-by: huggingface-moon x-request-id: Root=1-6ac09ad6-640ee94c3b6c010419b37811 ratelimit: "api";r=499;t=16 ratelimit-policy: "fixed window";"api";q=500;w=300 cross-origin-opener-policy: same-origin referrer-policy: strict-origin-when-cross-origin access-control-max-age: 86400 access-control-allow-origin: https://huggingface.co vary: Origin access-control-expose-headers: X-Repo-Commit,X-Request-Id,X-Error-Code,X-Error-Message,X-Total-Count,ETag,Link,Accept-Ranges,Content-Range,X-Linked-Size,X-Linked-ETag,X-Xet-Hash server-timing: mongo1-0;dur=1.3801779998466372 link: ; rel="next" x-cache: Miss from cloudfront via: 1.1 2f77ee6d00910cc9164b3833771289c2.cloudfront.net (CloudFront) x-amz-cf-pop: JFK50-P9 alt-svc: h3=":443"; ma=86400 x-amz-cf-id: IsBEAp1NIaT2SpfBITsyvZoaZNf4E2gDViwy0XrYXLvUCuM2TPyEZw== strict-transport-security: max-age=31536000 [{"_id":"6aacc6b34a8e10ba66ac6d0f","id":"convaiinnovations/laya","likes":5010,"trendingScore":1021,"private":false,"downloads":0,"tags":["transformers","safetensors","laya","system-one","calibrated-decisions","rlcd","classification","routing","scoring","guardrails","moderation","reinforcement-learning","commercial-use","text-classification","license:apache-2.0","endpoints_compatible","region:us"],"pipeline_tag":"text-classification","library_name":"transformers","createdAt":"2026-09-18T05:05:55.000Z","modelId":"convaiinnovations/laya"}] ## Appendix A (2026-10-03, 06:05Z to 06:08Z): keyless tools/call and the shapes the registry's gate sends. Same container, no credentials, no payment. Each request below opened its own initialize first (the server requires its mcp-session-id on every call after initialize); the session ids are redacted. ### A1. tools/call hf_fs with a wrong argument shape, 06:05:33Z (the prober's error, kept because the answer shows the validation path) $ POST https://huggingface.co/mcp {"jsonrpc":"2.0","id":3,"method":"tools/call","params":{"name":"hf_fs","arguments":{"command":"ls hf://models/trending"}}} HTTP/1.1 200 Connection Established HTTP/2 200 content-type: application/json content-length: 238 date: Sat, 03 Oct 2026 06:05:33 GMT vary: origin, access-control-request-method, access-control-request-headers x-content-type-options: nosniff referrer-policy: no-referrer access-control-allow-origin: * access-control-expose-headers: * x-proxied-host: http://10.114.19.24 x-proxied-replica: mydi1gyh-zn8px x-proxied-path: /mcp link: ;rel="canonical" x-request-id: 3o_cCY x-cache: Miss from cloudfront via: 1.1 cc68534c650c96afc37524c99c69a692.cloudfront.net (CloudFront) x-amz-cf-pop: BOS50-P6 alt-svc: h3=":443"; ma=86400 x-amz-cf-id: [cut by the prober] strict-transport-security: max-age=31536000 {"result":{"content":[{"type":"text","text":"Input validation error: Invalid arguments for tool hf_fs: operations: Invalid input: expected array, received undefined, Unrecognized key: \"command\""}],"isError":true},"jsonrpc":"2.0","id":3} ### A2. tools/call hf_fs ls hf://models/trending --limit 3, 06:06:07Z $ POST https://huggingface.co/mcp {"jsonrpc":"2.0","id":3,"method":"tools/call","params":{"name":"hf_fs","arguments":{"operations":[{"cmd":"ls","args":["hf://models/trending","--limit","3"]}]}}} HTTP/1.1 200 Connection Established HTTP/2 200 content-type: application/json content-length: 1624 date: Sat, 03 Oct 2026 06:06:07 GMT vary: origin, access-control-request-method, access-control-request-headers x-content-type-options: nosniff referrer-policy: no-referrer access-control-allow-origin: * access-control-expose-headers: * x-proxied-host: http://10.114.19.24 x-proxied-replica: mydi1gyh-zn8px x-proxied-path: /mcp link: ;rel="canonical" x-request-id: S1mDcM x-cache: Miss from cloudfront via: 1.1 cfe5ea671495866e5a4c623571ef38a8.cloudfront.net (CloudFront) x-amz-cf-pop: JFK50-P9 alt-svc: h3=":443"; ma=86400 x-amz-cf-id: [cut by the prober] strict-transport-security: max-age=31536000 { "result": { "content": [ { "type": "text", "text": "## Operation 1\n\n# hf_fs ls\n\nURI: `hf://models/trending`\n\n| Type | Path | URI | Target | Details |\n|---|---|---|---|---|\n| repo | convaiinnovations/laya | hf://models/convaiinnovations/laya | | repo=model, public, likes=5010, downloads=0, task=text-classification, updated=2026-09-24T05:39:22.000Z |\n| repo | Cloudflare/clef | hf://models/Cloudflare/clef | | repo=model, public, likes=827, downloads=824, task=image-text-to-text, updated=2026-10-01T15:23:46.000Z |\n| repo | abenzerps/Qwen-Image-2.1-Uncensored-GGUF | hf://models/abenzerps/Qwen-Image-2.1-Uncensored-GGUF | | repo=model, public, likes=2853, downloads=1376248, task=text-to-image, updated=2026-09-28T05:56:36.000Z |" } ], "structuredContent": { "results": [ { "index": 0, "status": "success", "result": { "uri": "hf://models/trending", "op": "ls", "entries": [ { "type": "repo", "path": "convaiinnovations/laya", "uri": "hf://models/convaiinnovations/laya", "repo_type": "model", "private": false, "gated": false, "likes": 5010, "downloads": 0, "task": "text-classification", "updated_at": "2026-09-24T05:39:22.000Z" }, { "type": "repo", "path": "Cloudflare/clef", "uri": "hf://models/Cloudflare/clef", "repo_type": "model", "private": false, "gated": false, "likes": 827, "downloads": 824, "task": "image-text-to-text", "updated_at": "2026-10-01T15:23:46.000Z" }, { "type": "repo", "path": "abenzerps/Qwen-Image-2.1-Uncensored-GGUF", "uri": "hf://models/abenzerps/Qwen-Image-2.1-Uncensored-GGUF", "repo_type": "model", "private": false, "gated": false, "likes": 2853, "downloads": 1376248, "task": "text-to-image", "updated_at": "2026-09-28T05:56:36.000Z" } ] } } ] } }, "jsonrpc": "2.0", "id": 3 } ### A3. tools/call hf_fs search hf://docs "how to use LoRA adapters with PEFT" --limit 3, 06:06:08Z $ POST https://huggingface.co/mcp {"jsonrpc":"2.0","id":5,"method":"tools/call","params":{"name":"hf_fs","arguments":{"operations":[{"cmd":"search","args":["hf://docs","how to use LoRA adapters with PEFT","--limit","3"]}]}}} HTTP/1.1 200 Connection Established HTTP/2 200 content-type: application/json content-length: 3828 date: Sat, 03 Oct 2026 06:06:09 GMT vary: origin, access-control-request-method, access-control-request-headers x-content-type-options: nosniff referrer-policy: no-referrer access-control-allow-origin: * access-control-expose-headers: * x-proxied-host: http://10.114.19.24 x-proxied-replica: mydi1gyh-zn8px x-proxied-path: /mcp link: ;rel="canonical" x-request-id: j9czK4 x-cache: Miss from cloudfront via: 1.1 59aec6d4f93b3178d60fa3d2370ea542.cloudfront.net (CloudFront) x-amz-cf-pop: JFK50-P9 alt-svc: h3=":443"; ma=86400 x-amz-cf-id: [cut by the prober] strict-transport-security: max-age=31536000 { "result": { "content": [ { "type": "text", "text": "## Operation 1\n\n# hf_fs search\n\nURI: `hf://docs`\n\n| Type | Path | URI | Target | Details |\n|---|---|---|---|---|\n| file | peft/v0.21.0/package\\_reference/lora\\_conversion.md | hf://docs/peft/v0.21.0/package\\_reference/lora\\_conversion.md\\#description | | library=peft, title=Description, anchor=description, to a LoRA adapter. Not all PEFT methods support this for now, but if they do, it means you can start with the PEFT method that works best for you and then later use it as if it were a LoRA adapter., web=https://huggingface.co/docs/peft/package\\_reference/lora\\_conversion\\#description, content type=text/markdown |\n| file | peft/v0.21.0/developer\\_guides/quantization.md | hf://docs/peft/v0.21.0/developer\\_guides/quantization.md\\#load-peft-lora-adapter-as-usual | | library=peft, title=Load PEFT LoRA adapter as usual, anchor=load-peft-lora-adapter-as-usual, \\# Load PEFT LoRA adapter as usual ... \\`\\`\\` An example demonstrating how to load a PEFT LoRA adapter into an INC-quantized FLUX text-to-image model for HPU devices is provided [here](https://github.com/huggingface/peft/blob/main/examples/sta\u2026, web=https://huggingface.co/docs/peft/developer\\_guides/quantization\\#load-peft-lora-adapter-as-usual, content type=text/markdown |\n| file | peft/v0.21.0/package\\_reference/hotswap.md | hf://docs/peft/v0.21.0/package\\_reference/hotswap.md\\#caveats | | library=peft, title=Caveats, anchor=caveats, \\#\\# Caveats Hotswapping works with transformers models and diffusers models. However, there are some caveats: - Right now, only LoRA is properly supported. - It only works for the same PEFT method, so no swapping LoRA and LoHa, for example.\u2026, web=https://huggingface.co/docs/peft/package\\_reference/hotswap\\#caveats, content type=text/markdown |" } ], "structuredContent": { "results": [ { "index": 0, "status": "success", "result": { "uri": "hf://docs", "op": "search", "entries": [ { "type": "file", "name": "lora_conversion.md", "path": "peft/v0.21.0/package_reference/lora_conversion.md", "uri": "hf://docs/peft/v0.21.0/package_reference/lora_conversion.md#description", "title": "Description", "anchor": "description", "description": "to a LoRA adapter. Not all PEFT methods support this for now, but if they do, it means you can start with the PEFT method that works best for you and then later use it as if it were a LoRA adapter.", "library": "peft", "url": "https://huggingface.co/docs/peft/package_reference/lora_conversion#description", "content_type": "text/markdown" }, { "type": "file", "name": "quantization.md", "path": "peft/v0.21.0/developer_guides/quantization.md", "uri": "hf://docs/peft/v0.21.0/developer_guides/quantization.md#load-peft-lora-adapter-as-usual", "title": "Load PEFT LoRA adapter as usual", "anchor": "load-peft-lora-adapter-as-usual", "description": "# Load PEFT LoRA adapter as usual ... ``` An example demonstrating how to load a PEFT LoRA adapter into an INC-quantized FLUX text-to-image model for HPU devices is provided [here](https://github.com/huggingface/peft/blob/main/examples/sta\u2026", "library": "peft", "url": "https://huggingface.co/docs/peft/developer_guides/quantization#load-peft-lora-adapter-as-usual", "content_type": "text/markdown" }, { "type": "file", "name": "hotswap.md", "path": "peft/v0.21.0/package_reference/hotswap.md", "uri": "hf://docs/peft/v0.21.0/package_reference/hotswap.md#caveats", "title": "Caveats", "anchor": "caveats", "description": "## Caveats Hotswapping works with transformers models and diffusers models. However, there are some caveats: - Right now, only LoRA is properly supported. - It only works for the same PEFT method, so no swapping LoRA and LoHa, for example.\u2026", "library": "peft", "url": "https://huggingface.co/docs/peft/package_reference/hotswap#caveats", "content_type": "text/markdown" } ] } } ] } }, "jsonrpc": "2.0", "id": 5 } ### A4. GET https://huggingface.co/mcp/server-card, user-agent public-agents-ci, 06:07:09Z (status line, content-type, date and etag kept; the body whole) HTTP/2 200 content-type: application/mcp-server-card+json; charset=utf-8 date: Sat, 03 Oct 2026 06:07:09 GMT etag: "EnisEUnCSm_tyNl7F2i19azLkRQmNoAj1ihjxr4vCQQ" {"$schema":"https://static.modelcontextprotocol.io/schemas/v1/server-card.schema.json","name":"huggingface.co/mcp","version":"0.4.27","description":"Official MCP server for the Hugging Face Hub.","title":"Hugging Face","websiteUrl":"https://huggingface.co/mcp","remotes":[{"type":"streamable-http","url":"https://huggingface.co/mcp"}]} ### A5. POST https://huggingface.co/mcp with body {} , user-agent public-agents-ci, accept */*, content-type application/json, 06:07:09Z (the shape the registry's link gate sends to a probe surface; status line, content-type and date kept) HTTP/2 400 content-type: application/json date: Sat, 03 Oct 2026 06:07:10 GMT {"jsonrpc":"2.0","error":{"code":-32600,"message":"Bad Request: the request body is not a valid JSON-RPC message"},"id":null} ### A6. initialize (clientInfo public-agents-researcher 1.0), 06:07:17Z, headers HTTP/1.1 200 Connection Established HTTP/2 200 content-type: application/json content-length: 2006 date: Sat, 03 Oct 2026 06:07:17 GMT vary: origin, access-control-request-method, access-control-request-headers x-content-type-options: nosniff referrer-policy: no-referrer access-control-allow-origin: * access-control-expose-headers: * mcp-session-id: [redacted by the prober: a per-session id] x-proxied-host: http://10.114.19.24 x-proxied-replica: mydi1gyh-zn8px x-proxied-path: /mcp link: ;rel="canonical" x-request-id: lGB5Nv x-cache: Miss from cloudfront via: 1.1 7fe59fc9baddfac8dd658cc0b65f3f4c.cloudfront.net (CloudFront) x-amz-cf-pop: BOS50-P6 alt-svc: h3=":443"; ma=86400 x-amz-cf-id: [cut by the prober] strict-transport-security: max-age=31536000 ### A7. tools/call hf_whoami with no arguments on that session, 06:07:17Z $ POST https://huggingface.co/mcp {"jsonrpc":"2.0","id":4,"method":"tools/call","params":{"name":"hf_whoami","arguments":{}}} HTTP/1.1 200 Connection Established HTTP/2 200 content-type: application/json content-length: 709 date: Sat, 03 Oct 2026 06:07:17 GMT vary: origin, access-control-request-method, access-control-request-headers x-content-type-options: nosniff referrer-policy: no-referrer access-control-allow-origin: * access-control-expose-headers: * x-proxied-host: http://10.114.19.24 x-proxied-replica: mydi1gyh-zn8px x-proxied-path: /mcp link: ;rel="canonical" x-request-id: Ga1OPT x-cache: Miss from cloudfront via: 1.1 e61d793f1b467706962fbe277321dfd6.cloudfront.net (CloudFront) x-amz-cf-pop: BOS50-P6 alt-svc: h3=":443"; ma=86400 x-amz-cf-id: [cut by the prober] strict-transport-security: max-age=31536000 { "result": { "content": [ { "type": "text", "text": "# Hugging Face authentication\n\nThe Hugging Face tools are being used anonymously and may be rate limited.\n\nVisit https://hf.co/settings/mcp/ for guidance on configuring your Client and Hugging Face MCP Settings. Go to https://hf.co/join to create a free \ud83e\udd17 account and enjoy higher rate limits and other benefits." } ], "structuredContent": { "status": "anonymous", "account": null, "organizations": [], "credential": null, "guidance": "Visit https://hf.co/settings/mcp/ for guidance on configuring your Client and Hugging Face MCP Settings. Go to https://hf.co/join to create a free \ud83e\udd17 account and enjoy higher rate limits and other benefits." } }, "jsonrpc": "2.0", "id": 4 } ### A8. tools/list with NO mcp-session-id header, 06:07:17Z (a fresh request, no initialize before it) $ POST https://huggingface.co/mcp {"jsonrpc":"2.0","id":2,"method":"tools/list","params":{}} HTTP/2 400 content-length: 80 date: Sat, 03 Oct 2026 06:07:18 GMT {"jsonrpc":"2.0","error":{"code":-32600,"message":"Session ID required"},"id":2} ### A9. The full keyless tools/list body of 06:04Z (section 1b above is cut at 20,000 bytes; this is the whole 18,961-byte JSON, pretty-printed) { "result": { "tools": [ { "name": "hf_whoami", "title": "Hugging Face User Info", "description": "Inspect the current Hugging Face authentication context, including the account, visible organization memberships, and credential access details. Read-only and never returns credential values.", "inputSchema": { "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "properties": {} }, "annotations": { "title": "Hugging Face User Info", "destructiveHint": false, "idempotentHint": false, "readOnlyHint": true, "openWorldHint": false }, "outputSchema": { "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "oneOf": [ { "type": "object", "properties": { "status": { "type": "string", "const": "authenticated" }, "account": { "type": "object", "properties": { "id": { "type": "string", "minLength": 1 }, "type": { "type": "string", "enum": [ "user", "org", "app" ] }, "name": { "type": "string", "minLength": 1 }, "url": { "type": "string", "format": "uri" }, "is_pro": { "type": "boolean" } }, "required": [ "id", "type", "name" ], "additionalProperties": false }, "organizations": { "type": "array", "items": { "type": "object", "properties": { "id": { "type": "string", "minLength": 1 }, "name": { "type": "string", "minLength": 1 }, "display_name": { "type": "string", "minLength": 1 }, "url": { "type": "string", "format": "uri" }, "role": { "type": "string", "minLength": 1 }, "plan": { "type": "string", "minLength": 1 }, "security_restrictions": { "type": "array", "items": { "type": "string", "minLength": 1 } }, "resource_groups": { "type": "array", "items": { "type": "object", "properties": { "id": { "type": "string", "minLength": 1 }, "name": { "type": "string", "minLength": 1 }, "role": { "type": "string", "minLength": 1 } }, "required": [ "id", "name", "role" ], "additionalProperties": false } } }, "required": [ "id", "name", "display_name", "url" ], "additionalProperties": false } }, "credential": { "oneOf": [ { "type": "object", "properties": { "type": { "type": "string", "const": "personal_access_token" }, "role": { "type": "string", "enum": [ "read", "write", "fine_grained" ] }, "created_at": { "type": "string", "format": "date-time", "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d:[0-5]\\d(?:\\.\\d+)?(?:Z))$" }, "permissions": { "type": "object", "properties": { "scoped": { "type": "array", "items": { "type": "object", "properties": { "entity": { "type": "object", "properties": { "id": { "type": "string", "minLength": 1 }, "type": { "type": "string", "enum": [ "model", "dataset", "space", "bucket", "kernel", "collection", "org", "user", "resource_group", "oauth_app" ] }, "name": { "type": "string", "minLength": 1 } }, "required": [ "id", "type" ], "additionalProperties": false }, "permissions": { "type": "array", "items": { "type": "string", "minLength": 1 } }, "restrictions": { "type": "array", "items": { "type": "object", "properties": { "resource_type": { "type": "string", "const": "inference_endpoint" }, "patterns": { "type": "array", "items": { "type": "string", "minLength": 1 } } }, "required": [ "resource_type", "patterns" ], "additionalProperties": false } } }, "required": [ "entity", "permissions" ], "additionalProperties": false } }, "global": { "type": "array", "items": { "type": "string", "minLength": 1 } }, "can_read_gated_repos": { "type": "boolean" } }, "required": [ "scoped" ], "additionalProperties": false } }, "required": [ "type", "role" ], "additionalProperties": false }, { "type": "object", "properties": { "type": { "type": "string", "const": "oauth" }, "expires_at": { "type": "string", "format": "date-time", "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d:[0-5]\\d(?:\\.\\d+)?(?:Z))$" }, "scopes": { "type": "array", "items": { "type": "string", "minLength": 1 } } }, "required": [ "type" ], "additionalProperties": false }, { "type": "object", "properties": { "type": { "type": "string", "const": "app_token" }, "role": { "type": "string", "minLength": 1 }, "entities": { "type": "array", "items": { "type": "object", "properties": { "type": { "type": "string", "enum": [ "model", "dataset", "space", "bucket", "kernel", "org" ] }, "name": { "type": "string", "minLength": 1 } }, "required": [ "name" ], "additionalProperties": false } } }, "required": [ "type", "entities" ], "additionalProperties": false }, { "type": "object", "properties": { "type": { "type": "string", "const": "other" }, "expires_at": { "type": "string", "format": "date-time", "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d:[0-5]\\d(?:\\.\\d+)?(?:Z))$" } }, "required": [ "type" ], "additionalProperties": false } ] } }, "required": [ "status", "account", "organizations", "credential" ], "additionalProperties": false }, { "type": "object", "properties": { "status": { "type": "string", "const": "anonymous" }, "account": { "type": "null" }, "organizations": { "type": "array", "items": { "type": "object", "properties": { "id": { "type": "string", "minLength": 1 }, "name": { "type": "string", "minLength": 1 }, "display_name": { "type": "string", "minLength": 1 }, "url": { "type": "string", "format": "uri" }, "role": { "type": "string", "minLength": 1 }, "plan": { "type": "string", "minLength": 1 }, "security_restrictions": { "type": "array", "items": { "type": "string", "minLength": 1 } }, "resource_groups": { "type": "array", "items": { "type": "object", "properties": { "id": { "type": "string", "minLength": 1 }, "name": { "type": "string", "minLength": 1 }, "role": { "type": "string", "minLength": 1 } }, "required": [ "id", "name", "role" ], "additionalProperties": false } } }, "required": [ "id", "name", "display_name", "url" ], "additionalProperties": false } }, "credential": { "type": "null" }, "guidance": { "type": "string", "minLength": 1 } }, "required": [ "status", "account", "organizations", "credential", "guidance" ], "additionalProperties": false }, { "type": "object", "properties": { "status": { "type": "string", "const": "authentication_unverified" }, "account": { "type": "null" }, "organizations": { "type": "array", "items": { "type": "object", "properties": { "id": { "type": "string", "minLength": 1 }, "name": { "type": "string", "minLength": 1 }, "display_name": { "type": "string", "minLength": 1 }, "url": { "type": "string", "format": "uri" }, "role": { "type": "string", "minLength": 1 }, "plan": { "type": "string", "minLength": 1 }, "security_restrictions": { "type": "array", "items": { "type": "string", "minLength": 1 } }, "resource_groups": { "type": "array", "items": { "type": "object", "properties": { "id": { "type": "string", "minLength": 1 }, "name": { "type": "string", "minLength": 1 }, "role": { "type": "string", "minLength": 1 } }, "required": [ "id", "name", "role" ], "additionalProperties": false } } }, "required": [ "id", "name", "display_name", "url" ], "additionalProperties": false } }, "credential": { "type": "null" }, "guidance": { "type": "string", "minLength": 1 } }, "required": [ "status", "account", "organizations", "credential", "guidance" ], "additionalProperties": false } ] } }, { "name": "hub_repo_search", "title": "Repo Search", "description": "Search Hugging Face repositories with a shared query interface. You can target models, datasets, spaces, or aggregate across multiple repo types in one call. Include links to repositories in your response.", "inputSchema": { "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "properties": { "query": { "description": "Search term. Leave blank and specify sort + limit to browse trending or recent repositories.", "type": "string" }, "repo_types": { "default": [ "model", "dataset" ], "description": "Repository types to search. Defaults to [\"model\", \"dataset\"]. space uses keyword search via /api/spaces.", "minItems": 1, "maxItems": 3, "type": "array", "items": { "type": "string", "enum": [ "model", "dataset", "space" ] } }, "author": { "description": "Organization or user namespace to filter by (e.g. 'google', 'meta-llama', 'huggingface').", "type": "string" }, "filters": { "description": "Optional hub filter tags. Applied to each selected repo type (e.g. [\"text-generation\"], [\"language:en\"], [\"mcp-server\"]).", "type": "array", "items": { "type": "string" } }, "sort": { "description": "Sort order (descending): trendingScore, downloads, likes, createdAt, lastModified", "type": "string", "enum": [ "trendingScore", "downloads", "likes", "createdAt", "lastModified" ] }, "limit": { "default": 20, "description": "Maximum number of results to return per selected repo type", "type": "number", "minimum": 1, "maximum": 100 } } }, "annotations": { "title": "Repo Search", "destructiveHint": false, "idempotentHint": false, "readOnlyHint": true, "openWorldHint": true } }, { "name": "hub_repo_details", "title": "Hub Repository Details", "description": "Get details for one or more Hugging Face repos (model, dataset, or space). Auto-detects type unless specified. For datasets, use operations: overview, dataset_structure, dataset_preview. Use dataset_structure first to discover configs, splits, sizes, and schema. Use dataset_preview only when config and split are known, unless the dataset has a single config/split.", "inputSchema": { "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "properties": { "repo_ids": { "minItems": 1, "maxItems": 10, "type": "array", "items": { "type": "string", "minLength": 1 }, "description": "Repo IDs for (models|dataset/space) - usually in author/name format (e.g. openai/gpt-oss-120b)" }, "repo_type": { "description": "Specify lookup type; otherwise auto-detects", "type": "string", "enum": [ "model", "dataset", "space" ] }, "operations": { "description": "Details to return. Defaults to [\"overview\"]. For datasets, prefer [\"overview\", \"dataset_structure\"] first; then call [\"dataset_preview\"] with config and split.", "type": "array", "items": { "type": "string", "enum": [ "overview", "dataset_structure", "dataset_preview" ] } }, "config": { "description": "Dataset Viewer config. Required for dataset_preview when the dataset has multiple config/split options. Discover via dataset_structure.", "type": "string" }, "split": { "description": "Dataset Viewer split. Required for dataset_preview when the dataset has multiple config/split options. Discover via dataset_structure.", "type": "string" }, "offset": { "description": "Row offset for dataset_preview. Defaults to 0.", "type": "integer", "minimum": 0, "maximum": 9007199254740991 }, "limit": { "description": "Row count for dataset_preview. Defaults to 5 and is clamped to 1-100.", "type": "integer", "minimum": -9007199254740991, "maximum": 9007199254740991 } }, "required": [ "repo_ids" ] }, "annotations": { "title": "Hub Repository Details", "destructiveHint": false, "idempotentHint": false, "readOnlyHint": true, "openWorldHint": true } }, { "name": "hf_fs", "title": "Hugging Face Hub: Find, use and view models, datasets, spaces, buckets, papers, documentation and collections. Get daily papers reports, and browse trending content. ", "description": "When to use: Hugging Face Hub models, datasets, Spaces, collections, papers, daily papers, today's trending models, current paper leaderboard, docs, and repository files.\n\nExamples:\n {\"operations\":[{\"cmd\":\"ls\",\"args\":[\"hf://models/trending\",\"--limit\",\"10\"]}]}\n {\"operations\":[{\"cmd\":\"ls\",\"args\":[\"hf://papers/trending\"]}]}\n {\"operations\":[{\"cmd\":\"ls\",\"args\":[\"hf://papers/daily/latest\"]}]}\n {\"operations\":[{\"cmd\":\"cat\",\"args\":[\"hf://papers/2501.00001/paper.md\"]}]}\n\nUse hf_fs for Hugging Face Hub filesystem operations. Call it with operations, an array of {cmd, args} items; multiple operations may be submitted together.\n\nUsage:\n {\"operations\":[{\"cmd\":\"ls\",\"args\":[\"hf://models/org/repo\"]}]}\n\nGrammar; each string below is one args array item:\n ls URI [--recursive] [--glob GLOB] [--type TYPE] [--sort SORT] [--limit N]\n cat URI [--offset N] [--max-bytes N]\n attach URI [--max-bytes N]\n stat URI\n find URI [--name GLOB] [--path GLOB] [--type TYPE] [--limit N]\n search URI [QUERY] [--type TYPE] [--sort SORT] [--tag TAG] [--kind mcp] [--limit N]\n\nCOMMAND = ls|cat|attach|stat|find|search.\nTYPE = file|dir|repo|bucket|collection|paper|link.\nSORT = createdAt|downloads|likes|lastModified|likes30d|trendingScore|mainSize|id|trending|upvotes.\nURI is a canonical hf:// URI. QUERY and GLOB are each one string.\n\nUse search for resource discovery, not repository-content search; ls for a known directory, find for recursive file discovery by name/path (not file contents), stat for filesystem metadata or an uncertain target type, cat for text contents, and attach for a complete JPEG, PNG, or WebP image. When the request gives an exact text-file URI, use cat directly; do not add ls or stat first. stat does not read the contents of JSON, Markdown, or other text files.\n\nSearch scopes: hf://models[/OWNER], hf://datasets[/OWNER], hf://spaces[/OWNER], hf://collections[/OWNER], hf://papers, and hf://docs[/...]. Repository and repository-file scopes are not supported: search a resource root or owner scope to discover resources; use find for file discovery within a repository or cat for a known text file. Paper and documentation search require QUERY. --tag (repeatable) and --kind are supported only on exactly hf://spaces, not owner scopes or other roots. The only valid --kind value is mcp, which selects MCP Spaces.\nUse ls hf://models/trending, hf://datasets/trending, hf://spaces/trending, or hf://papers/trending for trending listings.\nhf://papers/ID is a paper directory, not paper text. Use cat hf://papers/ID/paper.md for paper text and cat hf://papers/ID/metadata.json for metadata. No preliminary listing is needed for these known paths. Use ls hf://papers/ID to discover other resources.\nOmit --limit, --sort, and --type unless the request requires them. Limits and path-specific behavior are documented at hf://README.md. Issue one hf_fs call.", "inputSchema": { "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "properties": { "operations": { "minItems": 1, "maxItems": 30, "type": "array", "items": { "type": "object", "properties": { "cmd": { "type": "string", "enum": [ "ls", "cat", "attach", "stat", "find", "search" ], "description": "Command to execute." }, "args": { "type": "array", "items": { "type": "string" }, "description": "Command arguments. First item must be an hf:// URI, not a local path or bare filename. One argument per array item. search discovers resources, not repository contents; use root/owner discovery scopes, find for file discovery, or cat for a known text file. --tag and --kind require exactly hf://spaces; the only valid --kind value is mcp." } }, "required": [ "cmd", "args" ], "additionalProperties": false } } }, "required": [ "operations" ], "additionalProperties": false }, "annotations": { "title": "Hugging Face Hub: Find, use and view models, datasets, spaces, buckets, papers, documentation and collections. Get daily papers reports, and browse trending content. ", "destructiveHint": false, "idempotentHint": false, "readOnlyHint": true, "openWorldHint": true }, "outputSchema": { "$schema": "https://json-schema.org/draft/2020-12/schema", "type": "object", "properties": { "results": { "minItems": 1, "maxItems": 30, "type": "array", "items": { "oneOf": [ { "type": "object", "properties": { "index": { "type": "integer", "minimum": 0, "maximum": 9007199254740991 }, "status": { "type": "string", "const": "success" }, "result": { "type": "object", "properties": { "uri": { "type": "string" }, "op": { "type": "string", "enum": [ "ls", "cat", "attach", "stat", "find", "search" ] }, "entries": { "type": "array", "items": { "type": "object", "properties": { "type": { "type": "string", "enum": [ "file", "dir", "repo", "bucket", "collection", "paper", "link" ] }, "path": { "type": "string" }, "uri": { "type": "string" }, "name": { "type": "string" }, "target_uri": { "type": "string" }, "repo_type": { "type": "string", "enum": [ "model", "dataset", "space", "bucket" ] }, "size": { "type": "number" }, "total_files": { "type": "number" }, "lfs": { "type": "boolean" }, "private": { "type": "boolean" }, "gated": { "anyOf": [ { "type": "boolean", "const": false }, { "type": "string", "enum": [ "auto", "manual" ] } ] }, "likes": { "type": "number" }, "downloads": { "type": "number" }, "task": { "type": "string" }, "library": { "type": "string" }, "tags": { "type": "array", "items": { "type": "string" } }, "trending_score": { "type": "number" }, "sdk": { "type": "string" }, "title": { "type": "string" }, "category": { "type": "string" }, "semantic_relevance": { "type": "number" }, "anchor": { "type": "string" }, "description": { "type": "string" }, "upvotes": { "type": "number" }, "created_at": { "type": "string" }, "published_at": { "type": "string" }, "daily_papers_date": { "type": "string" }, "daily_papers_uri": { "type": "string" }, "url": { "type": "string" }, "arxiv_url": { "type": "string" }, "observed_at": { "type": "string" }, "updated_at": { "type": "string" }, "content_type": { "type": "string", "enum": [ "application/json", "text/markdown" ] } }, "required": [ "type", "path" ], "additionalProperties": false } }, "path": { "type": "string" }, "content": { "type": "string" }, "content_type": { "type": "string", "enum": [ "application/json", "text/markdown" ] }, "mime_type": { "type": "string", "enum": [ "image/jpeg", "image/png", "image/webp" ] }, "section": { "type": "string" }, "bytes": { "type": "number" }, "exists": { "type": "boolean" }, "type": { "type": "string", "enum": [ "namespace", "repo", "dir", "file", "collection", "paper", "link", "missing" ] }, "namespace": { "type": "string" }, "size": { "type": "number" }, "lfs": { "type": "boolean" }, "target_uri": { "type": "string" }, "published_at": { "type": "string" }, "daily_papers_date": { "type": "string" }, "daily_papers_uri": { "type": "string" }, "url": { "type": "string" }, "arxiv_url": { "type": "string" }, "truncated": { "type": "boolean" }, "truncation_reason": { "type": "string", "enum": [ "entry_limit", "max_bytes", "limit", "provider_limit", "output_budget" ] }, "truncation_message": { "type": "string" }, "next_offset": { "type": "number" }, "warnings": { "type": "array", "items": { "type": "string" } } }, "required": [ "uri", "op" ], "additionalProperties": false, "allOf": [ { "if": { "properties": { "op": { "const": "attach" } }, "required": [ "op" ] }, "then": { "properties": { "path": { "type": "string" }, "mime_type": { "type": "string", "enum": [ "image/jpeg", "image/png", "image/webp" ] }, "bytes": { "type": "integer", "minimum": 0, "maximum": 8388608 } }, "required": [ "path", "mime_type", "bytes" ] } } ] }, "output_truncated": { "type": "boolean" } }, "required": [ "index", "status", "result" ], "additionalProperties": false }, { "type": "object", "properties": { "index": { "type": "integer", "minimum": 0, "maximum": 9007199254740991 }, "status": { "type": "string", "const": "error" }, "error": { "type": "object", "properties": { "code": { "type": "string", "enum": [ "HF_FS_INVALID_ARGUMENT", "HF_FS_NOT_FOUND", "HF_FS_NOT_A_DIRECTORY", "HF_FS_NOT_A_FILE", "HF_FS_UNSUPPORTED_OPERATION", "HF_FS_ACCESS_DENIED", "HF_FS_TEXT_ONLY", "HF_FS_IMAGE_ONLY", "HF_FS_UNSUPPORTED_MEDIA", "HF_FS_IMAGE_TOO_LARGE", "HF_FS_ATTACHMENT_BUDGET_EXCEEDED", "HF_FS_IMAGE_CONTENT_DISABLED", "HF_FS_ATTACHMENT_INTEGRITY" ] }, "message": { "type": "string" }, "recovery": { "type": "string" }, "retryable": { "type": "boolean", "const": false }, "suggestedOperation": { "type": "string", "enum": [ "ls", "cat", "attach", "stat", "search" ] } }, "required": [ "code", "message", "recovery", "retryable" ], "additionalProperties": false } }, "required": [ "index", "status", "error" ], "additionalProperties": false } ] } }, "truncated": { "type": "boolean" }, "truncation_reason": { "type": "string", "const": "output_budget" } }, "required": [ "results" ], "additionalProperties": false } } ], "digest": "sha256:f84ad54e509c4d2982d9f72afda3b5974fee215982e880762955e7b5745a62cc" }, "jsonrpc": "2.0", "id": 2 } === APPENDIX 2026-10-03 (B), 12:04Z to 12:20Z, same container (egress 205.188.204.187), keyless, no payment: Astro Docs MCP server (mcp.docs.astro.build), the vendor surfaces behind it, and the ownership proofs. Follows the five-server pass of 06:03Z that found it. Headers below are the origin's; the proxy CONNECT line is omitted. === --- 1. initialize POST https://mcp.docs.astro.build/mcp {"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-06-18","capabilities":{},"clientInfo":{"name":"plumb-registry-probe","version":"1.0"}}} (content-type application/json; accept application/json, text/event-stream) HTTP/1.1 200 Connection Established HTTP/2 200 date: Sat, 03 Oct 2026 12:18:13 GMT content-type: text/event-stream server: cloudflare cf-ray: a44be360a9d93d15-BOS body bytes: 208 sha256: 4e62641274af8d5a20b5df808c2aa86ed2091b86e78244164c833b0afa78cf71 event: message data: {"result":{"protocolVersion":"2025-06-18","capabilities":{"logging":{},"tools":{"listChanged":true}},"serverInfo":{"name":"Astro Docs server","version":"1.0.0"}},"jsonrpc":"2.0","id":1} --- 2. tools/list, no session header (none was issued) POST https://mcp.docs.astro.build/mcp {"jsonrpc":"2.0","id":2,"method":"tools/list","params":{}} HTTP/1.1 200 Connection Established HTTP/2 200 date: Sat, 03 Oct 2026 12:18:46 GMT content-type: text/event-stream server: cloudflare cf-ray: a44be4301bfc2d6c-BOS body bytes: 386 sha256: a205c7502a43efd9c627362ffb3a8473c28d310de641df11e416487ee5964aa7 event: message data: {"result":{"tools":[{"name":"search_astro_docs","title":"Search Astro Docs","description":"Search the official Astro framework docs","inputSchema":{"type":"object","properties":{"query":{"type":"string","description":"Search query"}},"required":["query"],"additionalProperties":false,"$schema":"http://json-schema.org/draft-07/schema#"}}]},"jsonrpc":"2.0","id":2} --- 3. tools/call search_astro_docs POST https://mcp.docs.astro.build/mcp {"jsonrpc":"2.0","id":3,"method":"tools/call","params":{"name":"search_astro_docs","arguments":{"query":"How do I define a content collection schema?"}}} (0.91 s total) HTTP/1.1 200 Connection Established HTTP/2 200 date: Sat, 03 Oct 2026 12:19:25 GMT content-type: text/event-stream server: cloudflare cf-ray: a44be525bb7675f9-BOS body bytes: 25218 sha256: a6137fa1940f4fa2deeefa3e5ef352c87f1571cc672f40e101489bb5a69c56b6 event: message data: {"result":{"content":[{"type":"text","text":"{\n \"search_results\": [\n {\n \"content\": \"# En > Guides > Content collections\\n## Defining the collection schema\\n\\nSchemas enforce consistent frontmatter or entry data within a collection through Zod validation. A schema **guarantees** that this data exists in a predictable form when you need to reference or query it. If any file violates its collection schema, Astro will provide a helpful error to let you know.\\n\\nSchemas also power Astro’s automatic TypeScript typings for your content. When you define a schema for your collection, Astro will automatically generate and apply a TypeScript interface to it. The result is full TypeScript support when you query your collection, including property autocompletion and type-checking.\\n\\nTip\\n\\nIn order for Astro to recognize a new or updated schema, you may need to restart the dev server or [sync the content layer](https://docs.astro.build/en/reference/cli-reference/#astro-dev) (`s + enter`) to define the `astro:content` module.\\n\\nProviding a `schema` is optional, but highly recommended! If you choose to use a schema, then every frontmatter or data property of your collection entries must be defined using a [Zod data type](https://docs.astro.build/en/reference/modules/astro-zod/#common-data-type-validators):\\n\\nsrc/content.config.ts\\n\\n```\\nimport { defineCollection } from \\\"astro:content\\\";import { z } from \\\"astro/zod\\\";import { glob, file } from \\\"astro/loaders\\\";\\nconst blog = defineCollection({ loader: glob({ pattern: \\\"**/*.md\\\", base: \\\"./src/data/blog\\\" }), schema: z.object({ title: z.string(), description: z.string(), pubDate: z.coerce.date(), updatedDate: z.coerce.date().optional(), }),});const dogs = defineCollection({ loader: file(\\\"src/data/dogs.json\\\"), schema: z.object({ id: z.string(), breed: z.string(), temperament: z.array(z.string()), }),});\\nexport const collections = { blog, dogs };\\n```\\n\\n#### Defining datatypes with Zod\\n\\nAstro uses [Zod](https://github.com/colinhacks/zod) to power its content schemas. With Zod, Astro is able to validate every file’s data within a collection *and* provide automatic TypeScript types when you query content from inside your project.\\n\\nTo use Zod in Astro, import the `z` utility from `\\\"astro/zod\\\"`. This is a re-export of the Zod library, and it supports all of the features of Zod 4.\\n\\nSee the [`z` utility reference](https://docs.astro.build/en/reference/modules/astro-zod/) for a cheatsheet of common datatypes and to learn how Zod works and what features are available.\\n\\n##### Zod schema methods\\n\\nAll [Zod schema methods](https://docs.astro.build/en/reference/modules/astro-zod/#using-zod-methods) (e.g. `.parse()`, `.transform()`) are available, with some limitations. Notably, performing custom validation checks on images using `image().refine()` is unsupported.\",\n \"source_url\": \"https://docs.astro.build/en/guides/content-collections/#defining-the-collection-schema\",\n \"title\": \"Content collections|Defining the collection schema\",\n \"source_type\": \"Astro Docs\"\n },\n {\n \"content\": \"# En > Guides > Content collections > Defining the collection schema\\n## Defining collection references\\n\\nCollection entries can also “reference” other related entries.\\n\\nWith the [`reference()` function](https://docs.astro.build/en/reference/modules/astro-content/#reference), you can define a property in a collection schema as an entry from another collection. For example, you can require that every `space-shuttle` entry includes a `pilot` property which uses the `pilot` collection’s own schema for type checking, autocomplete, and validation.\\n\\nA common example is a blog post that references reusable author profiles stored as JSON, or related post URLs stored in the same collection:\\n\\nsrc/content.config.ts\\n\\n```\\nimport { defineCollection, reference } from \\\"astro:content\\\";import { glob } from \\\"astro/loaders\\\";import { z } from \\\"astro/zod\\\";\\nconst blog = defineCollection({ loader: glob({ base: \\\"./src/content/blog\\\", pattern: \\\"**/*.{md,mdx}\\\" }), schema: z.object({ title: z.string(), // Reference a single author from the `authors` collection by `id` author: reference(\\\"authors\\\"), // Reference an array of related posts from the `blog` collection by `id` relatedPosts: z.array(reference(\\\"blog\\\")), }),});\\nconst authors = defineCollection({ loader: glob({ pattern: \\\"**/*.json\\\", base: \\\"./src/data/authors\\\" }), schema: z.object({ name: z.string(), portfolio: z.url(), }),});\\nexport const collections = { blog, authors };\\n```\\n\\nThis example blog post specifies the `id`s of related posts and the `id` of the post author:\\n\\nsrc/content/blog/welcome.md\\n\\n```\\n---title: \\\"Welcome to my blog\\\"author: ben-holmes # references `src/data/authors/ben-holmes.json`relatedPosts:- about-me # references `src/content/blog/about-me.md`- my-year-in-review # references `src/content/blog/my-year-in-review.md`---\\n```\\n\\nThese references will be transformed into objects containing a `collection` key and an `id` key, allowing you to easily [query them in your templates](https://docs.astro.build/en/guides/content-collections/#accessing-referenced-data).\",\n \"source_url\": \"https://docs.astro.build/en/guides/content-collections/#defining-collection-references\",\n \"title\": \"Content collections|Defining collection references\",\n \"source_type\": \"Astro Docs\"\n },\n {\n \"content\": \"# En > Tutorial > 6-islands\\n## Optional: Make a content collection\\n\\nNow that you have a blog using Astro’s [built-in file-based routing](https://docs.astro.build/en/guides/routing/#static-routes), you will update it to use a [content collection](https://docs.astro.build/en/guides/content-collections/). Content collections are a powerful way to manage groups of similar content, such as blog posts.\\n\\nGet ready to…\\n\\n- Move your folder of blog posts into `src/blog/`\\n- Create a schema to define your blog post frontmatter\\n- Use `getCollection()` to get blog post content and metadata\\n\\n### Learn: Pages vs Collections\\n\\nEven when using content collections, you will still use the `src/pages/` folder for individual pages, such as your About Me page. But, moving your blog posts outside of this special folder will allow you to use more powerful and performant APIs to generate your blog post index and display your individual blog posts.\\n\\nAt the same time, you’ll receive better guidance and autocompletion in your code editor because you will have a **[schema](https://docs.astro.build/en/guides/content-collections/#defining-the-collection-schema)** to define a common structure for each post that Astro will help you enforce through [Zod](https://zod.dev/), a schema declaration and validation library for TypeScript. In your schema, you can specify when frontmatter properties are required, such as a description or an author, and which data type each property must be, such as a string or an array. This leads to catching many mistakes sooner, with descriptive error messages telling you exactly what the problem is.\\n\\nRead more about [Astro’s content collections](https://docs.astro.build/en/guides/content-collections/) in our guide, or get started with the instructions below to convert a basic blog from `src/pages/posts/` to `src/blog/`.\\n\\n#### Test your knowledge\\n\\n1. Which type of page would you probably keep in `src/pages/`?\\n\\n 1. Blog posts that all contain the same basic structure and metadata\\n 1. Product pages in an eCommerce site\\n 1. A contact page, because you do not have multiple similar pages of this type\\n\\nSubmit\\n2\\\\. Which is **not** a benefit of moving blog posts to a content collection?\\n\\n1\\\\. Pages are automatically created for each file\\n2\\\\. Better error messages, because Astro knows more about each file\\n3\\\\. Better data fetching, with a more performant function\\n\\nSubmit\\n3\\\\. Content collections uses TypeScript . . .\\n\\n1\\\\. To make me feel bad\\n2\\\\. To understand and validate my collections, and to provide editor tooling\\n3\\\\. Only if I have the `strictest` configuration set in `tsconfig.json`\\n\\nSubmit\\n\\nThe steps below show you how to extend the final product of the Build a Blog tutorial by creating a content collection for the blog posts.\\n\\n### Upgrade dependencies\\n\\nUpgrade to the latest version of Astro, and upgrade all integrations to their latest versions by running the following commands in your terminal:\\n\\n-\\n-\\n-\\n\\n#### npm\\n\\nTerminal window\\n\\n```\\n Upgrade Astro and official integrations togethernpx @astrojs/upgrade\\n```\\n\\n#### pnpm\\n\\nTerminal window\\n\\n```\\n Upgrade Astro and official integrations togetherpnpm dlx @astrojs/upgrade\\n```\\n\\n#### Yarn\\n\\nTerminal window\\n\\n```\\n Upgrade Astro and official integrations togetheryarn dlx @astrojs/upgrade\\n```\",\n \"source_url\": \"https://docs.astro.build/en/tutorial/6-islands/4/#_top\",\n \"title\": \"Optional: Make a content collection|Optional: Make a content collection\",\n \"source_type\": \"Astro Docs\"\n },\n {\n \"content\": \"# En > Tutorial > 6-islands > Optional: Make a content collection\\n## Create a collection for your posts\\n\\n1. Create a new **collection** (folder) called `src/blog/`.\\n1. Move all your existing blog posts (`.md` files) from `src/pages/posts/` into this new collection.\\n1. Create a `src/content.config.ts` file to [define a schema](https://docs.astro.build/en/guides/content-collections/#defining-the-collection-schema) for your `postsCollection`. For the existing blog tutorial code, add the following contents to the file to define all the frontmatter properties used in its blog posts:\\n\\nsrc/content.config.ts\\n\\n```\\n// Import the glob loaderimport { glob } from \\\"astro/loaders\\\";// Import utilities from `astro:content`import { defineCollection } from \\\"astro:content\\\";// Import Zodimport { z } from \\\"astro/zod\\\";// Define a `loader` and `schema` for each collectionconst blog = defineCollection({ loader: glob({ pattern: '**/[^_]*.md', base: \\\"./src/blog\\\" }), schema: z.object({ title: z.string(), pubDate: z.date(), description: z.string(), author: z.string(), image: z.object({ url: z.string(), alt: z.string() }), tags: z.array(z.string()) })});// Export a single `collections` object to register your collection(s)export const collections = { blog };\\n```\\n\\n4. In order for Astro to recognize your schema, quit (`CTRL + C`) and restart the dev server to continue with the tutorial. This will define the `astro:content` module.\",\n \"source_url\": \"https://docs.astro.build/en/tutorial/6-islands/4/#create-a-collection-for-your-posts\",\n \"title\": \"Optional: Make a content collection|Create a collection for your posts\",\n \"source_type\": \"Astro Docs\"\n },\n {\n \"content\": \"# En > Reference > Modules > Content Collections API Reference > Imports from `astro:content`\\n## `defineLiveCollection()`\\n\\n**Type:** `(config: LiveCollectionConfig) => LiveCollectionConfig`\\n\\n**Added in:**\\n`astro@6.0.0`\\n\\nA utility to configure a live collection in a `src/live.config.*` file.\\n\\nsrc/live.config.ts\\n\\n```\\nimport { defineLiveCollection } from 'astro:content';import { storeLoader } from '@example/astro-loader';\\nconst products = defineLiveCollection({ loader: storeLoader({ apiKey: process.env.STORE_API_KEY, endpoint: 'https://api.example.com/v1', }),});\\n// Expose your defined collection to Astro// with the `collections` exportexport const collections = { products };\\n```\\n\\nThis function accepts the following properties:\\n\\n##### `loader`\\n\\n**Type:** `LiveLoader`\\n\\n**Added in:**\\n`astro@6.0.0`\\n\\nAn object that allows you to load data at runtime from a remote source into a live content collection. (For build-time collections, see the [build-time `loader`](https://docs.astro.build/en/reference/modules/astro-content/#loader) property.)\\n\\nLearn how to [create a live loader](https://docs.astro.build/en/guides/content-collections/#creating-a-live-loader) with guided explanations and example usage.\\n\\n##### `schema`\\n\\n**Type:** `ZodType`\\n\\n**Added in:**\\n`astro@6.0.0`\\n\\nAn optional Zod object to configure the type and shape of your data for a live collection. Each value must use [a Zod validator](https://github.com/colinhacks/zod). (For build-time collections, see the [build-time `schema`](https://docs.astro.build/en/reference/modules/astro-content/#schema) property.)\\n\\nWhen you define a schema, it will take precedence over the [live loader’s types](https://docs.astro.build/en/reference/content-loader-reference/#live-loader-api) when you query the collection.\\n\\nLearn about [using Zod schemas with live collections](https://docs.astro.build/en/guides/content-collections/#using-zod-schemas-with-live-collections) through guided explanations and usage examples.\",\n \"source_url\": \"https://docs.astro.build/en/reference/modules/astro-content/#definelivecollection\",\n \"title\": \"Content Collections API Reference|`defineLiveCollection()`\",\n \"source_type\": \"Astro Docs\"\n },\n {\n \"content\": \"# En > Guides > Content collections\\n## Defining build-time content collections\\n\\nAll of your build-time content collections are defined in a special `src/content.config.ts` file (`.js` and `.mjs` extensions are also supported) using `defineCollection()`, and then a single collections object is exported for use in your project.\\n\\nEach individual collection configures:\\n\\n- [a build-time `loader`](https://docs.astro.build/en/guides/content-collections/#build-time-collection-loaders) for a data source (required)\\n- [a build-time `schema`](https://docs.astro.build/en/guides/content-collections/#defining-the-collection-schema) for type safety (optional, but highly recommended!)\\n\\nsrc/content.config.ts\\n\\n```\\n// 1. Import utilities from `astro:content`import { defineCollection } from 'astro:content';\\n// 2. Import loader(s)import { glob, file } from 'astro/loaders';\\n// 3. Import Zodimport { z } from 'astro/zod';\\n// 4. Define a `loader` and `schema` for each collectionconst blog = defineCollection({ loader: glob({ base: './src/content/blog', pattern: '**/*.{md,mdx}' }), schema: z.object({ title: z.string(), description: z.string(), pubDate: z.coerce.date(), updatedDate: z.coerce.date().optional(), }),});\\n// 5. Export a single `collections` object to register your collection(s)export const collections = { blog };\\n```\\n\\nYou can then use the dedicated `getCollection()` and `getEntry()` functions to [query your content collections data](https://docs.astro.build/en/guides/content-collections/#querying-build-time-collections) and render your content.\\n\\nYou can choose to [generate page routes](https://docs.astro.build/en/guides/content-collections/#generating-routes-from-content) from your build-time collection entries at build time for an entirely static, prerendered site. Or, you can render your build-time collections on demand, choosing to delay building your page until it is first requested. This is useful when you have a large number of pages (e.g. thousands or tens of thousands) and want to delay building a static page until it is needed.\",\n \"source_url\": \"https://docs.astro.build/en/guides/content-collections/#defining-build-time-content-collections\",\n \"title\": \"Content collections|Defining build-time content collections\",\n \"source_type\": \"Astro Docs\"\n },\n {\n \"content\": \"# En > Guides > Content collections > Live content collections\\n## Using Zod schemas with live collections\\n\\nYou can use Zod schemas with live collections to validate and transform data at runtime. This Zod validation works the same way as [schemas for build-time collections](https://docs.astro.build/en/guides/content-collections/#defining-the-collection-schema).\\n\\nWhen you define a schema for a live collection, it takes precedence over [the live loader’s types](https://docs.astro.build/en/reference/content-loader-reference/#the-liveloader-object) when you query the collection:\\n\\nsrc/live.config.ts\\n\\n```\\nimport { defineLiveCollection } from 'astro:content';import { z } from 'astro/zod';import { apiLoader } from './loaders/api-loader';\\nconst products = defineLiveCollection({ loader: apiLoader({ endpoint: process.env.API_URL }), schema: z .object({ id: z.string(), name: z.string(), price: z.number(), // Transform the API's category format category: z.string().transform((str) => str.toLowerCase().replace(/\\\\s+/g, '-')), // Coerce the date to a Date object createdAt: z.coerce.date(), }) .transform((data) => ({ ...data, // Add a formatted price field displayPrice: `$${data.price.toFixed(2)}`, })),});\\nexport const collections = { products };\\n```\\n\\nWhen using Zod schemas with live collections, validation errors are automatically caught and returned as `AstroError` objects:\\n\\nsrc/pages/store/index.astro\\n\\n```\\n---export const prerender = false; // Not needed in 'server' mode\\nimport { LiveCollectionValidationError } from 'astro/content/runtime';import { getLiveEntry } from 'astro:content';\\nconst { entry, error } = await getLiveEntry('products', '123');\\n// You can handle validation errors specificallyif (LiveCollectionValidationError.is(error)) { console.error(error.message); return Astro.rewrite('/500');}\\n// TypeScript knows entry.data matches your Zod schema, not the loader's typeconsole.log(entry?.data.displayPrice); // e.g., \\\"$29.99\\\"---\\n```\\n\\nSee [Zod’s README](https://github.com/colinhacks/zod) for complete documentation on how Zod works and what features are available.\",\n \"source_url\": \"https://docs.astro.build/en/guides/content-collections/#using-zod-schemas-with-live-collections\",\n \"title\": \"Content collections|Using Zod schemas with live collections\",\n \"source_type\": \"Astro Docs\"\n },\n {\n \"content\": \"# En > Guides > Content collections\\n## Live content collections\\n\\nLive collections use a different API than build-time content collections, although the configuration and helper functions are designed to feel familiar.\\n\\nKey differences include:\\n\\n1. **Execution time**: Run at request time instead of build time\\n1. **Configuration file**: Use `src/live.config.ts` instead of `src/content.config.ts`\\n1. **Collection definition**: Use `defineLiveCollection()` instead of `defineCollection()`\\n1. **Loader API**: Implement `loadCollection` and `loadEntry` methods instead of the `load` method\\n1. **Data return**: Return data directly instead of storing in the data store\\n1. **User-facing functions**: Use `getLiveCollection()`/`getLiveEntry()` instead of `getCollection()`/`getEntry()`\\n\\nAdditionally, you must have an adapter configured for [on-demand rendering](https://docs.astro.build/en/guides/on-demand-rendering/) of live collection data.\\n\\nDefine your live collections in the special file `src/live.config.ts` (separate from your `src/content.config.ts` for build-time collections, if you have one).\\n\\nEach individual collection configures:\\n\\n- a [live `loader`](https://docs.astro.build/en/guides/content-collections/#creating-a-live-loader) for your data source, and optionally for type safety (required)\\n- a [live collection `schema`](https://docs.astro.build/en/guides/content-collections/#using-zod-schemas-with-live-collections) for type safety (optional)\\n\\nUnlike for build-time collections, there are no built-in live loaders available. You will need to [create a custom live loader](https://docs.astro.build/en/guides/content-collections/#creating-a-live-loader) for your specific data source or find a third-party loader to pass to your live collection’s `loader` property.\\n\\nYou can optionally [include type safety in your live loaders](https://docs.astro.build/en/reference/content-loader-reference/#the-liveloader-object). Therefore, [defining a Zod `schema`](https://docs.astro.build/en/guides/content-collections/#using-zod-schemas-with-live-collections) for live collections is optional. However, if you provide one, it will take precedence over the live loader’s types.\\n\\nsrc/live.config.ts\\n\\n```\\n// Define live collections for accessing real-time dataimport { defineLiveCollection } from 'astro:content';import { storeLoader } from '@mystore/astro-loader';\\nconst products = defineLiveCollection({ loader: storeLoader({ apiKey: process.env.STORE_API_KEY, endpoint: 'https://api.mystore.com/v1', }),});\\n// Export a single `collections` object to register your collection(s)export const collections = { products };\\n```\\n\\nYou can then use the dedicated `getLiveCollection()` and `getLiveEntry()` functions to [access your live data](https://docs.astro.build/en/guides/content-collections/#accessing-live-data) and render your content.\\n\\nYou can [generate page routes](https://docs.astro.build/en/guides/content-collections/#generating-routes-from-content) from your live collection entries on demand, fetching your data fresh at runtime upon each request without needing a rebuild of your site like [build-time collections](https://docs.astro.build/en/guides/content-collections/#defining-build-time-content-collections) do. This is useful when accessing live, up-to-the-moment data is more important than having your content available in a performant data storage layer that persists between site builds.\",\n \"source_url\": \"https://docs.astro.build/en/guides/content-collections/#live-content-collections\",\n \"title\": \"Content collections|Live content collections\",\n \"source_type\": \"Astro Docs\"\n },\n {\n \"content\": \"# En > Guides > Upgrade-to > Upgrade to Astro v3 > Astro v3.0 Breaking Changes\\n## Removed: `image` from `astro:content` in content collections schema\\n\\nIn Astro v2.x, the content collections API deprecated an `image` export from `astro:content` for use in your content collections schemas.\\n\\nAstro v3.0 removes this export entirely.\\n\\n##### What should I do?\\n\\nIf you are using the deprecated `image()` from `astro:content`, remove it as this no longer exists. Validate images through [the `image` helper from `schema`](https://docs.astro.build/en/guides/upgrade-to/v3/#update-content-collections-schemas) instead:\\n\\nsrc/content/config.ts\\n\\n```\\nimport { defineCollection, z, image } from \\\"astro:content\\\";import { defineCollection, z } from \\\"astro:content\\\";\\ndefineCollection({ schema: ({ image }) => z.object({ image: image(), }),});\\n```\",\n \"source_url\": \"https://docs.astro.build/en/guides/upgrade-to/v3/#removed-image-from-astrocontent-in-content-collections-schema\",\n \"title\": \"Upgrade to Astro v3|Removed: `image` from `astro:content` in content collections schema\",\n \"source_type\": \"Astro Docs\"\n },\n {\n \"content\": \"# En > Guides > Content collections > What are Content Collections?\\n## When to create a collection\\n\\nDefine your data as a collection when:\\n\\n- You have multiple files or data to organize that share the same overall structure (e.g. a directory of blog posts written in Markdown which all have the same frontmatter properties).\\n- You have existing content stored remotely, such as in a CMS, and want to take advantage of the collections helper functions instead of using `fetch()` or SDKs.\\n- You need to fetch (tens of) thousands of related pieces of data at build time, and need a querying and caching method that handles at scale.\\n\\nMuch of the benefit of using collections comes from:\\n\\n- Defining a common data shape to validate that an individual entry is “correct” or “complete”, avoiding errors in production.\\n- Content-focused APIs designed to make querying intuitive (e.g. `getCollection()` instead of `import.meta.glob()`) when importing and rendering content on your pages.\\n- Access to both built-in loaders and access to the low-level [Content Loader API](https://docs.astro.build/en/reference/content-loader-reference/) for retrieving your content. There are additionally several third-party and community-built loaders available, and you can build your own custom loader to fetch data from anywhere.\\n- Performance and scalability. Build-time content collections data can be cached between builds and is suitable for tens of thousands of content entries.\",\n \"source_url\": \"https://docs.astro.build/en/guides/content-collections/#when-to-create-a-collection\",\n \"title\": \"Content collections|When to create a collection\",\n \"source_type\": \"Astro Docs\"\n }\n ]\n}"}]},"jsonrpc":"2.0","id":3} --- 4. the link gate's shapes: HEAD https://mcp.docs.astro.build/mcp -> 405; POST {} with content-type application/json and no accept header -> 406 text/plain, body: {"jsonrpc":"2.0","error":{"code":-32000,"message":"Not Acceptable: Client must accept both application/json and text/event-stream"},"id":null} --- 5. vendor surfaces (GET, same UA), status / bytes / sha256 of raw body: 200 5879 ef7896c3f2d15db47d243539d9c2d50e76acd03c5ae21f5c58b83a8f544fb9d2 https://mcp.docs.astro.build/ 200 223031 e16c0878b3e99627b168f9be0846ecdcea86170baf16723c177312f3f7fec96b https://docs.astro.build/en/guides/build-with-ai/ 200 3342 c0128ab5f7617a3e22e20f88b60049310144472c1abda78427dc35194f045051 https://raw.githubusercontent.com/withastro/docs-mcp/main/README.md 200 3670 61ad1307a4b1a18149419572a9834a0a398ac2127e62b3fbec16311201e5deee https://raw.githubusercontent.com/withastro/docs-mcp/main/netlify/edge-functions/mcp-server.ts 200 50659 e9aecde44e19aff17047197b415627acbfa81dbc45456ed8d8fe91b1a6907caf https://astro.build/terms/ 200 46623 d1e58e7082d860bdb751ff128f18662872c8e5334b3d30d931fd5cef1d1b4977 https://astro.build/privacy/ 404 https://docs.astro.build/llms.txt (0 bytes); 302 https://astro.build/llms.txt -> https://docs.astro.build/llms.txt; 404 /llms-full.txt, /llms-small.txt on docs.astro.build 404 /.well-known/public-agents.json on astro.build (39,572-byte HTML), docs.astro.build (0 bytes), mcp.docs.astro.build (3,449-byte HTML); DoH TXT _public-agents.{astro.build,docs.astro.build,mcp.docs.astro.build}: Status 3 (NXDOMAIN) each, 12:17Z GitHub API: withastro/docs-mcp created 2025-07-11, default branch main, license field null (no LICENSE file: raw .../main/LICENSE 404), package.json "license":"MIT", version 1.0.0, deps @modelcontextprotocol/sdk, @netlify/edge-functions, fetch-to-node, zod; last commit 2025-10-25T18:57:44Z. withastro/docs: src/content/docs/en/guides/build-with-ai.mdx first commit 2025-07-16, last 2026-09-22, 18 commits. --- 6. the server source, verbatim (3,670 bytes): import { McpServer } from "@modelcontextprotocol/sdk/server/mcp.js"; import { StreamableHTTPServerTransport } from "@modelcontextprotocol/sdk/server/streamableHttp.js"; import { toFetchResponse, toReqRes } from "fetch-to-node"; import z from "zod"; import type { Config, Context } from "@netlify/edge-functions"; const apiKey = Netlify.env.get("KAPA_API_KEY"); const projectId = Netlify.env.get("KAPA_PROJECT_ID"); const integrationId = Netlify.env.get("KAPA_INTEGRATION_ID"); if (!apiKey || !projectId || !integrationId) { throw new Error( "Missing required environment variables: KAPA_API_KEY, KAPA_PROJECT_ID, or KAPA_INTEGRATION_ID" ); } interface SearchResponse { search_results: Array<{ title: string; source_url: string; content: string; source_type: string; }>; } function getServer(): McpServer { const server = new McpServer( { name: "Astro Docs server", version: "1.0.0", }, { capabilities: { logging: {}, }, } ); server.registerTool( "search_astro_docs", { title: "Search Astro Docs", description: "Search the official Astro framework docs", inputSchema: { query: z.string().describe("Search query") }, }, async ({ query }) => { if (!query) { throw new Error("Query is required"); } const result = await sendKapaRequest("search", query); return formatResponse(result); } ); return server; } async function sendKapaRequest( action: string, query: string ): Promise { const url = `https://api.kapa.ai/query/v1/projects/${projectId}/${action}/`; const response = await fetch(url, { method: "POST", headers: { "Content-Type": "application/json", "X-API-KEY": apiKey!, }, body: JSON.stringify({ query, integration_id: integrationId, }), }); if (!response.ok) { const errorText = await response.text(); console.error(`Kapa API error: ${errorText}`); return { error: "Error: Unable to fetch data from API. Please try again later.", }; } return await response.json(); } function formatResponse(data: unknown): { content: Array<{ type: "text"; text: string }>; } { return { content: [ { type: "text", text: JSON.stringify(data, null, 2), }, ], }; } // Netlify Edge Function Handler export default async function handler(req: Request) { if (req.method === "GET") { return new Response("Method Not Allowed", { status: 405, headers: { "Content-Type": "text/plain", Allow: "POST", }, }); } try { const { req: nodeReq, res: nodeRes } = toReqRes(req); const server = getServer(); const transport = new StreamableHTTPServerTransport({ sessionIdGenerator: undefined, // Stateless mode }); await server.connect(transport); // Parse request body as JSON const body = await req.json(); // Handle the request through the transport await transport.handleRequest(nodeReq, nodeRes, body); // Handle response closing nodeRes.on("close", () => { transport.close(); server.close(); }); // Convert Node.js ServerResponse back to Web API Response return toFetchResponse(nodeRes); } catch (error) { const errorMessage = error instanceof Error ? error.message : String(error); console.error("Error in MCP server:", errorMessage); return Response.json(formatResponse({ error: errorMessage }), { status: 500, }); } } export const config: Config = { path: ["/mcp"], method: ["POST", "GET"], };