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 an agent to drive a real browser while enforcing provenance-based gating so URLs and form values must trace to the user or an allowlist, never to untrusted page content.
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.
Enables AI agents to interact with Home Assistant through tiered, human-gated access: free reads and reversible comfort controls, while sensitive actions like locks, alarm, covers, and climate changes require per-operation human approval via Matrix.
Enables any agent to drive a dedicated Chromium instance through MCP, including opening and reading pages, taking steps, logging in via a password vault, downloading/uploading files, and replaying saved routines. It also gates sensitive actions behind approvals and can use client certificates or one-time card data for official procedures.
This MCP server provides secure access to databases for AI agents, enforcing authentication, authorization, human approval, logging, and notifications to prevent dangerous actions.
Enables secure browser automation by letting agents fill Turnkey-stored secrets into web forms without the secret values ever appearing in the conversation, transcript, or model context.
Read-only observation of a single live URL: parses static HTML to report security posture, forms, links, accessibility signals, and leaks, with described fixes. SSRF-gated and safe, never executes JavaScript.
Enables AI agents to drive a self-hosted Chromium through MCP tools for opening pages, reading content, taking screenshots, clicking, filling forms, and triggering final submissions, while a human watches the same browser live and can take over for logins or captchas. Server-side guardrails enforce per-session domain allowlists and denylists, refuse password, payment card, IBAN and one-time-code fields, isolate each token in its own browser context, and route submits, payments and orders through a separate final-action tool that can require human approval.
MCP server acting as a credential vault and browser execution broker, letting AI agents perform browser tasks (login, scraping, etc.) without exposing raw credentials, with per-tab billing and a monitoring UI.
An MCP server that gives AI clients controlled access to a real headless browser with domain allowlisting, SSRF protection, per-session isolation, audit logging, and persistent cookies/state across restarts.
Enables users to deploy a minimal Model Context Protocol server on Render, connect MCP clients with bearer-token authentication, and add custom tools callable through the MCP endpoint.
Enables deployment and connection to a minimal Streamable HTTP MCP server with bearer-token authentication, a health endpoint, and an example tool, while allowing developers to add custom tools.
Enables ZenTao user administration, including token retrieval, user queries, and user creation/update/delete, over stdio or Streamable HTTP transports.
Provides Copilot Studio with six tools for secure workspace file operations and one-time execution of pre-approved Python jobs in isolated, network-less Docker containers, with strict access controls and audit logging.
Provides AI assistants with specialized tools to interact with NIST's Open Security Controls Assessment Language (OSCAL) framework. It enables agents to retrieve schemas, explore models, and generate valid OSCAL documentation for security compliance automation.