DOCX.now MCP Server
REMOTE · DOCX.NOW
Convert DOCX documents to and from PDF, TXT, HTML, ODT, JPG and RTF.
Available components
Last scanned (1 day ago)
Scores higher than 0% of remote servers
Unreachable for 7 days in a row. Last reached 28 Oct 2026.
Category Documents and Files
Dead
Every channel of this server has been unreachable for long enough to be marked dead. Its trust score is pinned to 0 and does not recover automatically: even once the server responds again it stays dead until it is manually reinstated.
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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
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.
- 4 Nov 26 −13
- HSTS header: fail → unverified ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- 3 Nov 26 −14
- HSTS header: unverified → fail ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the whole tool list to see what that exposes. security
- 2 Nov 26 −13
The score moved with no change recorded against any check. We would rather say so than guess.
- 1 Nov 26 −14
- HSTS header: fail → unverified ▼ security
- Transport: fail → pass ▲ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- 31 Oct 26 −13
- HSTS header: unverified → fail ▼ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the whole tool list to see what that exposes. security
- 29 Oct 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- HSTS header: fail → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Stability: 0.03 → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 28 Oct 26 +7
- HSTS header: unverified → fail ▼ security
- Authorization: unverified → partial ▲ security
- Stability: unverified → 0.03 ▲ functional
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 27 Oct 26 60
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 4 Nov 2026 · Probed https://docx.now/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=docx.now | CN=WE1,O=Google Trust Services,C=US | 7 Oct 2026 | 5 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 18b7f1c98f8a6e1513e2038eb1706649 |
| SANs: docx.now, *.docx.now | ||||||
| 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 docx.now. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| now. | present | 53572 | 8 | Verified |
| docx.now. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://docx.now/mcp | Unreachable | ||
| http (plaintext) | http://docx.now/mcp | HTTPS enforced | 301 | https://docx.now/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 →
convert_image_url Convert a DOCX document from a URL ~111
Download a publicly accessible DOCX or supported document URL, submit it to DOCX.now using a converter slug, and optionally wait for the result. Private-network URLs and embedded URL credentials are rejected.
| Name | Type | Req | Description |
|---|---|---|---|
| background_color | – | – | – |
| converter | string | yes | – |
| height | – | – | – |
| quality | integer | – | – |
| source_url | string | yes | – |
| strip_metadata | boolean | – | – |
| timeout_seconds | integer | – | – |
| wait_for_completion | boolean | – | – |
| width | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_api_usage Get DOCX.now API usage ~25
Return the caller's DOCX.now API credits, usage, and rate limit.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
get_conversion_status Get conversion status ~36
Check a DOCX.now conversion job. A completed job includes an absolute, temporary download URL.
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
list_converters List DOCX.now converters ~63
Search the live DOCX.now converter catalog and return valid converter slugs such as docx-to-pdf, docx-to-txt, pdf-to-docx, and odt-to-docx.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| search | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the DOCX.now MCP Server server?
DOCX.now MCP Server is a hosted endpoint at https://docx.now/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 · docx.now
claude mcp add --transport http chrisyau83-docx-now 'https://docx.now/mcp'
What is the DOCX.now MCP Server server?
DOCX.now MCP Server is listed in the public MCP registry as io.github.chrisyau83/docx-now. Convert DOCX documents to and from PDF, TXT, HTML, ODT, JPG and RTF. This page covers its hosted endpoint (https://docx.now/mcp).
Is the DOCX.now MCP Server server safe to use?
DOCX.now MCP Server scores 0 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 DOCX.now MCP Server server expose?
DOCX.now MCP Server exposes 4 tools: list_converters, convert_image_url, get_conversion_status, get_api_usage. Their descriptions and schemas cost roughly 235 tokens of context every time the server is loaded.
Does the DOCX.now MCP Server server require authentication?
Its publisher declares that DOCX.now MCP Server requires credentials, so you will need to authorise it in your MCP client. We have not been able to confirm that against the live endpoint.
Is the DOCX.now MCP Server server still maintained?
DOCX.now MCP Server has been unreachable for long enough that we treat it as dead, and its score is pinned to zero. We last reached this channel on 28 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.