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

io.github.marin1321/mcp-devtools

NPM · @OSCARMARIN/MCP-DEVTOOLS

MCP server giving AI agents safe access to filesystem, databases, processes, and APIs.

0 this week 81 Trust /100

Last scanned (17 hours ago)

Scores higher than 69% of npm servers

Category Developer Tools

Trust breakdown (7 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 → 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
  • 45 of 133 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability77
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 857 tokens (~50/item across 17 items; 15 tools + 2 resources), lean.Pass
  • 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 Coverage72
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 17% of tool parameters carry a description.Partial
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "query_db" implies "execute" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 16 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
What we tested

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 →

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.

  • 20 Nov 26 +1
    • Stability: 0.97 → pass security
  • 19 Nov 26 −1
    • CVE-2026-112366 no longer affects this package ▲ security
    • Known CVEs: partial → pass ▲ security
    • Stability: pass → 0.97 functional
  • 18 Nov 26 0
    • CVE-2026-112366 affects this package ▼ security
    • Known CVEs: pass → partial ▼ security
  • 13 Nov 26 +1
    • Stability: 0.97 → pass security
  • 12 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 10 Nov 26 +6
    • Source repository: unverified → pass ▲ security
  • 9 Nov 26 −6
    • Provenance: pass → unverified ▼ security
  • 6 Nov 26 +1
    • Stability: 0.97 → pass security
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 21 Nov 2026 · Analysed npm/@oscarmarin/mcp-devtools@1.0.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 133 packages
Packages resolved 133
Stale 45
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 15 exposed · ~819 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. 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 →

Tool Tokens
call_api ~62

Invoke an operation defined in an OpenAPI spec.

NameTypeReqDescription
body–––
headersobject––
operationIdstringyes–
pathParamsobject––
queryParamsobject––
specPathstringyes–

No output schema declared.

No examples provided.

describe_table ~41

Return column metadata for a table in a configured database connection.

NameTypeReqDescription
connectionstring––
schemastring––
tablestringyes–

No output schema declared.

No examples provided.

echo_test ~45

Returns the provided message and a server-side ISO timestamp. Used to verify the MCP server pipeline end-to-end.

NameTypeReqDescription
messagestringyesArbitrary string the server will echo back

No output schema declared.

No examples provided.

get_env ~52

Return environment variables (process env or .env file) with optional masking.

NameTypeReqDescription
keysarray––
maskSecretsboolean––
pathstring––
sourcestring––

No output schema declared.

No examples provided.

get_file_info ~38

Return metadata (size, type, MIME, line count, symlink info) for a file or directory.

NameTypeReqDescription
pathstringyes–

No output schema declared.

No examples provided.

list_directory ~52

List directory entries inside the configured scope, with optional recursion and glob filtering.

NameTypeReqDescription
depthinteger––
globstring––
includeHiddenboolean––
pathstring––

No output schema declared.

No examples provided.

list_processes ~60

List running processes, optionally filtered by name or listening port.

NameTypeReqDescription
limitinteger–Maximum number of results
namestring–Filter processes by name substring (case-insensitive)
portinteger–Filter by TCP listening port

No output schema declared.

No examples provided.

list_tables ~30

List tables in a configured database connection.

NameTypeReqDescription
connectionstring––
schemastring––

No output schema declared.

No examples provided.

parse_openapi ~28

Parse an OpenAPI spec and return a summary of operations.

NameTypeReqDescription
pathstringyes–

No output schema declared.

No examples provided.

query_db ~62

Execute a parameterized SQL query against a configured database connection. Read-only by default.

NameTypeReqDescription
connectionstring––
maxRowsinteger––
paramsarray––
sqlstringyes–
timeoutMsinteger––

No output schema declared.

No examples provided.

read_file ~79

Read a text file inside the configured scope. Optionally restrict to a line range.

NameTypeReqDescription
endLineinteger–1-based, inclusive. Returns up to and including this line.
pathstringyesRelative path from the configured scope root
startLineinteger–1-based, inclusive. Returns from this line onwards.

No output schema declared.

No examples provided.

read_logs ~49

Read the tail of a configured log file with optional filter.

NameTypeReqDescription
filterstring––
jsonFieldstring––
pathstringyes–
tailinteger––

No output schema declared.

No examples provided.

run_command ~73

Spawn a process from the configured allowedCommands list. Captures stdout/stderr with caps and a timeout.

NameTypeReqDescription
argsarray––
commandstringyesBinary name (must be in allowedCommands)
cwdstring––
envobject––
timeoutMsinteger––

No output schema declared.

No examples provided.

search_files ~92

Search for a pattern (literal or regex) across files inside the configured scope.

NameTypeReqDescription
caseInsensitiveboolean––
contextLinesinteger––
globstring––
includeHiddenboolean––
maxResultsinteger––
pathstring––
patternstringyes–
regexboolean–Treat `pattern` as a regular expression

No output schema declared.

No examples provided.

write_file ~56

Write a file atomically inside the configured scope (writes to a temp file then renames).

NameTypeReqDescription
contentstringyes–
createDirsboolean––
encodingstring––
pathstringyes–

No output schema declared.

No examples provided.

Install

How do I install the io.github.marin1321/mcp-devtools server?

io.github.marin1321/mcp-devtools runs locally as an npm package, launched with npx -y @oscarmarin/mcp-devtools. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @oscarmarin/mcp-devtools

# add to Claude Code
claude mcp add marin1321-mcp-devtools -- npx -y @oscarmarin/mcp-devtools
Common questions

What is the io.github.marin1321/mcp-devtools server?

io.github.marin1321/mcp-devtools is listed in the public MCP registry as io.github.marin1321/mcp-devtools. MCP server giving AI agents safe access to filesystem, databases, processes, and APIs. This page covers its npm package (@oscarmarin/mcp-devtools).

Is the io.github.marin1321/mcp-devtools server safe to use?

io.github.marin1321/mcp-devtools scores 81 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 io.github.marin1321/mcp-devtools server expose?

io.github.marin1321/mcp-devtools exposes 15 tools: echo_test, read_file, write_file, list_directory, search_files, and 10 more. Their descriptions and schemas cost roughly 819 tokens of context every time the server is loaded.

Is the io.github.marin1321/mcp-devtools server still maintained?

io.github.marin1321/mcp-devtools 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 io.github.marin1321/mcp-devtools server under?

io.github.marin1321/mcp-devtools 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 io.github.marin1321/mcp-devtools server?

VerifyMCP ran 16 checks on io.github.marin1321/mcp-devtools, 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.