Poldex

io.github.lordolamiPublished by GitHub account lordolamiv0.0.3Updated Oct 24, 2026

MCP server exposing PolDex commercial insurance extraction tools to AI agents.

VerifiedSTDIODesktop onlyBusiness & Commerce

Overview

AI-generated overview

Poldex is a local MCP server that gives AI assistants tools for commercial insurance extraction through the PolDex API.

What you can do
Expose PolDex commercial insurance extraction capabilities to an assistant as MCP tools, covering credit, estimate, extraction, job, batch, connector event and download operations. Check available credit and get estimates before running extractions. Submit and manage extraction jobs, including batch runs. Handle connector events and download results.
When to use it
Useful when an assistant needs to run or manage commercial insurance document extraction through PolDex, including batch jobs and result downloads, rather than doing it manually in the PolDex interface.
Requirements
Runs as a local process via the npm package @poldex/mcp-server over stdio, so Node.js is needed. Requires a PolDex API key in the POLDEX_API_KEY environment variable. Optionally set POLDEX_API_BASE_URL; it defaults to the production Cloudflare API. Network access to the PolDex API is required.
Before you install
The API key in POLDEX_API_KEY is a secret and should be kept out of logs and shared configuration. Extraction, estimate, job, batch and download tools act on a PolDex account and may consume credits or incur charges; check credit and estimates first. Jobs and batches change server-side state, and extracted insurance data is sent to the PolDex API.

Installation

In SourceWeft

  1. Open Poldex in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.0.3LatestSep 16, 2026

Score

25% 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 days25 pts

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

  • Auth declared10 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
  • Documentation15 pts

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

  • License10 pts

    Declare a license in the repository or the registry entry.