"Security testing, penetration testing, and code auditing services" matching MCP servers:

MCP server that gives AI agents direct access to Google services including Gmail, Calendar, Drive, and more, with multi-account OAuth support. Enables reading and sending email, managing calendar events, and interacting with Google files through natural language.

Enables scheduling and todo management via MCP, allowing users to add reminders, view tasks, and mark completion through natural language.

Enables interaction with multiple Google services including Maps, Finance, Flights, Gmail, and Calendar through a unified interface. Provides comprehensive access to geocoding, stock data, flight information, email management, and calendar operations.

Enables comprehensive Google Meet and Calendar management through Google Calendar API v3 and Google Meet API v2, supporting calendar event creation with Meet links, space management, transcription, recording, attendance tracking, and meeting moderation controls.

Provides read-only access to Google Drive meeting transcripts and Google Calendar events, enabling AI assistants to search, analyze, and retrieve meeting insights.

Provides access to Google Sheets, Gmail, and Google Calendar through 13 tools that enable reading/writing spreadsheet data, managing emails, and creating/updating calendar events.

MCP server for Claude Desktop providing access to Google Sheets, Gmail, and Google Calendar.

Lets Claude read and manage your iCloud Reminders and Calendar through a custom MCP connector, enabling natural language queries and actions.

MCP server demonstrating elicitation for booking appointments and an interactive MCP App for viewing appointments with SQLite persistence.

Gives time-blind LLMs and agent frameworks a real clock: current time and timezone, elapsed task duration, countdowns to deadlines, timezone conversion, session heartbeats, cron-style due checks, and session-level timers. This lets locally hosted or self-built models stop hallucinating the time and actually perceive how long a task or conversation has been running.

Enables an AI agent to discover and call bounded Microsoft 365 tools for reading calendar, mail, Teams channels, SharePoint, and Power Platform metadata through MCP, with synthetic fixtures by default and optional Microsoft Entra/Graph tenant integration.

Enables AI agents to manage spa/wellness operations via Zenoti API, including appointments, guests, services, and billing.

NodeCodeStudio is a hybrid MCP implementation that lets AI agents activate and manage tools like Gmail, Google Calendar, WordPress, Asana and more through a unified interface. It also includes a Browser MCP extension with ready-made automations like LinkedIn jobs and price searches.

Exposes vaccination-appointment scheduling as standardized MCP tools backed by an in-memory mock backend. Enables agents to list available slots by date and vaccine type, book appointments, check confirmation status, and cancel bookings.

Enables AI assistants to interact with Fastmail services, providing tools for comprehensive email management, contact searching, and calendar event coordination via the JMAP API. It supports advanced features like threaded conversations, attachment handling, and bulk mailbox operations through natural language.

MCP server for the Crown Town Compost customer portal that lets you check pickups, invoices, and upcoming collections, skip services, report missed pickups, and update account details through natural language.

Read-only MCP server for Gingr pet-care facility data, enabling queries about owners, animals, reservations, appointments, services, and staff via natural language.

Enables AI assistants to manage Microsoft 365 services like Outlook, Calendar, OneDrive, and Contacts through natural language commands, with support for multi-account and high-performance caching.

A local MCP server that enables multi-account read-only access to Google Workspace services such as Gmail, Calendar, and Drive through named profiles.

Enables AI clients to inspect and control a Home Assistant instance over its REST API using a long-lived access token, reading entity states, services, history, logbook, error logs, and calendars, rendering Jinja2 templates, and calling services, firing events, or setting and deleting states, with a generic API escape hatch for other endpoints.