io.github.RECERQA/rq-scan
NPM · RQ-SCAN-MCP
MCP Server for RQ-SCAN - AI-powered document OCR and data extraction platform
Available components
Last scanned (5 hours ago)
Scores higher than 50% of npm servers
Category Documents and Files
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security80
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 39 of 102 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency18
- Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 288 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability86
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1220 tokens (~87/item across 14 items; 13 tools + 1 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
- Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 13 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 14 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Nov 26 −1
- Stability: pass → 0.93 functional
- 29 Oct 26 0
- Stability: 0.97 → pass security
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Oct 26 −1
- Stability: pass → 0.93 functional
- 24 Oct 26 −5
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: partial → fail ▼ security
- CVE-2024-22363 no longer affects this package ▲ security
- CVE-2023-30533 no longer affects this package ▲ security
- 21 Oct 26 0
- Stability: 0.97 → pass security
- 20 Oct 26 0
- Stability: pass → 0.97 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/rq-scan-mcp@1.2.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 3 findings
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-4r6h-8v6p-xvw6 | CVE-2023-30533 | high | CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H | no |
| GHSA-5pgg-2g8v-p4x9 | CVE-2024-22363 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | no |
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 102 packages
| Packages resolved | 102 |
|---|---|
| Stale | 39 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
create_format_rule ~254
ワークフローのスキャン設定（FormatRule）を作成または更新します。抽出したい項目を定義します。 **重要な制限事項**: - 項目名: 最大50文字 - 項目のdescription: 最大500文字 - ルールのdescription: 最大500文字 これらの制限を超えると、画面からのチューニングができなくなります。
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | 設定の説明（最大500文字） |
| format_rule_name | string | yes | スキャン設定の名前（例: "請求書スキャン設定"） |
| items | array | yes | 抽出する項目のリスト |
| llm_model_type | string | – | 使用するLLMモデル（デフォルト: "claude"） |
| ocr_provider | string | – | 使用するOCRプロバイダー（デフォルト: "azure"） |
| use_llm | boolean | – | LLMを使用してデータを抽出するか（デフォルト: true） |
| workflow_id | string | yes | ワークフローのID（UUID形式） |
No output schema declared.
No examples provided.
create_upload_set ~86
ファイルをアップロードするためのアップロードセット（バッチ）を作成します。ファイルをアップロードする前に必ず作成してください。
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | アップロードセットの名前（例: "2025年1月請求書"） |
| workflow_id | string | yes | ワークフローのID（UUID形式） |
No output schema declared.
No examples provided.
create_workflow ~104
新しいワークフローを作成します。ワークフローはOCR処理やドキュメント仕分けの設定単位です。
| Name | Type | Req | Description |
|---|---|---|---|
| workflow_name | string | yes | ワークフローの名前（例: "請求書スキャン", "契約書仕分け"） |
| workflow_type | string | yes | ワークフローの種類（ocr: OCR処理, sorting: ドキュメント仕分け） |
No output schema declared.
No examples provided.
enqueue_image_files ~111
複数のローカルファイルをアップロードセットに一括でアップロードします。ファイルパスのリストを指定してください。対応形式: PDF, JPEG, PNG
| Name | Type | Req | Description |
|---|---|---|---|
| file_paths | array | yes | アップロードするファイルの絶対パスのリスト（例: ["/path/to/invoice1.pdf", "/path/to/invoice2.pdf"]） |
| upload_set_id | string | yes | アップロードセットのID（UUID形式） |
No output schema declared.
No examples provided.
export_csv ~108
抽出結果をCSV形式で取得します。プレビュー表示またはファイル保存が選択できます。
| Name | Type | Req | Description |
|---|---|---|---|
| preview_lines | number | – | プレビュー表示する行数（デフォルト: 20）。0を指定すると全量をファイルに保存します。 |
| save_path | string | – | CSVを保存するファイルパス（preview_lines=0の場合に使用） |
| upload_set_id | string | yes | アップロードセットのID（UUID形式） |
No output schema declared.
No examples provided.
get_format_rule ~59
ワークフローの最新スキャン設定（FormatRule）を取得します。設定されている抽出項目やLLM設定を確認できます。
| Name | Type | Req | Description |
|---|---|---|---|
| workflow_id | string | yes | ワークフローのID（UUID形式） |
No output schema declared.
No examples provided.
get_processing_status ~57
アップロードセットの処理ステータスを確認します。OCR処理の進捗状況やエラーを確認できます。
| Name | Type | Req | Description |
|---|---|---|---|
| upload_set_id | string | yes | アップロードセットのID（UUID形式） |
No output schema declared.
No examples provided.
get_results ~77
抽出結果のサマリーとプレビューを表示します。全データが必要な場合は export_csv を使用してください。
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | 表示するページ数の上限（デフォルト: 3） |
| upload_set_id | string | yes | アップロードセットのID（UUID形式） |
No output schema declared.
No examples provided.
get_workflow ~60
指定したワークフローの詳細情報を取得します。LLM設定、OCR設定、スキャン項目などの情報が含まれます。
| Name | Type | Req | Description |
|---|---|---|---|
| workflow_id | string | yes | ワークフローのID（UUID形式） |
No output schema declared.
No examples provided.
list_format_rules ~61
ワークフローのスキャン設定（FormatRule）履歴一覧を取得します。リビジョン管理されている過去の設定を確認できます。
| Name | Type | Req | Description |
|---|---|---|---|
| workflow_id | string | yes | ワークフローのID（UUID形式） |
No output schema declared.
No examples provided.
list_workflows ~50
RQ-SCANに登録されているワークフローの一覧を取得します。ワークフローはOCR処理やドキュメント仕分けの設定単位です。
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
start_processing ~64
アップロードしたファイルのAI処理（データ抽出）を開始します。ファイルアップロード後、OCR処理が完了したら実行してください。
| Name | Type | Req | Description |
|---|---|---|---|
| upload_set_id | string | yes | アップロードセットのID（UUID形式） |
No output schema declared.
No examples provided.
upload_file ~102
ローカルファイルをアップロードセットにアップロードします。ファイルパスを指定するだけで、自動的にファイルを読み込んでアップロードします。対応形式: PDF, JPEG, PNG
| Name | Type | Req | Description |
|---|---|---|---|
| file_path | string | yes | アップロードするファイルの絶対パス（例: "/path/to/invoice.pdf"） |
| upload_set_id | string | yes | アップロードセットのID（UUID形式） |
No output schema declared.
No examples provided.
How do I install the io.github.RECERQA/rq-scan MCP server?
io.github.RECERQA/rq-scan runs locally as an npm package, launched with npx -y rq-scan-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · rq-scan-mcp
claude mcp add recerqa-rq-scan -- npx -y rq-scan-mcp
What is the io.github.RECERQA/rq-scan MCP server?
io.github.RECERQA/rq-scan is an MCP server listed in the public MCP registry as io.github.RECERQA/rq-scan. MCP Server for RQ-SCAN - AI-powered document OCR and data extraction platform. This page covers its npm package (rq-scan-mcp).
Is the io.github.RECERQA/rq-scan MCP server safe to use?
io.github.RECERQA/rq-scan scores 75 out of 100 on VerifyMCP. We recorded 3 known advisories against it as of 5 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.RECERQA/rq-scan MCP server expose?
io.github.RECERQA/rq-scan exposes 13 tools: list_workflows, get_workflow, create_workflow, create_upload_set, upload_file, and 8 more. Their descriptions and schemas cost roughly 1,193 tokens of context every time the server is loaded.
Is the io.github.RECERQA/rq-scan MCP server still maintained?
io.github.RECERQA/rq-scan is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.RECERQA/rq-scan MCP server under?
io.github.RECERQA/rq-scan declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.