Kapilraghuwanshi Dev Tools MCP Server
@kapilraghuwanshi/dev-tools-mcp
npm
v1.3.0
Published by @kapilraghuwanshi — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.
Zero-config MCP server for developers — encode/decode, hash, UUID, JWT, DNS, IP info, URL tracing, npm lookup and more.
The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.
1. Threat score — 100 − 6.3 = 94. What the published surface and source actually contain:
| Points | What was found | Category |
|---|---|---|
| −6.3 | Suspicious external URL in tool metadata MTC-INJ-URL-1 | exfiltration |
2. Client adoption risk — 94 − 4 = 90. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:
| Points | Adoption-risk factor |
|---|---|
| −3 | capability blast radius (moderate) — client exposure if the model is manipulated |
| −1 | publisher verification (public source) — no provenance, but the source is public and inspectable |
Capability observations and info notes are shown under Findings but never scored.
Open any row's finding below for the file, line and evidence behind a deduction.
Findings 2
medium Suspicious external URL in tool metadataMTC-INJ-URL-1
A hardcoded link to a request/paste/webhook sink (or raw IP) appears in the description of tool "dt_http_trace". Tool metadata pointing the model at a fixed external endpoint is a data-exfiltration channel — the classic "send the output to …" poisoning.
Evidence: https://bit.ly/xyz
Fix: A legitimate tool takes its destination as a validated parameter; it does not hardcode a webhook/paste sink in its description.
Location: tool dt_http_trace · description
medium Unconstrained URL/host parameter "url" on "dt_http_headers"MTC-CAP-007
Tool "dt_http_headers" takes a URL/host parameter "url" with no allowlist/pattern. An outbound-request tool with an unbounded destination enables SSRF and cloud-metadata access (e.g. 169.254.169.254).
Fix: Allowlist destinations or constrain the parameter; block private/link-local addresses server-side.
Location: tool dt_http_headers · inputSchema.properties.url
Tools 27
Each tool and what it can reach — statically extracted from the published source.
dt_format_sqlreads sensitive datadt_github_repoingests untrusted inputdt_http_headersingests untrusted inputdt_npm_infoingests untrusted inputdt_caniuseno sensitive capabilitydt_color_convertno sensitive capabilitydt_convert_caseno sensitive capabilitydt_diff_textno sensitive capabilitydt_dns_lookupno sensitive capabilitydt_encode_decodeno sensitive capability
Show 17 more tools ↓
dt_format_jsonno sensitive capabilitydt_generate_passwordno sensitive capabilitydt_generate_uuidno sensitive capabilitydt_gitignore_genno sensitive capabilitydt_hash_stringno sensitive capabilitydt_http_traceno sensitive capabilitydt_ip_infono sensitive capabilitydt_lorem_ipsumno sensitive capabilitydt_my_ipno sensitive capabilitydt_parse_jwtno sensitive capabilitydt_port_checkno sensitive capabilitydt_regex_testno sensitive capabilitydt_ssl_checkno sensitive capabilitydt_timestamp_convertno sensitive capabilitydt_unit_converterno sensitive capabilitydt_url_parseno sensitive capabilitydt_whois_lookupno sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (27 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Versions 1
Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v1.3.0 latest |
A 90/100 | 2 | 1.13.0 | 2026-09-07 |
Embed this score
Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.
Verify this score yourself
The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.
npx mcptrustchecker scan @kapilraghuwanshi/dev-tools-mcp --onlineOther implementations of Kapilraghuwanshi Dev Tools 1
Independent packages implementing the same tool, scanned with the same engine. Compare all 2 side by side →
More in Other
A Model Context Protocol server implementation for AdGuard Home that enables AI agents to query and manage DNS records, filtering rules and more
Identity oracle and trust layer for autonomous AI agents. Bidirectional KYA and trust scoring.
MCP server with Airtable integration
A free one-minute reset for people, delivered by AI, with no account or personal data.
Access SEC filings efficiently, save time and tokens, and get cited answers.
A smart [MCP](https://modelcontextprotocol.io) server for [AniList](https://anilist.co) that gets your anime/manga taste - not just API calls.