"A tool for running code in a REPL-like environment" matching MCP servers:

MCP server enabling Claude Code to capture screenshots of Windows applications through WSL2, allowing AI to diagnose UI errors and verify layouts.

Enables AI agents to call tools through a security gateway that intercepts requests, enforces deterministic policy and risk checks, blocks or escalates high-risk actions for human approval, and keeps tool credentials and audit logs protected.

Enables AI agents to request an independent second opinion from a different frontier model, with PII scrubbing before transit, live web search grounding, caching, and multi-provider failover.

This MCP server provides secure access to databases for AI agents, enforcing authentication, authorization, human approval, logging, and notifications to prevent dangerous actions.

Governed MCP server for bank-grade agent tool access with RBAC, PII redaction, rate limiting, and audit logging.

Checks a code repository without running it: Safe, Works and Complete scores with an A-F grade, catching leaked keys, dangerous calls, invented or lookalike packages, broken imports and missing project files. Standard-library Python; MCP tools scan, orphans and explain.

Enables centralized proxy and orchestration of MCP servers, providing unified tool discovery, authentication, and secure request routing. It adds a human-in-the-loop approval gate for high-risk actions and audit logging.

Provides agent certification and trust verification tools for AI agents, enabling certification checks, trust score calculations, audit ticket issuance, and emergency kill switch activation through the A-SOC trust network.

A secure tool-execution plane for agentic AI that enforces JWT authentication, rate limiting, prompt-injection inspection, and audit logging, while ingesting downstream OpenAPI endpoints as MCP tools.

Protects AI agents from bad tool outputs, schema mismatches, and tool poisoning by validating, sanitizing, and scoring reliability of tool responses.

Enables AI agents to securely discover, invoke, and manage tools through a hardened MCP endpoint with protections like injection detection, circuit breakers, retry backoff, response caching, context-window limiting, and state snapshots.

Enables MCP tool handlers to be declared with a decorator, collected into a registry from a config map, and served over a bearer-token-authenticated Streamable HTTP ASGI app. Tools can also be invoked in-process without running any HTTP server.

Enables AI agents to manage VPN infrastructure through provisioning, lifecycle control, traffic routing, and health monitoring.

Strict AI code reviewer powered by Groq. Finds bugs, vulnerabilities and security issues in your code. Supports analyze, compare versions, explain code, generate tests, and HTML reports.

A security filter that blocks dangerous code patterns by comparing normalized structural syntax trees against a blacklist of known threats using vector embeddings. It acts as a gatekeeper to prevent malicious code execution by identifying dangerous structures regardless of specific identifiers or literals.

Enables agents to check third-party tool licenses, validate vendor policies, and issue license receipts before using external tools.

Enables declaring a catalog of tools for LLMs, filtering them by role, validating arguments, guarding sensitive calls with server-side confirmations, and recording an audit log.

MCP server providing a searchable security knowledge base for AI coding assistants, enabling retrieval of secure-coding instructions and feature-specific security guidance.

Enables a sandboxed Claude Code session to see editor selections, review proposed edits as VS Code diffs, and read workspace diagnostics through an MCP-over-WebSocket IDE bridge.

Enables executing arbitrary Joern/CPGQL queries against a loaded Code Property Graph, loading source code in multiple languages (PHP, Java, JavaScript, Python, C/C++) to build new CPGs, and inspecting loaded projects and the active workspace. It communicates with a running Joern server over its synchronous HTTP query endpoint, so no state polling is required.