Trusted GMail MCP Server

Created By
0xfreysaa year ago
First Trusted MCP server running on AWS Nitro Enclave Trusted Execution Environment
Overview

What is Trusted GMail MCP Server?

Trusted GMail MCP Server is a secure email server running on AWS Nitro Enclave, designed to enhance the security of email communications through the Model Context Protocol (MCP).

How to use Trusted GMail MCP Server?

To use this server, you need to create an app-specific password from your Google account and configure your client's mcp.json file with the provided URL format.

Key features of Trusted GMail MCP Server?

  • Operates within a secure AWS Nitro Enclave for enhanced security.
  • Supports remote MCP server connections using SSE transport.
  • Provides a proof of concept for secure email handling.

Use cases of Trusted GMail MCP Server?

  1. Securely handling email communications in sensitive environments.
  2. Testing and developing applications that require secure email interactions.
  3. Running personal instances for enhanced privacy and security.

FAQ from Trusted GMail MCP Server?

  • Is this server secure?

Yes, it runs in a secure AWS Nitro Enclave, but users should be cautious with app-specific passwords in URLs.

  • Can I run my own instance?

Yes, instructions are provided to set up your own instance in a TEE.

  • What is the MCP?

The Model Context Protocol (MCP) is a protocol designed for secure communication between applications.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
0xfreysa
Star
0
Language
TypeScript
License
-
Tags

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
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
Voyei

6 hours ago