@microsoft/vscode-inproc-mcp

npm

Is @microsoft/vscode-inproc-mcp safe to use?

Based on the latest brin safety scan, no vulnerabilities or threats were detected for @microsoft/vscode-inproc-mcp v0.3.0. Trust score: 75/100. No known CVE vulnerabilities, no detected threat patterns, and no suspicious capabilities identified. This is an automated, point-in-time assessment.

Install (safety-checked)

@microsoft/vscode-inproc-mcp Passed Security Checks

No security concerns detected

clean
CVEs

0

Threats

0

Install Scripts

0

No Concerns Detected

No security concerns detected in the latest brin assessment. This is an automated, point-in-time evaluation — security posture may change.

This is an automated, point-in-time assessment and may contain errors. Findings are risk indicators, not confirmed threats. Security posture may change over time. Maintainers can dispute findings via the brin review process.

@microsoft/vscode-inproc-mcp Capabilities & Permissions

What @microsoft/vscode-inproc-mcp can access when installed. Review these capabilities before using with AI agents like Cursor, Claude Code, or Codex.

Filesystem Access

Writes to the filesystem.

package.json (w)

AGENTS.md for @microsoft/vscode-inproc-mcp

Good instructions lead to good results. brin adds @microsoft/vscode-inproc-mcp documentation to your AGENTS.md so your agent knows how to use it properly—improving both safety and performance.

brin init

Vercel's research: 100% accuracy with AGENTS.md vs 53% without →

@microsoft/vscode-inproc-mcp Documentation & Source Code

For the full @microsoft/vscode-inproc-mcp README, API documentation, and source code, visit the official package registry.

Frequently asked questions about @microsoft/vscode-inproc-mcp safety

Weekly Downloads

10

Version

0.3.0

License

See LICENSE in the project root for license information.

Last Scanned

1 day ago

Trust Score

75/100·Legitimacy signals, not safety

Capabilities

Filesystem

Writes files