flexorch-mcp
https://mcp.flexorch.com/mcp ↗
Description
Convert unstructured business documents (PDF, DOCX, invoices, contracts, payroll sheets) into structured, LLM-ready datasets with automatic classification, field extraction, PII masking, and quality scoring. **6 async tools:** - `process_document` — submit document for processing - `get_job_status` — poll until complete - `get_extraction_result` — read structured fields + quality grade - `build_dataset` — package records into a named dataset - `export_dataset` — download as JSONL, RAG, CSV, or Markdown - `search_documents` — keyword + semantic search across datasets **Requires:** FlexOrch API key — get one at [app.flexorch.com/settings](https://app.flexorch.com/settings)
What our measurements say
flexorch-mcp is a remote MCP server published at mcp.flexorch.com. It has been probed 7 times since 9/10/2026. It answered in 7 of them (100.0%), a near-uninterrupted record. Median response time is 354 ms, placing it among the faster endpoints. It offers a narrow, focused set of 9 tools. On the protocol side it still runs 2025-11-25 and has not moved to the newer spec.
Agent readability score
Can an LLM agent pick the right tool here — names, descriptions and parameter clarity are assessed.
Agent readability score
Strengths
- Tools follow a logical workflow with clear step-by-step progression (e.g., process → status → result).
- Some descriptions include usage context (e.g., 'call this after document.process').
Weaknesses
- Multiple descriptions are truncated (e.g., 'tool ret' in document.process).
- Parameter requirements and types are not explicitly defined in descriptions.
- Tool names like 'dataset.build' and 'dataset.export' may cause confusion with similar functions.
document.process— Description truncated mid-sentencejob.status— Incomplete explanation of response formatsdataset.build— Ambiguous overlap with dataset.exportdataset.search— Missing clear usage constraintsdataset.chunks— Requires Pro+ plan but no explicit warning
Verdict
Event narrative
Risk: medium
- 2026-09-10T21:16:35.016Z — Era changed from 'unknown' to 'legacy' · Server now operates in a defined, stable era with known compliance metrics
- 2026-09-11T01:59:45.474Z — Compliance score set to 100 (previously null) · Achieved full compliance status, indicating no critical configuration issues
Advice
Schema compliance
tools/list structure, inputSchema validity, and a functional smoke test — the components of the 0-100 score.
- tools/list schema valid
- inputSchema is valid JSON Schema
- Smoke test not run this round
- Cold-start: cold 59ms → warm 57ms (penalty 2ms)
Availability history
Event log
Derived by comparing consecutive probes — changes in era, protocol version, build and reachability.
- Server build: — → 1.29.1
- Supported versions: — → 2025-11-25
- Era changed: Unknown → Legacy
- Added to watch — era: Unknown
Get your badge
Add this badge to your README — it updates automatically as measurements change.
[](https://mcpmetrics.io/servers/developer-ty82-flexorch-mcp)<a href="https://mcpmetrics.io/servers/developer-ty82-flexorch-mcp"><img src="https://mcpmetrics.io/badge/developer-ty82/flexorch-mcp/era.svg" alt="mcpmetrics"></a>You are seeing the last 7 days. Sign up for the full history. Which check failed and why is in the dashboard.
Sign up free to see