Server data from the Official MCP Registry
Parse a document into structured, confidence-scored fields. Bring your own model, pay per scan.
Parse a document into structured, confidence-scored fields. Bring your own model, pay per scan.
This is a well-structured MCP server that wraps the ParseRelay document scanning API. Authentication is properly required via API keys (environment variables or Bearer tokens), input validation is thorough with Zod schemas, and error handling is appropriate. The codebase is clean with no malicious patterns, hardcoded secrets, or dangerous operations. Minor code quality observations exist but do not materially impact security. Supply chain analysis found 5 known vulnerabilities in dependencies (2 critical, 3 high severity). Package verification found 1 issue.
7 files analyzed · 10 issues found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
This plugin requests these system permissions. Most are normal for its category.
Set these up before or after installing:
Environment variable: PARSERELAY_API_KEY
Environment variable: PARSERELAY_BASE_URL
Add this to your MCP configuration file:
{
"mcpServers": {
"io-github-parserelay-mcp": {
"env": {
"PARSERELAY_API_KEY": "your-parserelay-api-key-here",
"PARSERELAY_BASE_URL": "your-parserelay-base-url-here"
},
"args": [
"-y",
"@parserelay/mcp"
],
"command": "npx"
}
}
}From the project's GitHub README.
ParseRelay's scan operation as an MCP tool — so any
MCP host (Claude Desktop, Cursor, …) can parse a document into structured, confidence-scored
fields. Same contract as the REST API and the <DeadSimpleMicroScanner> component; one tool,
scan.
scan toolInput mirrors the sync ScanRequest — image (required), plus
schema, doc_type, engine, ocr, dry_run, model, model_key. (relay webhooks are
omitted: a tool call is synchronous, so you get the envelope back inline.) The result is the
full ScanEnvelope as JSON: fields, per-field confidence,
needs_review, field_source, and meta (engine, credits, tokens).
Set dry_run: true to preview which fields would trigger a paid rescue — and the estimated
credits — without spending anything.
{
"mcpServers": {
"parserelay": {
"command": "npx",
"args": ["-y", "@parserelay/mcp"],
"env": {
"PARSERELAY_API_KEY": "your-key",
"PARSERELAY_BASE_URL": "https://api.parserelay.app" // optional
}
}
}
}
PARSERELAY_API_KEY=your-key PORT=8080 node node_modules/@parserelay/mcp/dist/http.js
# → POST http://localhost:8080/mcp
Stateless: a fresh server per request, so it scales horizontally. Auth per request via
Authorization: Bearer <key>, falling back to PARSERELAY_API_KEY for single-tenant setups.
import { createMcpServer } from "@parserelay/mcp";
import { ParseRelayClient } from "@parserelay/client";
const server = createMcpServer(new ParseRelayClient({ apiKey }));
// then wire your own transport: await server.connect(transport)
| Env var | Required | Default | Notes |
|---|---|---|---|
PARSERELAY_API_KEY | stdio: yes | — | HTTP can override per request via Authorization: Bearer. |
PARSERELAY_BASE_URL | no | https://api.parserelay.app | Point at a local worker for testing. |
PORT | no | 8080 | HTTP transport only. |
Be the first to review this server!
by Modelcontextprotocol · Developer Tools
Web content fetching and conversion for efficient LLM usage
by Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.
by mcp-marketplace · Developer Tools
Create, build, and publish Python MCP servers to PyPI — conversationally.