Autodesk Product Help MCP
REMOTE · API.APS.AUTODESK.COM
Read official Autodesk documentation for 110+ products. No key required.
Available components
Last scanned (3 hours ago)
Scores higher than 64% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Code Search and Documentation
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security83
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability52
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 957 tokens (~478/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management30
- Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +1
- Server version: 1.0.12 → 1.0.13 functional
- “search_help_content” reworded the description of “sources” cosmetic
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 27 Oct 26 71
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://api.aps.autodesk.com/knowledge/public/v1/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| SERIALNUMBER=2401504,CN=api.aps.usa.autodesk.com,O=Autodesk\, Inc.,L=San Francisco,ST=California,C=US,2.5.4.15=#131450726976617465204f7267616e697a6174696f6e,1.3.6.1.4.1.311.60.2.1.2=#130844656c6177617265,1.3.6.1.4.1.311.60.2.1.3=#13025553 | CN=DigiCert EV RSA CA G2,O=DigiCert Inc,C=US | 12 Aug 2026 | 26 Feb 2027 | RSA 2048 | SHA256-RSA | 5c82abec86efed3ba3b1a492ec8af6b |
| SANs: api.aps.usa.autodesk.com, api.aps.aus.autodesk.com, api.aps.can.autodesk.com, developer.api.autodesk.com, api.aps.autodesk.com, api.aps.deu.autodesk.com, api.aps.gbr.autodesk.com, api.aps.ind.autodesk.com, api.aps.jpn.autodesk.com, api.aps.irl.autodesk.com | ||||||
| CN=DigiCert EV RSA CA G2,O=DigiCert Inc,C=US (CA) | CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US | 2 Jul 2020 | 2 Jul 2030 | RSA 2048 | SHA256-RSA | 1678f1fef882255d8b0a70e6b7bb220 |
| CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US (CA) | CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US | 1 Aug 2013 | 15 Jan 2038 | RSA 2048 | SHA256-RSA | 33af1e6a711a9a0bb2864b11d09fae5 |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of api.aps.autodesk.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| autodesk.com. | present | 2624 | 13 | Verified |
| api.aps.autodesk.com. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.aps.autodesk.com/knowledge/public/v1/mcp | Verified | 200 | |
| http (plaintext) | http://api.aps.autodesk.com/knowledge/public/v1/mcp | HTTPS enforced |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_available_products Get Available Products ~95
Returns the canonical Autodesk product catalog (closed set). Each item has: product_name, product_code, and release_codes. Use this to discover or validate product values for other product-scoped tools. Not required if valid product context is already available. Terminology: release_codes = the code only (e.g. 2025), not the human-readable release name (release_name, e.g. 'AutoCAD 2025').
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
search_help_content Search Help Content ~835
Search Autodesk Help/Support documentation and return the most relevant documents for a user question. Use when: - The user asks how to do something in an Autodesk product. - The user reports an error (include the exact error text/code in the query). - The user needs official troubleshooting steps or reference documentation. Call shape (recommended): - Always pass: `query`, `locale`. - If your agent has a default product context, pass it directly via `product_code` (preferred) or `product_name`. - Pass `release_code` only when you can validate it for that product. Behavior: 1) Locale: - Read `locale` from your current context. Do not guess locale. - Pass that locale as the `locale` parameter. 2) Product and release filters (best-effort): - If your agent already has a default `product_code` or `product_name`, pass it directly. - Only call `get_available_products` to validate/normalize when: a) product is missing/unknown in context, OR b) the user explicitly specifies a product that may differ from your default, OR c) you have a `release_code` that may not be valid for the product, OR d) the product/release value appears malformed or not an allowed enum/value. - If you cannot confidently map to an exact allowed value from `get_available_products`, omit that field rather than guessing. - If both `product_name` and `product_code` are present, they must refer to the same product; `product_code` takes precedence. 3) Query construction: - Make the query keyword-rich: include product + feature/task nouns. - Include exact error text/codes when relevant. - Use the user's wording where possible. - Do not include secrets, credentials, or personal data. Returns: - Up to `max_results` documents sorted by relevance. Each item includes title, url, locale, body, media_type, source (and may include internal IDs for debugging/deduplication).
| Name | Type | Req | Description |
|---|---|---|---|
| locale | string | yes | Required. Locale used to scope search/results (language/region). Use the locale from context (do not guess). |
| max_results | – | – | Optional. Maximum number of results to return. Default is 5. Maximum allowed is 50. |
| product_code | – | – | Optional. Product code filter (preferred). First check your context for product_code, then call `get_available_products` to validate/normalize it. Use only the exact product_code returned by `get_ava… |
| product_name | – | – | Optional. Product name filter. First check your context for a product name, then call `get_available_products` to validate/normalize it. Use only the exact `product_name` returned by `get_available_p… |
| query | string | yes | Required. Keyword-rich search text. Include product + task/feature, and exact error codes/messages when relevant. Use the user's wording when possible. Write the query in the same language as `locale… |
| release_code | – | – | Optional. Product-specific release identifier (often looks like a year, but may be alphanumeric/variant). First check your context for a release, then call `get_available_products` to validate/normal… |
| sources | array | – | Restrict which sources to search. Defaults to all sources on this deployment when omitted. sfdc_articles: support/knowledge-base articles. product_documentation: official product documentation. aps_a… |
| Name | Type | Req | Description |
|---|---|---|---|
| results | array | yes | List of search results. |
| total_results | integer | yes | Total number of results found. |
No examples provided.
How do I install the Autodesk Product Help MCP server?
Autodesk Product Help MCP is a hosted endpoint at https://api.aps.autodesk.com/knowledge/public/v1/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · api.aps.autodesk.com
claude mcp add --transport http com-autodesk-aps-api-product-help-mcp 'https://api.aps.autodesk.com/knowledge/public/v1/mcp'
What is the Autodesk Product Help MCP server?
Autodesk Product Help MCP is listed in the public MCP registry as com.autodesk.aps.api/product-help-mcp. Read official Autodesk documentation for 110+ products. No key required. This page covers its hosted endpoint (https://api.aps.autodesk.com/knowledge/public/v1/mcp).
Is the Autodesk Product Help MCP server safe to use?
Autodesk Product Help MCP scores 75 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Autodesk Product Help MCP server expose?
Autodesk Product Help MCP exposes 2 tools: get_available_products, search_help_content. Their descriptions and schemas cost roughly 930 tokens of context every time the server is loaded.
Does the Autodesk Product Help MCP server require authentication?
No. We connected to Autodesk Product Help MCP without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Autodesk Product Help MCP server still maintained?
Autodesk Product Help MCP is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.