Dedox
REMOTE · API.DEDOX.AI
Gives AI assistants read access to your Dedox help centre and knowledge base articles.
Available components
Last scanned (9 hours ago)
Scores higher than 68% of remote servers
Reachable. Last reached 6 Nov 2026.
Category Documents and Files
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 Security89
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token. See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability68
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1293 tokens (~53/item across 24 items; 24 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 4 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 24 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 5 Nov 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 4 Nov 26 +1
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 3 Nov 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 2 Nov 26 +1
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 1 Nov 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 31 Oct 26 +4
- Stability: unverified → 0.03 ▲ functional
- Destructive annotations: All 4 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation. functional
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 30 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 6 Nov 2026 · Probed https://api.dedox.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=dedox.ai | CN=WE1,O=Google Trust Services,C=US | 26 Oct 2026 | 24 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 95021eae6c5a9ef13a38dca4ea5121c |
| SANs: dedox.ai, *.dedox.ai | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.dedox.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | DS published | 1814, 3799 | 8, 8 | Verified |
| dedox.ai. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=15552000; includeSubDomains |
| content-security-policy | default-src 'self';base-uri 'self';font-src 'self' https: data:;form-action 'self';frame-ancestors 'self';img-src 'self' data:;object-src 'none';script-src 'self';script-src-attr 'none';style-src 'self' https: 'unsafe-inline';upgrade-insecure-requests |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | no-referrer |
Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | No resource metadata |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.dedox.ai/mcp | Verified | 200 | |
| http (plaintext) | http://api.dedox.ai/mcp | HTTPS enforced | 301 | https://api.dedox.ai/mcp |
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 →
approve_comment Approve comment ~32
Approve a pending comment on an article so it is shown publicly
| Name | Type | Req | Description |
|---|---|---|---|
| commentId | string | yes | Comment ID |
No output schema declared.
No examples provided.
create_article Create article ~161
Create a new article in a knowledge base
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Article category |
| content | string | yes | Article content (Markdown format, will be converted to HTML) |
| excerpt | string | – | Short description or excerpt (max 500 characters) |
| knowledgeBaseId | string | yes | Knowledge base ID |
| seo | object | – | SEO metadata object with optional fields: metaTitle (max 60 chars), metaDescription (max 160 chars), keywords (array of strings or comma-separated string) |
| slug | string | – | URL slug (auto-generated from title if not provided) |
| status | string | – | Article status (default: draft) |
| tags | array | – | Array of tag strings |
| title | string | yes | Article title |
No output schema declared.
No examples provided.
create_category Create category ~51
Create a new category in a knowledge base. It is listed straight away, including before an article uses it.
| Name | Type | Req | Description |
|---|---|---|---|
| knowledgeBaseId | string | yes | Knowledge base ID |
| name | string | yes | Category name |
No output schema declared.
No examples provided.
create_knowledge_base Create knowledge base ~62
Create a new knowledge base
| Name | Type | Req | Description |
|---|---|---|---|
| branding | object | – | Branding configuration |
| name | string | yes | Knowledge base name |
| settings | object | – | Knowledge base settings |
| subdomain | string | – | Custom subdomain (auto-generated if not provided) |
No output schema declared.
No examples provided.
delete_article Delete article ~25
Delete an article (soft delete)
| Name | Type | Req | Description |
|---|---|---|---|
| articleId | string | yes | Article ID |
No output schema declared.
No examples provided.
delete_category Delete category ~49
Delete a category from a knowledge base (uncategorizes all articles with that category)
| Name | Type | Req | Description |
|---|---|---|---|
| categoryName | string | yes | Category name to delete |
| knowledgeBaseId | string | yes | Knowledge base ID |
No output schema declared.
No examples provided.
delete_comment Delete comment ~25
Delete a comment (soft delete)
| Name | Type | Req | Description |
|---|---|---|---|
| commentId | string | yes | Comment ID |
No output schema declared.
No examples provided.
delete_knowledge_base Delete knowledge base ~30
Delete a knowledge base (soft delete)
| Name | Type | Req | Description |
|---|---|---|---|
| knowledgeBaseId | string | yes | Knowledge base ID |
No output schema declared.
No examples provided.
get_article Get article ~26
Get detailed information about a specific article
| Name | Type | Req | Description |
|---|---|---|---|
| articleId | string | yes | Article ID |
No output schema declared.
No examples provided.
get_article_analytics Get article analytics ~53
Get analytics data for an article
| Name | Type | Req | Description |
|---|---|---|---|
| articleId | string | yes | Article ID |
| endDate | string | yes | End date (ISO format) |
| startDate | string | yes | Start date (ISO format) |
No output schema declared.
No examples provided.
get_article_categories List categories ~30
Get all categories used in a knowledge base
| Name | Type | Req | Description |
|---|---|---|---|
| knowledgeBaseId | string | yes | Knowledge base ID |
No output schema declared.
No examples provided.
get_article_tags List tags ~30
Get all tags used in a knowledge base
| Name | Type | Req | Description |
|---|---|---|---|
| knowledgeBaseId | string | yes | Knowledge base ID |
No output schema declared.
No examples provided.
get_knowledge_base Get knowledge base ~31
Get detailed information about a specific knowledge base
| Name | Type | Req | Description |
|---|---|---|---|
| knowledgeBaseId | string | yes | Knowledge base ID |
No output schema declared.
No examples provided.
get_knowledge_base_analytics Get knowledge base analytics ~58
Get analytics data for a knowledge base
| Name | Type | Req | Description |
|---|---|---|---|
| endDate | string | yes | End date (ISO format) |
| knowledgeBaseId | string | yes | Knowledge base ID |
| startDate | string | yes | Start date (ISO format) |
No output schema declared.
No examples provided.
list_article_versions List article versions ~26
List all versions of an article
| Name | Type | Req | Description |
|---|---|---|---|
| articleId | string | yes | Article ID |
No output schema declared.
No examples provided.
list_articles List articles ~97
List articles for a knowledge base with optional filters
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Filter by category |
| knowledgeBaseId | string | yes | Knowledge base ID |
| limit | number | – | Maximum number of results (1-100, default: 50) |
| offset | number | – | Number of results to skip (default: 0) |
| status | string | – | Filter by status |
| tags | array | – | Filter by tags |
No output schema declared.
No examples provided.
list_comments List comments ~34
List comments for an article
| Name | Type | Req | Description |
|---|---|---|---|
| articleId | string | yes | Article ID |
| status | string | – | Filter by status |
No output schema declared.
No examples provided.
list_knowledge_bases List knowledge bases ~20
List all knowledge bases owned by the user
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
reject_comment Reject comment ~32
Reject a pending comment on an article so it is not shown publicly
| Name | Type | Req | Description |
|---|---|---|---|
| commentId | string | yes | Comment ID |
No output schema declared.
No examples provided.
restore_article_version Restore article version ~39
Restore an article to a specific version
| Name | Type | Req | Description |
|---|---|---|---|
| articleId | string | yes | Article ID |
| versionNumber | number | yes | Version number to restore |
No output schema declared.
No examples provided.
search_articles Search articles ~75
Search articles using full-text search
| Name | Type | Req | Description |
|---|---|---|---|
| knowledgeBaseId | string | – | Filter by knowledge base ID |
| limit | number | – | Maximum number of results (1-100, default: 50) |
| offset | number | – | Number of results to skip (default: 0) |
| query | string | yes | Search query |
No output schema declared.
No examples provided.
update_article Update article ~182
Update an existing article. Creates a new version with a change note.
| Name | Type | Req | Description |
|---|---|---|---|
| articleId | string | yes | Article ID |
| category | string | – | Article category |
| changeNote | string | – | Optional note describing the changes made (max 500 characters). If not provided, a summary of changed fields will be generated. |
| content | string | – | Article content (Markdown format, will be converted to HTML) |
| excerpt | string | – | Article excerpt (max 500 characters) |
| seo | object | – | SEO metadata object with optional fields: metaTitle (max 60 chars), metaDescription (max 160 chars), keywords (array of strings or comma-separated string) |
| slug | string | – | URL slug |
| status | string | – | Article status |
| tags | array | – | Array of tag strings |
| title | string | – | Article title |
No output schema declared.
No examples provided.
update_category Rename category ~57
Rename a category in a knowledge base (updates all articles with that category)
| Name | Type | Req | Description |
|---|---|---|---|
| categoryName | string | yes | Current category name |
| knowledgeBaseId | string | yes | Knowledge base ID |
| newName | string | yes | New category name |
No output schema declared.
No examples provided.
update_knowledge_base Update knowledge base ~68
Update an existing knowledge base
| Name | Type | Req | Description |
|---|---|---|---|
| branding | object | – | Branding configuration |
| knowledgeBaseId | string | yes | Knowledge base ID |
| name | string | – | Knowledge base name |
| settings | object | – | Knowledge base settings |
| subdomain | string | – | Custom subdomain |
No output schema declared.
No examples provided.
How do I install the Dedox MCP server?
Dedox is a hosted endpoint at https://api.dedox.ai/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.dedox.ai
claude mcp add --transport http ai-dedox-dedox 'https://api.dedox.ai/mcp'
What is the Dedox MCP server?
Dedox is an MCP server listed in the public MCP registry as ai.dedox/dedox. Gives AI assistants read access to your Dedox help centre and knowledge base articles. This page covers its hosted endpoint (https://api.dedox.ai/mcp).
Is the Dedox MCP server safe to use?
Dedox scores 77 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 Dedox MCP server expose?
Dedox exposes 24 tools: list_articles, get_article, create_article, update_article, delete_article, and 19 more. Their descriptions and schemas cost roughly 1,293 tokens of context every time the server is loaded.
Does the Dedox MCP server require authentication?
Yes. Dedox asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the Dedox MCP server still maintained?
Dedox is still listed as active in the MCP registry. We last reached this channel on 6 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Dedox MCP server?
VerifyMCP ran 13 checks on Dedox, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.