{"passport":{"unfragile":{"@version":"1.0","version":"2026-05","artifact":{"id":"smithery_omd01-aws-ses-mcp","slug":"omd01-aws-ses-mcp","name":"AWS SES Email Sender","type":"mcp","url":"https://smithery.ai/servers/omd01/aws-ses-mcp","page_url":"https://unfragile.ai/omd01-aws-ses-mcp","categories":["mcp-servers","app-builders"],"tags":["mcp","model-context-protocol","smithery:omd01/aws-ses-mcp"],"pricing":{"model":"open_source","free":true,"starting_price":null},"status":"active","verified":false},"capabilities":[{"id":"smithery_omd01-aws-ses-mcp__cap_0","uri":"capability://tool.use.integration.seamless.email.composition.and.dispatch","name":"seamless email composition and dispatch","description":"This capability allows users to compose and send emails directly from applications using AWS SES by integrating with Cursor or Claude Desktop. It employs a model-context-protocol (MCP) architecture to facilitate real-time email creation and dispatch without manual copy-pasting, ensuring that the email content is dynamically generated based on user input and context. The integration with these platforms allows for a streamlined workflow that enhances productivity and reduces friction in email management.","intents":["How can I send emails directly from my application without manual intervention?","What is the best way to integrate email dispatch into my existing workflow?","Can I automate email sending with custom content using AWS SES?"],"best_for":["developers looking to automate email workflows in their applications"],"limitations":["Requires a valid AWS account with SES setup; email sending limits apply based on account status."],"requires":["AWS account with SES access","Cursor or Claude Desktop integration"],"input_types":["text"],"output_types":["text"],"categories":["tool-use-integration","productivity"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"smithery_omd01-aws-ses-mcp__cap_1","uri":"capability://tool.use.integration.customizable.sender.address.management","name":"customizable sender address management","description":"This capability enables users to specify custom sender addresses for outgoing emails, leveraging AWS SES's features. The implementation uses a configuration management approach to allow users to define multiple sender identities, ensuring that emails can be sent from different addresses based on the context or recipient. This flexibility is crucial for businesses that need to manage communications from various departments or services.","intents":["How can I send emails from different sender addresses based on context?","What is the best way to manage multiple sender identities in my application?","Can I customize the sender address for each email I send?"],"best_for":["teams managing multiple communication channels"],"limitations":["Custom sender addresses must be verified in AWS SES before use."],"requires":["AWS SES verified sender addresses"],"input_types":["text"],"output_types":["text"],"categories":["tool-use-integration","email-management"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"smithery_omd01-aws-ses-mcp__cap_2","uri":"capability://tool.use.integration.cc.and.bcc.email.functionality","name":"cc and bcc email functionality","description":"This capability supports the inclusion of CC (carbon copy) and BCC (blind carbon copy) recipients in emails sent via AWS SES. It utilizes a structured approach to manage recipient lists, allowing users to specify multiple CC and BCC addresses while ensuring compliance with email standards. This feature enhances communication by allowing users to keep stakeholders informed without revealing all recipients' addresses.","intents":["How can I include multiple recipients in my email without exposing their addresses?","What is the best way to manage CC and BCC in my email sending process?","Can I automate the addition of CC and BCC recipients in my emails?"],"best_for":["developers needing to manage complex email recipient lists"],"limitations":["Maximum recipient limits imposed by AWS SES apply."],"requires":["AWS SES account"],"input_types":["text"],"output_types":["text"],"categories":["tool-use-integration","email-management"],"confidence":0.5,"matches":0,"success_rate":0}],"trust":{"score":28,"verified":false,"data_access_risk":"high","permissions":["AWS account with SES access","Cursor or Claude Desktop integration","AWS SES verified sender addresses","AWS SES account"],"failure_modes":["Requires a valid AWS account with SES setup; email sending limits apply based on account status.","Custom sender addresses must be verified in AWS SES before use.","Maximum recipient limits imposed by AWS SES apply.","builder identity is not verified yet","no observed match outcomes yet"],"rank_breakdown":{"adoption":0.05,"quality":0.31,"ecosystem":0.49000000000000005,"match_graph":0.25,"freshness":0.5,"weights":{"adoption":0.25,"quality":0.25,"ecosystem":0.15,"match_graph":0.23,"freshness":0.12}},"observed_outcomes":{"matches":0,"success_rate":0,"avg_confidence":0,"top_intents":[],"last_matched_at":null},"maintenance":{"status":"active","updated_at":"2026-05-24T12:16:27.443Z","last_scraped_at":"2026-05-03T15:18:42.145Z","last_commit":null},"community":{"stars":null,"forks":null,"weekly_downloads":null,"model_downloads":null,"model_likes":null}},"distribution":{"claim_url":"https://unfragile.ai/submit?claim=omd01-aws-ses-mcp","compare_url":"https://unfragile.ai/compare?artifact=omd01-aws-ses-mcp"}},"signature":"qUWK7slfS8jA7P0qyiSN0F2aTVuJKL50G7OgTkAlTDfXK44HdmKSzxAGwaumn1J5zz8p7cFimMwOL5LQKal+CQ==","signedAt":"2026-06-23T07:59:44.624Z","signedBy":"unfragile.ai","version":1},"_links":{"self":"https://unfragile.ai/api/v1/passport/omd01-aws-ses-mcp","artifact":"https://unfragile.ai/omd01-aws-ses-mcp","verify":"https://unfragile.ai/api/v1/verify?slug=omd01-aws-ses-mcp","publicKey":"https://unfragile.ai/api/v1/trust-passport-public-key","spec":"https://unfragile.ai/trust","schema":"https://unfragile.ai/schema.json","docs":"https://unfragile.ai/docs"}}