DescopeSAFE
Overview
From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.
[](https://smithery.ai/server/@descope-sample-apps/descope-mcp-server)
Introduction
The Descope Model Context Protocol (MCP) server provides an interface to interact with Descope's Management APIs, enabling the search and retrieval of project-related information.
Available Tools
search-audits: Retrieves up to 10 audit log entries from your Descope project.search-users: Retrieves up to 10 user records from your Descope project.create-user: Creates a new user in your Descope project.invite-user: Invites a new user to your Descope project.
Requirements
Before proceeding, make sure you have the following:
- Node.js (version 18 or later)
- Claude Desktop installed on your system
- A valid Descope Project ID and Management Key
- Git installed
To confirm your Node.js installation, run:
node --version # Expected output: v18.0.0 or later
Setup Instructions
Installing via Smithery
To install Descope MCP Server for Claude Desktop automatically via Smithery:
npx -y @smithery/cli install @descope-sample-apps/descope-mcp-server --client claude
Manual Installation
- Clone the repository:
git clone https://github.com/descope-sample-apps/descope-mcp-server.git cd descope-mcp-server
- Install the necessary dependencies:
npm install
- Build the project:
npm run build
Configuration
1. Configure Claude Desktop to recognize the Descope MCP server
To locate the claude_desktop_config.json file, open the Claude Desktop app and enable Developer Mode from the top-left menu bar.
Once enabled, go to
c7f4933a8cfaOBSERVED · 2026-10-08Connect
Built from this server's own package name, version and transport as found in its source — not copied from anyone's documentation, so it cannot drift against a page we do not control. Replace the environment placeholders with a token scoped to the least it needs.
claude mcp add descope-mcp-server --env DESCOPE_MANAGEMENT_KEY=${DESCOPE_MANAGEMENT_KEY} -- npx -y [email protected]{
"mcpServers": {
"descope-mcp-server": {
"command": "npx",
"args": [
"-y",
"[email protected]"
],
"env": {
"DESCOPE_MANAGEMENT_KEY": "${DESCOPE_MANAGEMENT_KEY}"
}
}
}
}Exposed tools (4)
2 read · 2 write · 0 destructive.
| Tool | Risk | Description |
|---|---|---|
create-user | write | Create a new user in Descope project |
invite-user | write | Create and invite a new user to the Descope project |
search-audits | read | Search Descope project audit logs |
search-users | read | Search for users in Descope project |
Trust audit
SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | PASS |
| L1 | Static analysis of the code | PASS |
| L2 | Instruction surface (what it tells the agent) | PASS |
| L3 | Class-specific surface | PASS |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- none-observed
- Network
- declared (1 observation(s))
- Shell
- none-observed
- Dependencies
- not all pinned
- Secrets in source
- none-found
Findings (1)
@descope/node-sdk, @modelcontextprotocol/sdk, dotenv, express, node-fetch, zod, @types/express, @types/node
Gates applied: no_behavioural_pass.
c7f4933a8cfafull audit observations/trust-audit/mcp-server/descope-sample-apps__descope.json · Report an issue / request a re-scanAudit history
Every audit this server has had. A grade with a past is a grade somebody is still checking.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-08 | c7f4933a8cfa | SAFE | B | 89 | first audit |
Questions
What tools does Descope expose?
4 in total: 2 read-only, 2 that write, and 0 that can delete or overwrite. Every one is listed on this page with its risk.
Is Descope safe to connect to an agent?
The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean server reads B.
What credentials does Descope need?
It reads DESCOPE_MANAGEMENT_KEY from the environment. Give it a token scoped to the least it needs — an agent that can be talked into calling a tool can be talked into calling it with your credentials.
How does Descope run?
It speaks sse and stdio, so it runs as a local process your client starts. It is published on npm as descope-mcp-server at 1.0.0.
How current is this page?
The grade is for one exact copy of the source (c7f4933a8cfa), read on 2026-10-08. The repository is watched and re-audited when it changes.