"How to use make.com" matching MCP servers:

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.

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.

Audits Make.com scenario blueprints before import, checking for hardcoded secrets, dangling references, plain-HTTP URLs, and other issues. Provides tools to inspect blueprint structure, trace module mappings, and generate a safety findings report.

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

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.

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.

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.

A secure email gateway MCP server that protects AI agents from prompt injection attacks by scanning emails for malicious instructions before they reach the agent.

A demonstration server that reveals security risks by accessing sensitive environment variables, illustrating how MCP tools can potentially leak user data without explicit consent.

A local-first secrets vault for MCP clients that lets AI assistants use secrets by injecting them into child processes, without the plaintext ever entering the model's context.

Exposes verification and safety tools to MCP clients, enabling text and agent-output hallucination checks, computer-use action risk grading, and prompt-injection, jailbreak, harmful-content, sensitive-data, and fraud screening through an authenticated proxy.

Enables action-bound authorization and verifiable evidence contracts for MCP tool execution, offering deterministic action planning, policy decisions, and one-use capability tokens tied to exact action envelopes.