dev.bigapi/mcp
NPM · @BIGAPI/MCP
The output layer for AI agents: turn what an agent produced into a finished file.
Available components
Last scanned (21 hours ago)
Scores higher than 71% 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 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
- 31 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- 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 5 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability65
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1436 tokens (~287/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 19 Nov 26 0
- Stability: 0.97 → pass security
- 18 Nov 26 0
- Security disclosure: unverified → fail ▼ functional
- Stability: pass → 0.97 functional
- 17 Nov 26 0
- Security disclosure: fail → unverified ▼ functional
- 16 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 15 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- Package version: 0.9.0 → 0.9.1 functional
- 14 Nov 26 0
- Security disclosure: unverified → fail ▼ functional
- 13 Nov 26 0
- Security disclosure: fail → unverified ▼ functional
- 12 Nov 26 0
- Stability: 0.97 → pass security
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 21 Nov 2026 · Analysed npm/@bigapi/mcp@0.9.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 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 31 |
| 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 →
enable_tools ~206
Add the dedicated tools for specific operations to this session, e.g. ["pdf_redact","einvoice_validate"], or ["all"] for every operation. Tools for every operation in the live bigapi catalogue are available, including ones added after this server was released. bigapi starts lean – only find_tool, run_operation, get_access and get_balance are listed – so your context stays free. You rarely need this: every operation already runs through run_operation. Reach for it when you will call the same operation many times and want its parameters spelled out in your tool list. Names come from find_tool; unknown names are reported back and skipped while the rest are still enabled. The effect lasts for this session, adds to what is already enabled, and cannot be undone from here – restart the server for the lean list again.
| Name | Type | Req | Description |
|---|---|---|---|
| names | array | yes | Tool names as find_tool reports them, e.g. ["pdf_redact","ocr"], or ["all"] for the full list |
No output schema declared.
No examples provided.
find_tool ~191
Find the right bigapi operation for a task. Describe what you need in plain words, English or German – "convert a png to webp", "remove customer names from a contract", "extract the ZUGFeRD invoice XML" – and get the matching operations with their parameters, a ready-to-run example, the price and a guide link. It recommends only: it never touches your files and never spends credit; run what it names with run_operation. Free and no API key needed, so it is also the cheapest way to see what bigapi covers. Start here whenever you are unsure which operation fits, and skip it when you already know the operation name. If nothing fits, the answer says so plainly instead of guessing.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many candidates to return |
| query | string | yes | The task in plain words, e.g. "convert a png to webp" |
No output schema declared.
No examples provided.
get_access ~162
Get a bigapi API key for this machine. Call this once when no key is configured; other bigapi tools fail with "no API key" until you do. Creates a NEW free key (no signup, no credit card) and stores it in the local config file, where every bigapi tool picks it up. Calling it again creates an additional key rather than returning the existing one – use get_balance to check the key you already have. The new key includes 100 free operations, then $0.01 per operation from a prepaid balance; neither expires. Needs network access to api.bigapi.dev.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | – | Label stored with the key so you can tell keys apart later, e.g. "claude-desktop". Cosmetic only. |
No output schema declared.
No examples provided.
get_balance ~93
Check the bigapi key that is currently configured: remaining credit, free operations left, monthly cap and spend so far this month. Read-only, free, and a snapshot of this moment – the numbers move as operations run. Use it to confirm a key works, before a large batch, or when an operation reports a low balance. It does not create keys (that is get_access) and does not list past operations.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
run_operation ~288
Run any bigapi operation on real files: merge or redact a PDF, OCR a scan, convert an image, chunk text for embeddings, read a ZUGFeRD invoice, sign an image as AI-generated. Take the operation name from find_tool (e.g. "pdf/merge", "ocr", "text/chunk"). Uploads are local file paths. A file result is written to output_path, or to a temporary file when you omit it, and the path comes back with size and content type; a data result comes back as JSON. $0.01 per operation flat, no subscription, and failed calls cost nothing. This one executor covers every operation, including ones added after your client started – enable_tools only adds convenience wrappers around it. Files are processed in Germany, deleted right after delivery, and every operation ships with a published proof that it does what it promises.
| Name | Type | Req | Description |
|---|---|---|---|
| file_field | string | – | Form field for the uploads; defaults to "files[]" for pdf/merge and "file" otherwise |
| files | array | – | Local file paths to upload, in order |
| op | string | yes | Operation name or path, e.g. "pdf/merge" or "/v1/pdf/merge" |
| output_path | string | – | Where to write the result |
| params | object | – | Parameters of the operation, exactly as described by find_tool |
No output schema declared.
No examples provided.
How do I install the dev.bigapi/mcp server?
dev.bigapi/mcp runs locally as an npm package, launched with npx -y @bigapi/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 · @bigapi/mcp
claude mcp add dev-bigapi-mcp -- npx -y @bigapi/mcp
What is the dev.bigapi/mcp server?
dev.bigapi/mcp is listed in the public MCP registry as dev.bigapi/mcp. The output layer for AI agents: turn what an agent produced into a finished file. This page covers its npm package (@bigapi/mcp).
Is the dev.bigapi/mcp server safe to use?
dev.bigapi/mcp scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 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 dev.bigapi/mcp server expose?
dev.bigapi/mcp exposes 5 tools: find_tool, run_operation, enable_tools, get_access, get_balance. Their descriptions and schemas cost roughly 940 tokens of context every time the server is loaded.
Is the dev.bigapi/mcp server still maintained?
dev.bigapi/mcp is still listed as active in the MCP registry. We last reached this channel on 21 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 dev.bigapi/mcp server under?
dev.bigapi/mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the dev.bigapi/mcp server?
VerifyMCP ran 16 checks on dev.bigapi/mcp, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.