UpGuard CyberRisk MCP Server

Created By
leroylima year ago
Node.js MCP server for UpGuard CyberRisk API integration. Provides comprehensive cybersecurity risk assessment tools with stateless HTTP transport, caching, and resilience patterns.
Overview

What is UpGuard CyberRisk MCP Server?

UpGuard CyberRisk MCP Server is a Node.js server designed for integrating with UpGuard's CyberRisk API, providing tools for comprehensive cybersecurity risk assessment and management.

How to use UpGuard CyberRisk MCP Server?

To use the server, clone the repository, install dependencies, configure your UpGuard API credentials in a .env file, and run the server using Node.js.

Key features of UpGuard CyberRisk MCP Server?

  • 67 API tools across 13 categories for security management
  • Real-time risk assessment and vendor monitoring
  • Automated documentation generation in multiple formats
  • Interactive API explorer with Swagger UI
  • Comprehensive schema validation with Zod

Use cases of UpGuard CyberRisk MCP Server?

  1. Conducting risk assessments for vendors and assets.
  2. Generating compliance reports automatically.
  3. Monitoring security breaches in real-time.
  4. Managing large-scale asset operations efficiently.

FAQ from UpGuard CyberRisk MCP Server?

  • What are the prerequisites for using the server?
    You need Node.js 18+, npm or yarn, and UpGuard CyberRisk API credentials.

  • Is there a documentation available?
    Yes, comprehensive documentation is generated and available in multiple formats.

  • Can I contribute to the project?
    Yes, contributions are welcome! Fork the repository and submit a pull request after making your changes.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
leroylim
Star
1
Language
JavaScript
License
MIT license

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

16 hours ago