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 · SCANNED SEP 24

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

0 this week 78 Trust /100
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
  • 44 of 136 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 Management80
  • Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
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
// .cursor/mcp.json
{
  "mcpServers": {
    "marin1321-mcp-devtools": {
      "command": "npx",
      "args": [
        "-y",
        "@oscarmarin/mcp-devtools"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "marin1321-mcp-devtools": {
      "command": "npx",
      "args": [
        "-y",
        "@oscarmarin/mcp-devtools"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add marin1321-mcp-devtools -- npx -y @oscarmarin/mcp-devtools
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "marin1321-mcp-devtools": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@oscarmarin/mcp-devtools"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add marin1321-mcp-devtools --command npx --arg -y --arg @oscarmarin/mcp-devtools
# ~/.hermes/config.yaml
mcp_servers:
  marin1321-mcp-devtools:
    command: "npx"
    args: ["-y", "@oscarmarin/mcp-devtools"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "marin1321-mcp-devtools": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@oscarmarin/mcp-devtools"
      ]
    }
  }
}
# add to Vellum
assistant mcp add marin1321-mcp-devtools -t stdio -c npx -a -y @oscarmarin/mcp-devtools
// mcp.json
{
  "mcpServers": {
    "marin1321-mcp-devtools": {
      "command": "npx",
      "args": [
        "-y",
        "@oscarmarin/mcp-devtools"
      ]
    }
  }
}
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.

  • 24 Sept 26 +1

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

  • 23 Sept 26 −4
    • Stability: pass → 0.77 functional
  • 22 Sept 26 +1
    • Stability: 0.97 → pass security
  • 20 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.

  • 18 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.

  • 16 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 15 Sept 26 +1
    • Stability: 0.97 → pass security
  • 13 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.

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 24 Sept 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 136 packages
Packages resolved 136
Stale 44
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.

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 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.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 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.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.