io.github.dev-proxy-tools/mcp

Name: io.github.dev-proxy-tools/mcp
Author: io.github.dev-proxy-tools

MCPattested

v0.3.1io.github.dev-proxy-toolsUnknownUpdated 9mo agonpm GitHub

MCP server for Dev Proxy that enables AI assistants to interact with Dev Proxy.

A Model Context Protocol (MCP) server for Dev Proxy that enables AI assistants to interact with Dev Proxy capabilities using the MCP standard. Use this server to: 1. Create Dev Proxy configurations using natural language 1. Get contextual help for working with Dev Proxy 1. Discover Dev Proxy features and capabilities Dev Proxy is an API simulator that helps you effortlessly test your app beyond…

Works in

ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Attested build

A verified provenance attestation binds this artifact to the listed repository. Nobody has claimed the listing yet — this proves where the code was built, not who stands behind it.

4GitHub stars

2Forks

9mo agoLast update

Package

Authorio.github.dev-proxy-tools

LicenseUnknown

Version0.3.1

Sourcemcp-registry

npm@devproxy/mcp

GitHubdev-proxy-tools/mcp

SBOMCycloneDX 1.6 ↓

Trust Status

85/100Trusted

✓Listed in Forge index+10/10

✓Identity verified · attested build+20/20

—Ed25519 publish signature+0/5

→ Included automatically when the publisher runs `forge publish`

—Domain verification+0/5

→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }

✓npm Trusted Publishing (Sigstore)+5/5

—npm maintainer match+0/5

→ Publisher: add the verified GitHub login to the npm package's maintainers (npm owner add <login>)

✓CVE scan · clean+30/30

✓Static analysis · clean+20/20

Paste into Claude Code, Cursor, or any AI assistant to fix all gaps

StatusIdentity verified

PublisherUnverified

SignatureUnsigned

Domain—

Provenance✓ Sigstore-verified · 1f1e856

Dependencies✓ 60 resolved+ · none vulnerable

Tool surface4 tools · none privileged

Security scan✓ Cleanv0.4.0 · 3mo agoHow well does this scan work?

EvalsNone

IndexedJun 13, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

4 tools · none privileged

Statically extracted from the published packagev0.4.0 · 3mo ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

GetBestPracticesNo description published

This tool published no description. Forge does not invent one.

FindDocsNo description published

This tool published no description. Forge does not invent one.

GetVersionNo description published

This tool published no description. Forge does not invent one.

CreateJwtNo description published

This tool published no description. Forge does not invent one.

0 of 4 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

Keywords

mcp

Alternatives

Comparing tool surfaces…

io.github.dev-proxy-tools/mcp

Tools

Tools exposed

No dependency coverage