"How to use the terminal" matching MCP servers:

A secure terminal execution server that enables controlled command execution with security features and resource limits via the Model Context Protocol (MCP).

Safety middleware for AI computer use agents that monitors, enforces policies, and provides guardrails to enable safe desktop interaction.

Demonstrates Agent Passport System pre-dispatch authorization by issuing one-use grants and verifying signed authorization envelopes before proxied tool calls reach the upstream server.

Routes web requests from AI tools through Tor for anonymized fetching, with selective per-URL routing to bypass Tor-blocking sites.

Read-only ProofRelay MCP verifier for non-confidential evidence bundles. Exposes 22 public-safe tools, 11 resources, and 11 prompts for bundle integrity checks, receipt-chain review, checkpoint recommendations, MCP risk metadata review, and real-estate closing proof-pack readiness.

An MCP front-end for AnB. The tool surface is "use-don't-reveal": no tool returns a plaintext secret. Reveal paths require a TTY the server doesn't have, so the no-reveal guarantee is structural, not prompt-based — it holds even against a prompt-injected agent. Runs as a dedicated, narrowly-scoped AnB identity; exec is default-deny (only allowlist rules tagged scope=mcp run); command output

Enables AI agents to securely use real secrets (API keys, database passwords) by requiring human approval for each release, ensuring secrets never enter the model's context.

Scans suspicious messages, URLs, and text for scams inside any MCP-compatible AI assistant. No signup or API key needed for anonymous use.

MCP server to easily use compliance-trestle for OSCAL compliance workflows from any MCP-compliant client.

Runs a regular expression on real engines — JavaScript (V8), Python (CPython re), PCRE2 and RE2 — reporting each engine's own compile errors with positions, every match with its groups and named groups, replacement results, and where the engines disagree. It also detects catastrophic backtracking (ReDoS), naming the at-risk part of the pattern, generating an attack string, and timing how long each engine actually takes on it.

Enables AI agents to securely manage local credentials, obtain short-lived tokens for authenticated API access, and audit every use by purpose.

Provides DNS lookup and email authentication diagnostic tools (SPF, DKIM, DMARC, MX, etc.) for use with MCP-compatible clients. Enables natural language queries to check DNS records and email health.

MCP server that integrates the Phylax verification API, enabling AI assistants to verify packages, repositories, and other MCP servers before use. It exposes tools for verifying artifacts, checking policies, and fetching attestations.

Local-first MCP proxy with BM25 tool discovery, quarantine security, Docker isolation, OAuth support, activity logging, and web UI. Routes multiple upstream MCP servers through a single endpoint.

Enables AI agents to publish text and link posts, comment, react, and delete posts on LinkedIn through the official OAuth API, with every write gated behind human approval via a two-phase prepare/execute flow. Includes exact-match digests, single-use expiring proposals, daily write caps, and private local token storage with zero third-party dependencies.

Terminal-native DOM perception layer for AppSec and AI. Hook into live Chrome sessions, compress HTML tokens by 98.9%, and map attack surfaces deterministically.

An MCP bridge for ProphetKey, an offline-first encrypted API key vault for AI agents. Use one of the 5 prophetkey_* tools to inject real API keys through a local proxy — agents only ever see safe_key identifiers, never the real provider keys.

Security for the MCP servers you use: detects tool poisoning, rug pulls, shadowing, secrets and supply-chain risk (OWASP MCP Top 10), with runtime guards and approved-server policy. Runs locally.

Enables AI agents to use corporate card and expense functions, including balance checks, transaction listing, receipt compliance, expense reporting, and approval workflows, by calling existing REST APIs through a governed gateway with identity, policy, and audit controls.

Exposes user, membership, and role administration tools via MCP, acting as a thin passthrough to a coordinator API with RBAC enforced by the coordinator using caller bearer tokens.