Developer · Remote MCP server
DepScope
Package intelligence MCP for AI agents - 22 tools, 19 ecosystems, AGPL SDK, free.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
dev.depscope/mcp- Version
- 0.9.24
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP, stdio (local process)
- Package
- npm
- Published
- 2026-05-05
- Updated
- 2026-05-05
- Publisher
- dev.depscope
- Namespace
- Namespace verified by the MCP Registry via the domain depscope.dev · how
- Website
- depscope.dev
- Repository
- github.com/cuttalo/depscope-mcp
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://mcp.depscope.dev/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 410)
- Handshake
- HTTP 410
- Checked on
- 2026-10-05
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | depscope-mcp | 0.9.0 | stdio |
How to connect DepScope
DepScope is a remote MCP server: there is nothing to install. Its endpoint is https://mcp.depscope.dev/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
It can also run locally from a Node.js package published to the npm registry: depscope-mcp version 0.9.0. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y depscope-mcp@0.9.0.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"depscope-mcp@0.9.0"
]
}
}
}Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| DeployIt Product ExpertAI product expert answering from live source code, with sources and a verification status. | Remote · HTTPLive check: ✓ handshake |
| Deployment.ioDeploy apps on your cloud. Create environments, configure infrastructure, and monitor jobs. | Remote · HTTPLive check: sign-in required |
| DepotInspect Depot builds, CI runs, job logs and Actions runners; retry or cancel CI runs. | Remote · HTTPLive check: ✓ handshake |
| Deprecation MCPMCP server for cross-vendor API/SDK deprecation and breaking-change tracking. | Local · stdio |
| DepwireDependency graph + 24 MCP tools. Impact analysis, simulation, security, agent coordination. | Local · stdio |
| DesignforyouGenerate logos, social posts, app screenshots, comic panels & visual-novel assets from prompts. | Remote · HTTPLive check: ✓ handshake |
| DesignvaultSearch, browse and manage your DesignVault design-asset library from any MCP client. | Local · stdio |
| DeskCloneAsk a company's DeskClone support agent from Claude, Cursor or any MCP client (API key needed). | Remote · HTTPLive check: sign-in required |