Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, email [email protected] and we’ll put it right.

io.github.IntelagentStudios/mcp-file-processor

NPM · @INTELAGENT/MCP-FILE-PROCESSOR · SCANNED AUG 3

Text extraction, keyword extraction, language detection, and chunking for RAG

+19 this week 66 Trust /100
Trust breakdown (6 categories)

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 →

Supply Chain Security87
  • No malware found by supply-chain analysis.Pass
  • Only part of the dependency tree could be resolved (122 of 126), so this covers what we could see, not the whole tree.Partial
  • No install/post-install scripts declared.Pass
  • Only part of the dependency tree could be resolved (122 of 126), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency19
Schema Quality & AI Usability85
  • 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 Management27
  • Stability observed for 8 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
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

npm · @intelagent/mcp-file-processor

# add to Claude Code
claude mcp add intelagentstudios-mcp-file-processor -- npx -y @intelagent/mcp-file-processor
# add to Codex CLI
codex mcp add intelagentstudios-mcp-file-processor -- npx -y @intelagent/mcp-file-processor
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "intelagentstudios-mcp-file-processor": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@intelagent/mcp-file-processor"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add intelagentstudios-mcp-file-processor --command npx --arg -y --arg @intelagent/mcp-file-processor
# ~/.hermes/config.yaml
mcp_servers:
  intelagentstudios-mcp-file-processor:
    command: "npx"
    args: ["-y", "@intelagent/mcp-file-processor"]
// mcp.json
{
  "mcpServers": {
    "intelagentstudios-mcp-file-processor": {
      "command": "npx",
      "args": [
        "-y",
        "@intelagent/mcp-file-processor"
      ]
    }
  }
}
Changelog

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.

  • 3 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 2 Aug 26 +39
    • Provenance: unverified → fail security
    • Install scripts: unverified → pass security
    • Known CVEs: unverified → partial security
    • Malware scan: unverified → pass security
    • Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
    • Security disclosure: fail → unverified functional
    • Capabilities: pass → unverified functional
    • Tool coverage: 100 → unverified functional
    • Schema quality: 100 → unverified functional
    • Schema quality: unverified → excellent functional
    • License: unverified → pass functional
    • Stability: unverified → 0.23 functional
    • Maintenance: unverified → pass functional
    • Dependency health: unverified → partial functional
    • Licence: MIT functional
  • 1 Aug 26 +5
    • Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
    • MCP protocol: unverified → pass functional
  • 31 Jul 26 −26
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 27 Jul 26 47

    First indexed and scored.

Diagnostics

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 3 Aug 2026 · Analysed npm/@intelagent/[email protected]

Provenance none

Ecosystem: npm · Outcome: none

Dependencies 122 packages

122 packages in the resolved dependency tree · 122 deprecated · 48 stale.

The dependency tree was only partially resolved, so these counts may be incomplete.

MCP tools — 6 exposed · ~525 tokens

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.

Tool Tokens
chunk_text ~83

Split text into overlapping chunks suitable for RAG/embedding pipelines. Configurable chunk size and overlap. Returns chunks with positional metadata.

NameTypeReqDescription
chunkSizenumberTarget chunk size in characters (default: 1000)
overlapnumberOverlap between chunks in characters (default: 200)
textstringyesText 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.

NameTypeReqDescription
fileNamestringOptional file name for extension-based detection (e.g. "app.ts")
textstringyesText 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.

NameTypeReqDescription
limitnumberMaximum number of keywords to return (default: 20)
textstringyesText 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.

NameTypeReqDescription
contentstringyesFile content — base64-encoded for binary formats (PDF, DOCX), raw text for text formats
fileTypestringyesMIME 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.

NameTypeReqDescription
chunkOverlapnumberOverlap between chunks in characters (default: 200)
chunkSizenumberTarget chunk size in characters (default: 1000)
contentstringyesFile content — base64-encoded for binary formats (PDF, DOCX), raw text for text formats
fileTypestringyesMIME type or file extension (e.g. "application/pdf", ".md", "csv")
keywordLimitnumberMaximum 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.