Devcontainer MCP

An MCP to allow Copilot and Claude Code to work directly with and inside of a devcontainer

MCP Servers Rust Listed MIT

Is Devcontainer MCP safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 3.1 / 10
Provenance None
Signed commits 30%
Last push 18d ago
Compare Devcontainer MCP
Suggest a correction

In detail: Devcontainer MCP scores 46.4/100 (Grade D), ranked #1033 of 1325 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 3.1/10; 30% of recent commits are signed; last pushed 2026-09-08. Every point is earned from checkable signals — never paid placement. How scoring works →

How Devcontainer MCP compares in MCP Servers

  1. #603 Scrapegraph MCP 46.8 +0.4
  2. #604 Agrobr MCP 46.5 +0.1
  3. #605 Devcontainer MCP 46.4 this agent
  4. #606 Synter Media AI MCP Server 46.1 −0.3
  5. #607 Godot MCP 46.0 −0.4

Bars show each HVTrust score; the tick marks Devcontainer MCP’s 46.4.

Where the 46.4 comes from

HVTrust dimensions vs the MCP Servers average

46.4 / 100 · 100.0% confidence

Devcontainer MCP MCP Servers average (775 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
5.4 / 25
4.9 below avg 10.3
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.6 below avg 13.4
Transparency50% declared license · 50% OSSF Scorecard
11.1 / 17
1.1 below avg 12.2
Maintenance60% last-push freshness · 40% commit activity
13.6 / 20
1.5 above avg 12.1
AdoptionLog-scaled stars · package downloads
3.5 / 20
3.7 below avg 7.2

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Rank Moved
Rank dropped 436 spots (#583 → #1019)
2026-09-23
HVTrust Changed
HVTrust up 11.9pts (34.7 → 46.6)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 3.1/10. Tighten the weakest checks to improve public safety evidence.
Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.
Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.
43.2
Activity sub-score · out of 100
#605

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade D reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage C is separate — it grades how many independent signal types back the score (2 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-09-26 06:32 UTC · Repo last pushed 18 days ago

Rank Trend

2026-08-11 2026-09-26

Activity & Reach

Stars
27
Forks
4
Last Push
2026-09-08
18 days ago
Commits (4 wk)
4
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
4
Rank Change
▼2
was #1031

Analysis

Activity Inputs

43.2 / 100
StarsRepository reach
8.7 / 30
FreshnessLast push recency
22.5 / 25
ActivityRecent commits
8.7 / 25
CommunityFork signal
3.3 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
3.1 / 10
OpenSSF Scorecard · scanned Sep 23, 2026
Signed Commits
30%
of last 100 commits verified
Binary-Artifacts 10
Branch-Protection 0
CI-Tests 10
CII-Best-Practices 0
Code-Review 0
Contributors 0
Dangerous-Workflow 10
Dependency-Update-Tool 0
Fuzzing 0
License 10
Maintained 6
Packaging -1
Pinned-Dependencies 0
SAST 0
Security-Policy 0
Signed-Releases 0
Token-Permissions 0
Vulnerabilities 5

Common questions about Devcontainer MCP

Public trust evidence for Devcontainer MCP is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.
Does Devcontainer MCP publish package provenance?
No published build provenance is currently detected for Devcontainer MCP. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Devcontainer MCP have an OpenSSF Scorecard?
Devcontainer MCP has an OpenSSF Scorecard score of 3.1/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.
Is Devcontainer MCP actively maintained?
Maintained. Last push was 18 days ago.
What license does Devcontainer MCP use?
Devcontainer MCP ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Devcontainer MCP's commits signed?
29% of the last 100 commits to Devcontainer MCP are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

AI agent surface

MCP, providers, tool surface
Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support
medium confidence
Implemented
Devcontainer MCP appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
None detected
No clear third-party provider dependency detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
None detected
No clear plugin system or broad tool surface detected.
Detailed evidence is not shown in the public view.
Package Provenance Drift
N/A
No package source configured
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live
How this surface has changed

Detected changes to Devcontainer MCP's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.

2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented

Maintain Devcontainer MCP?

For maintainers

HVTrust scores Devcontainer MCP from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Reputation Timeline

Signal history
Rank 22Listed 2HVTrust 2Scorecard 1Delisted 1MCP 1
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Rank Moved
Rank dropped 436 spots (#583 → #1019)
2026-09-23
HVTrust Changed
HVTrust up 11.9pts (34.7 → 46.6)
2026-09-22
Newly Listed
First tracked at rank #583
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-17
Rank Moved
Rank rose 25 spots (#1029 → #1004)
2026-09-12
Rank Moved
Rank dropped 12 spots (#1015 → #1027)
2026-09-11
Rank Moved
Rank dropped 13 spots (#1002 → #1015)
2026-09-09
Rank Moved
Rank dropped 15 spots (#995 → #1010)
2026-09-07
Rank Moved
Rank dropped 36 spots (#968 → #1004)
2026-09-06
Rank Moved
Rank dropped 14 spots (#954 → #968)
2026-09-05
Rank Moved
Rank dropped 62 spots (#892 → #954)
2026-09-04
Rank Moved
Rank dropped 27 spots (#865 → #892)
2026-09-03
Rank Moved
Rank dropped 43 spots (#822 → #865)
2026-09-02
Rank Moved
Rank dropped 42 spots (#780 → #822)
2026-09-01
Rank Moved
Rank dropped 25 spots (#755 → #780)
2026-08-31
Rank Moved
Rank dropped 35 spots (#720 → #755)
2026-08-30
Rank Moved
Rank dropped 27 spots (#693 → #720)
2026-08-29
Rank Moved
Rank dropped 46 spots (#647 → #693)
2026-08-28
Rank Moved
Rank dropped 18 spots (#629 → #647)
2026-08-27
Rank Moved
Rank dropped 17 spots (#612 → #629)
2026-08-26
Scorecard Added
OSSF Scorecard: 3.2/10
2026-08-26
Rank Moved
Rank rose 426 spots (#1038 → #612)
2026-08-26
HVTrust Changed
HVTrust up 25.3pts (20.7 → 46.0)
2026-08-24
Rank Moved
Rank dropped 12 spots (#1026 → #1038)
2026-08-16
Rank Moved
Rank dropped 29 spots (#1010 → #1039)
2026-08-12
Rank Moved
Rank rose 14 spots (#1016 → #1002)
2026-08-10
Rank Moved
Rank dropped 20 spots (#990 → #1010)
2026-08-08
Newly Listed
First tracked at rank #976

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 46.4 Grade D
Markdown:
[![HVTrust](https://hvtracker.net/badge/devcontainer-mcp.svg)](https://hvtracker.net/agents/devcontainer-mcp)
HTML:
<a href="https://hvtracker.net/agents/devcontainer-mcp"><img src="https://hvtracker.net/badge/devcontainer-mcp.svg" alt="HVTrust"></a>

Other agents in MCP Servers

Data sources
GitHub REST API (repo, commits, stars, forks, license) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON