RISKEN MCP Server

The RISKEN MCP Server is a Model Context Protocol (MCP) server that provides seamless integration with RISKEN APIs, enabling advanced automation and interaction capabilities for developers and tools.
Power your agent
Install from the publisher. Not a PlugMCP endpoint.
Host a copy with our keys and logs.
No packaged release in the registry yet. Follow the repository README.
Remote URL or a command on your machine? How the two installs differ
Run on PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
LaunchFrom the publisher

The RISKEN MCP Server is a Model Context Protocol (MCP) server that provides seamless integration with RISKEN APIs, enabling advanced automation and interaction capabilities for developers and tools.
RISKEN's official MCP Server
By connecting the RISKEN MCP server to your everyday AI tools, you can perform various operations such as:
Please add the following MCP server configuration to your MCP Client (Claude Desktop or Cursor) settings.
{
"mcpServers": {
"risken": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"RISKEN_ACCESS_TOKEN",
"-e",
"RISKEN_URL",
"ghcr.io/ca-risken/risken-mcp-server",
"stdio"
],
"env": {
"RISKEN_URL": "http://localhost:8098",
"RISKEN_ACCESS_TOKEN": "your_access_token"
}
}
}
}
RISKEN MCP Server supports Streamable HTTP.
docker run -it --rm \
-e RISKEN_URL=http://localhost:8098 \
-e RISKEN_ACCESS_TOKEN=xxxxxx \
-p 8080:8080 \
ghcr.io/ca-risken/risken-mcp-server http
You can deploy the server on Google Cloud Run with Terraform.
Visit terraform/examples/googlecloud and deploy the server on Google Cloud Run with Terraform.
Add the following MCP server configuration to your MCP Client (Claude Desktop or Cursor) settings.
Note: Since most MCP clients only allow stdio connections, it is currently necessary to use mcp-remote as a proxy to connect to remote MCP servers.
{
"mcpServers": {
"risken": {
"command": "npx",
"args": [
"mcp-remote",
"http://localhost:8098/mcp",
"--header",
"RISKEN-ACCESS-TOKEN:${RISKEN_ACCESS_TOKEN}"
],
"env": {
"RISKEN_ACCESS_TOKEN": "xxxxxx"
}
}
}
}
RISKEN MCP Server supports Third-Party Authorization (OAuth2.1) that enables secure authentication through external Identity Providers (IdP).
The OAuth2.1 implementation follows the MCP Authorization specification with Third-Party Authorization Flow, where:
sequenceDiagram
participant Browser as User Browser
participant Client as MCP Client
participant Server as MCP Server
participant IdP as Identity Provider
Client->>Server: POST /mcp (no auth)
Server->>Client: 401 Unauthorized + WWW-Authenticate
Client->>Server: GET /.well-known/oauth-authorization-server
Server->>Client: Authorization metadata
Client->>Server: POST /register (Dynamic Client Registration)
Server->>Client: client_id
Client->>Browser: Open authorization URL (with PKCE challenge)
Browser->>IdP: User authentication
IdP->>Browser: Redirect to callback URL (with code)
Browser->>Server: GET /oauth/callback (IdP code)
Note over Server: Store IdP code, generate internal JWT authorization code
Server->>Client: Authorization complete (internal code)
Client->>Server: POST /token (internal code + PKCE verifier)
Note over Server: Verify PKCE challenge/verifier
Server->>IdP: Exchange IdP code for access token
IdP->>Server: Access token
Server->>Client: Access token
Client->>Server: POST /mcp (with Bearer token)
Server->>Client: MCP response
The following environment variables are required for OAuth2.1 support:
Your IdP must support the following OAuth features:
Note: PKCE verification is handled internally by the MCP Server between MCP Client and MCP Server (per MCP specification). The IdP does not need to support PKCE.
search_finding - Search RISKEN findings. (Supports both Organization and Project tokens)
finding_id - Search by finding ID.alert_id - Search by alert ID. (Project token only)data_source - Search by data source.resource_name - Search by resource name.from_score - Search by minimum score.
0.0 ~ 0.3 - Low0.3 ~ 0.6 - Medium0.6 ~ 0.8 - High0.8 ~ 1.0 - Criticalstatus - Search by status.
0 - All1 - Active (default)2 - Pendingoffset - Search by offset.limit - Search by limit.archive_finding - Archive RISKEN finding. (Supports both Organization and Project tokens)
finding_id - Archive by finding ID. (Required)note - Note.status - Search by status.
1 - Active2 - Pending3 - Deactive (already closed)finding://{project_id}/{finding_id}project_id: The ID of the project.finding_id: The ID of the finding.This project is licensed under the MIT License. See the LICENSE file for details.
Tools
No tool list yet. Remote servers get one after the first health check.
FAQ
Copy the stdio config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.
No required environment variable is listed on this record.
Risken runs locally over stdio.
Last checked 2026-10-28. RISKEN's official MCP Server