Mervext

com.vstudiodigitalPublished by vstudiodigital.comOfficial publisherv0.1.1Updated Oct 24, 2026

Extract invoices, receipts and contracts into structured JSON. EU-hosted, per-field confidence.

VerifiedStreamable HTTPWeb executableFiles & StorageData & Analytics

Overview

AI-generated overview

Mervext turns invoices, receipts and contracts into structured JSON with per-field confidence, via a hosted, EU-hosted document extraction service.

What you can do
  • Extract a PDF, photo or text document into structured JSON using a built-in schema or your own schema JSON, with per-field confidence
  • Detect a document's type without extracting fields
  • List the built-in extraction schemas and what each one captures
  • Check plan, remaining credits and usage
  • Delete a document by id for explicit zero-retention removal
When to use it
Useful when an assistant needs to read invoices, receipts or contracts and get clean structured fields rather than raw text, for example in bookkeeping, expense or contract-review workflows that want EU-hosted processing and confidence scores.
Requirements
Remote Streamable HTTP endpoint at mcp.vstudiodigital.com, or a local Node.js build run over stdio or HTTP. A Mervext API key is required, supplied per request via the X-API-Key or Authorization Bearer header, or the MERVEKT_API_KEY environment variable for stdio. Keys come with free trial credits from the Mervext site. OAuth is declared for the hosted endpoint.
Before you install
The API key is a billable credential: extraction consumes credits, so usage can cost money and the key should be scoped and rotated. The server sends document contents to the Mervext engine at api.vstudiodigital.com, so check that this third-party processing fits your data rules. delete_document permanently removes a document by id.

Installation

In SourceWeft

  1. Open Mervext in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. 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/com.vstudiodigital%2Fmervext/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. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "mervext": {
      "type": "http",
      "url": "https://mcp.vstudiodigital.com/mcp"
    }
  }
}

README

mervext-mcp

MCP server for Mervext — documents in, structured JSON out, for AI agents (Claude, Claude Code, Codex, Cursor, Hermes, Gemini CLI, …).

Thin wrapper over the deployed Mervext engine (https://api.vstudiodigital.com). Standalone: no changes to the engine repo, no state, no stored secrets.

Hosted endpoint (live)

https://mcp.vstudiodigital.com/mcp — Streamable HTTP, stateless, on Cloudflare Workers (scale-to-zero). Health: GET /healthz.

Client config (any MCP client that supports HTTP + headers):

json
{  "mcpServers": {    "mervext": {      "type": "http",      "url": "https://mcp.vstudiodigital.com/mcp",      "headers": { "X-API-Key": "fw_…your key…" }    }  }}

The API key is supplied per request by the client — the worker stores nothing, keeps no sessions, and holds no secrets. Get a key with free trial credits at https://mervext.com, or mint a device key: POST /v1/keys/device.

Tools

ToolWhat it does
extract_documentOne document (PDF / photo / text) → structured JSON with per-field confidence. Built-in schema id or your own schema_json.
classify_documentDetect document type without extracting fields.
list_schemasThe built-in schemas (id + what each extracts).
check_balancePlan, remaining credits, usage.
delete_documentExplicit zero-retention delete by document id.

Auth

The MCP client supplies the Mervext API key; the server never stores it:

  • stdio: MERVEKT_API_KEY=fw_live_…
  • HTTP: X-API-Key: fw_… or Authorization: Bearer fw_… header per request

Run locally

bash
npm installnpm run build
# stdio (local clients)MERVEKT_API_KEY=fw_live_… node dist/stdio.js
# HTTP (local / testing)node dist/http.js            # :8787 — POST /mcp, GET /healthz

Engine base URL override: MERVEKT_API_URL (default https://api.vstudiodigital.com).

Deploy (Cloudflare Workers)

bash
npx wrangler deploy
  • wrangler.toml: worker mervext-mcp, route mcp.vstudiodigital.com/* (zone vstudiodigital.com). workers_dev is off — route only (no workers.dev subdomain on the account).
  • Run from WSL — wrangler OAuth lives there (skill: cloudflare-pages-deploys).

Smoke tests

bash
# stdio, against the live engine (1–2 credits)node scripts/mcp-smoke.ts [--image path.jpg] [--schema invoice]
# hosted worker, real Streamable-HTTP clientMERVEKT_API_KEY=… node scripts/mcp-http-smoke.ts [https://…/mcp]

Status

  • v0 — five tools, stateless HTTP + stdio, tested against the live engine
  • Hosted on Cloudflare Workers — live at mcp.vstudiodigital.com, verified end-to-end through the hosted stack: text invoice 2.1 s (confidence 1.0, source-grounded); scanned receipt without a text layer (vision path) 7.6 s; clean 422 naming valid schemas for raw images.
  • Official MCP registry: com.vstudiodigital/mervext (DNS-verified publisher)
  • Static server card at /.well-known/mcp/server-card.json (metadata for registries/scanning)
  • Smithery: contact-3yen/mervext — published
  • mcp.so / Glama (public-repo listings)

License

MIT — see LICENSE.

Not in the Mervext product repo on purpose — that repo runs its own deploy pipeline.

Source: README.md at commit e52b1ee

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v0.1.1LatestOct 9, 2026

Score

85% 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
  • Auth declaredRequired10 pts
  • 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
  • License10 pts