MCP Risk

Directory / server

co.machins/marketplace

This directory entry reports an automated security scan of co.machins/marketplace, scanned 2026-07-28. Trust grade C rates provenance, transport, known vulnerabilities and instruction integrity; capability risk is reported separately, not folded into the grade.

registry.modelcontextprotocol.io, scanned 2026-07-28, tool surface via package-source

C 69/100 permalink

Automated checks

StatusCheckPolicyResult
PASS Listed on the official MCP registry §1.1
Listed on registry.modelcontextprotocol.io as co.machins/marketplace. 1 finding
  • Registry entry: co.machins/marketplace ↗
FAIL Source repository is public and maintained §1.2

Claimed source repository does not exist (or is private).
FAIL Published package is consistent and attested §1.3
Integrity concerns: package repository field does not match the claimed source repo; no PyPI trusted-publishing provenance. 5 findings
  • Package: machins@0.1.0 ↗
  • Ecosystem: PyPI
  • Age: 147 days
  • Repo field matches source repo: false
  • Trusted-publishing provenance: absent
PASS Tool surface is inspectable and proportionate §2.1–§2.4
Package source scanned; no high-risk capability signals. 1 finding
  • Detected capabilities: none
PASS HTTPS-only endpoint §3.1
Endpoint uses HTTPS. 1 finding
  • Endpoint: https://machins.co/mcp
UNVERIFIABLE Authentication required §3.2

No MCP endpoint responded at this URL (HTTP 404); authentication could not be probed.
WARN OAuth protected-resource metadata published §3.3
No protected-resource metadata found - clients cannot discover the authorization server per spec. 1 finding
  • Checked: https://machins.co/.well-known/oauth-protected-resource
PASS No known vulnerabilities (OSV.dev) §4.1

No advisories on record for machins @0.1.0 (PyPI).
PASS Server-supplied instructions free of poisoning indicators §5.1–§5.4

No poisoning indicators found across 12 server-supplied text item(s).
What this grade covers
  • Provenance & supply-chain integrity (§1)
  • Tool surface & capability risk (§2)
  • Transport & authentication (§3)
  • Known CVEs via OSV.dev (§4)
  • Instruction/tool poisoning patterns (§5)

Limitations: pattern-based only (no semantic injection detection), static npm analysis (live server instructions not retrieved for package-only scans), single-server scope (no cross-server toxic flow analysis). See the full policy.

Methodology: MCP Server Security Policy. Unfamiliar term? See the glossary.