well-010-docx-to-text

dev.workers.mmelnyk2000.well-010-docx-to-textPublished by well-010-docx-to-text.mmelnyk2000.workers.devOfficial publisherv1.0.0Updated Oct 24, 2026

Word .docx to text and tables. x402 $0.005 USDC, Base. As is, no warranty.

VerifiedStreamable HTTPWeb executableFiles & Storage

Overview

AI-generated overview

Converts Word .docx files into plain text and tables through a remote MCP endpoint.

What you can do
This remote MCP server extracts content from Word .docx documents. According to its registry description, it returns text and tables from the uploaded file. No individual tool names or parameters are listed in the manifest.
When to use it
Use it when an assistant needs to read or process the contents of Word documents and no local conversion library is available. It may suit workflows that require extracting text and tabular data from .docx files.
Requirements
It runs as a remote streamable HTTP endpoint; no local runtime or package is needed. The registry description states a payment of $0.005 USDC on Base via x402, so a compatible crypto wallet or payment setup is required. No accounts, API keys, or headers are declared.
Before you install
The registry description states a $0.005 USDC charge on Base per use, so real money may be spent. It also says the service is provided as is with no warranty. Documents sent to the remote endpoint leave the user's machine and are processed by a third party.

Installation

In SourceWeft

  1. Open well-010-docx-to-text in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/dev.workers.mmelnyk2000.well-010-docx-to-text%2Fdocx-to-text/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "well-010-docx-to-text": {
      "type": "http",
      "url": "https://well-010-docx-to-text.mmelnyk2000.workers.dev/mcp"
    }
  }
}

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.0.0LatestOct 16, 2026

Score

17% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.