io.github.IntelagentStudios/mcp-file-processor
NPM · @INTELAGENT/MCP-FILE-PROCESSOR · SCANNED SEP 24
Text extraction, keyword extraction, language detection, and chunking for RAG
Available components
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 Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 49 of 123 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: the declared repository URL redirects; it must resolve directly. 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 192 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
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 540 tokens (~77/item across 7 items; 6 tools + 1 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management80
- Stability observed for 24 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 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
How do I install the io.github.IntelagentStudios/mcp-file-processor server?
io.github.IntelagentStudios/mcp-file-processor runs locally as an npm package, launched with npx -y @intelagent/mcp-file-processor. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @intelagent/mcp-file-processor
claude mcp add intelagentstudios-mcp-file-processor -- npx -y @intelagent/mcp-file-processor
{
"mcpServers": {
"intelagentstudios-mcp-file-processor": {
"command": "npx",
"args": [
"-y",
"@intelagent/mcp-file-processor"
]
}
}
} {
"servers": {
"intelagentstudios-mcp-file-processor": {
"command": "npx",
"args": [
"-y",
"@intelagent/mcp-file-processor"
]
}
}
} codex mcp add intelagentstudios-mcp-file-processor -- npx -y @intelagent/mcp-file-processor
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"intelagentstudios-mcp-file-processor": {
"type": "local",
"command": [
"npx",
"-y",
"@intelagent/mcp-file-processor"
],
"enabled": true
}
}
} openclaw mcp add intelagentstudios-mcp-file-processor --command npx --arg -y --arg @intelagent/mcp-file-processor
mcp_servers:
intelagentstudios-mcp-file-processor:
command: "npx"
args: ["-y", "@intelagent/mcp-file-processor"] {
"McpServers": {
"intelagentstudios-mcp-file-processor": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@intelagent/mcp-file-processor"
]
}
}
} assistant mcp add intelagentstudios-mcp-file-processor -t stdio -c npx -a -y @intelagent/mcp-file-processor
{
"mcpServers": {
"intelagentstudios-mcp-file-processor": {
"command": "npx",
"args": [
"-y",
"@intelagent/mcp-file-processor"
]
}
}
} 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.
- 24 Sept 26 −3
- Stability: pass → 0.80 functional
- 23 Sept 26 +1
- Stability: 0.97 → pass security
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 −3
- Stability: pass → 0.80 functional
- 16 Sept 26 +1
- Stability: 0.97 → pass security
- 14 Sept 26 +1
- Security disclosure: unverified → fail ▼ functional
- 13 Sept 26 0
- Security disclosure: fail → unverified ▼ 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 24 Sept 2026 · Analysed npm/@intelagent/mcp-file-processor@0.1.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 →
Dependencies 123 packages
| Packages resolved | 123 |
|---|---|
| Stale | 49 |
| 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 →
chunk_text ~83
Split text into overlapping chunks suitable for RAG/embedding pipelines. Configurable chunk size and overlap. Returns chunks with positional metadata.
| Name | Type | Req | Description |
|---|---|---|---|
| chunkSize | number | – | Target chunk size in characters (default: 1000) |
| overlap | number | – | Overlap between chunks in characters (default: 200) |
| text | string | yes | Text to split into chunks |
No output schema declared.
No examples provided.
detect_language ~72
Detect whether content is code, natural language, or mixed. Optionally detects the programming language from file extension. Useful for routing content to appropriate processing pipelines.
| Name | Type | Req | Description |
|---|---|---|---|
| fileName | string | – | Optional file name for extension-based detection (e.g. "app.ts") |
| text | string | yes | Text content to analyse |
No output schema declared.
No examples provided.
extract_keywords ~61
Extract ranked keywords from text. Returns keywords sorted by frequency, useful for tagging, search indexing, and topic identification.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Maximum number of keywords to return (default: 20) |
| text | string | yes | Text to extract keywords from |
No output schema declared.
No examples provided.
extract_text ~129
Extract text content from a file. Supports PDF, DOCX, CSV, JSON, Markdown, HTML, and code files. Pass file content as base64 (for binary formats like PDF/DOCX) or raw text (for text formats). Returns extracted text, word count, and processing time.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | File content — base64-encoded for binary formats (PDF, DOCX), raw text for text formats |
| fileType | string | yes | MIME type (e.g. "application/pdf") or file extension (e.g. ".pdf", "pdf", ".ts") |
No output schema declared.
No examples provided.
process_file ~149
All-in-one file processing: extract text, detect content type, extract keywords, and chunk for RAG. Returns the complete processed result in a single call.
| Name | Type | Req | Description |
|---|---|---|---|
| chunkOverlap | number | – | Overlap between chunks in characters (default: 200) |
| chunkSize | number | – | Target chunk size in characters (default: 1000) |
| content | string | yes | File content — base64-encoded for binary formats (PDF, DOCX), raw text for text formats |
| fileType | string | yes | MIME type or file extension (e.g. "application/pdf", ".md", "csv") |
| keywordLimit | number | – | Maximum keywords to extract (default: 20) |
No output schema declared.
No examples provided.
server_info ~31
Returns server metadata: name, version, registered tools, and registered resources. Useful for introspection and health checks.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the io.github.IntelagentStudios/mcp-file-processor server?
io.github.IntelagentStudios/mcp-file-processor is listed in the public MCP registry as io.github.IntelagentStudios/mcp-file-processor. Text extraction, keyword extraction, language detection, and chunking for RAG. This page covers its npm package (@intelagent/mcp-file-processor).
Is the io.github.IntelagentStudios/mcp-file-processor server safe to use?
io.github.IntelagentStudios/mcp-file-processor scores 78 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 24 September 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.IntelagentStudios/mcp-file-processor server expose?
io.github.IntelagentStudios/mcp-file-processor exposes 6 tools: extract_text, extract_keywords, detect_language, chunk_text, process_file, server_info. Their descriptions and schemas cost roughly 525 tokens of context every time the server is loaded.
Is the io.github.IntelagentStudios/mcp-file-processor server still maintained?
io.github.IntelagentStudios/mcp-file-processor is still listed as active in the MCP registry. We last reached this channel on 24 September 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.IntelagentStudios/mcp-file-processor server under?
io.github.IntelagentStudios/mcp-file-processor declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.