Hosting

hosted

Transport

Streamable HTTP

Endpoint

https://mcp.safedep.io/model-context-protocol/threats/v1/mcp

Authentication

API key in Authorization plus tenant domain in X-Tenant-ID; legacy SSE endpoint is separately documented.

Requirements

• Hosted mode requires an MCP client supporting remote HTTP servers and custom HTTP headers, a SafeDep Cloud tenant, an API key, and the tenant domain.
• The official documentation describes a free tier; check the current plan and account terms in SafeDep Cloud.
• Local stdio mode requires Docker for the documented container setup, or a separately installed vet binary. Avoid writing server logs to stdout because that would corrupt stdio MCP traffic.
• The local vet MCP README documents npm and PyPI package ecosystems. Hosted service documentation describes broader registry coverage; coverage may depend on the service and account configuration.

Setup steps

1. For hosted use, sign in at https://app.safedep.io/settings/api-keys with Google, GitHub, or email. First sign-in creates a tenant. In SafeDep Cloud settings, create an API key and copy the tenant domain shown there.
2. Store the API key and tenant domain in local environment variables named SAFEDEP_API_KEY and SAFEDEP_TENANT_ID. Do not place their values in a catalog record or commit them.
3. Add the hosted Streamable HTTP MCP endpoint https://mcp.safedep.io/model-context-protocol/threats/v1/mcp to the client. For Codex, the official SafeDep docs show [mcp_servers.safedep] with url set to that endpoint and [mcp_servers.safedep.env_http_headers] mapping Authorization to SAFEDEP_API_KEY and X-Tenant-ID to SAFEDEP_TENANT_ID.
4. Restart or reload the MCP client and confirm the server connects and its tools are visible. The official source does not publish a stable named tools/list inventory, so do not treat a guessed tool name/count as verified.
5. The official setup guide describes a safe connection check using the package safedep-test-pkg in npm or PyPI, which SafeDep marks malicious for testing. Ask the agent to check/report its verdict; do not actually install the package.
6. For local stdio use, the maintainer documents Docker command: docker run --rm -i ghcr.io/safedep/vet:latest -l /tmp/vet-mcp.log server mcp. The default transport is stdio. Keep diagnostics directed to a file rather than stdout.

Current SafeDep vet MCP source registers six package-safety tools by default. Two SQL-query tools are opt-in via --sql-query-tool and require a database path; catalog includes both configuration-dependent tools.

• get_package_version_malware_report

  Get a malware analysis report for a package version.

  01
• get_package_version_vulnerabilities

  Get vulnerabilities for a package version.

  02
• get_package_version_popularity

  Get popularity information for a package version.

  03
• get_package_version_license_info

  Get license information for a package version.

  04
• get_package_latest_version

  Get the latest version of a package.

  05
• get_package_available_versions

  List available versions for a package.

  06
• vet_query_sql_introspect_schema

  Inspect tables, columns, types, and relationships in the local vet report database.

  07
• vet_query_execute_sql_query

  Run a read-only SELECT query on the local vet report database.

  08

• Hosted endpoint requires both API key and tenant domain headers.

• official repository documentation

  Documents local vet MCP over stdio or SSE, Docker invocation, stdout logging warning, and npm/PyPI support for the local MCP.

• official credential and tenant portal

  SafeDep sign-in entry for API key settings. Official docs state that first sign-in creates a tenant and the tenant domain appears in Cloud settings.

• official publisher branding

  Verified publisher organization branding asset selected as the official SafeDep product mark (A/B branding tier); downloaded original SVG, decoded/rasterized to transparent PNG, and visually reviewed on light and dark card backgrounds.

• official documentation

  Current publisher or maintainer documentation reviewed 2026-10-28T19:00:00.000Z.

Documentation checked 2026-10-28T19:00:00.000Z. Connection has not been runtime tested.