MCP for Copilot Start hereDirectorySkillsStandardsLearnMethodologySubmit / Get featuredNewsletter

← Directory

Invitt: Invitations, RSVPs, Planning

Plan an event in chat: venue ideas, RSVP deadline and past events, then email invites and RSVPs.

likely compatible

OAuth with discovery metadata and Dynamic Client Registration; use OAuth 2.0 → Dynamic discovery.

Rule R2c · what this means · Not tested in Copilot Studio.

Registry namenet.invitt/invitt
Endpoint used for verdicthttps://agent.invitt.net/mcp
Transportsstreamable-http
Auth (Copilot Studio setting)OAuth 2.0 – Dynamic discovery
Last endpoint check2026-10-23T22:51:20Z · HTTP 401
GitHubarnaudgrunwald0404/invitt-plugin
Websitehttps://invitt.net
Version1.0.0
Registry updated2026-10-22

Standards signals

Official MCP RegistryListed (active)
MCP Registry
server.json schema2025-12-11 · current
server.json schema changelog
TransportStreamable HTTP (remote)
Transports: Streamable HTTP
Answers MCPNeeds sign-in, so not checked
Lifecycle: initialization
RFC 9728 protected resource metadataPublished
Authorization: RFC 9728 metadata
Client ID Metadata DocumentsNot advertised
Client registration: CIMD
RFC 9207 issuer in responsesNot advertised
Authorization: RFC 9207 iss
Spec version spokenNot observed
Versioning
Supports 2026-07-28Not checked (needs sign-in)
server/discover

Observed from public registry data and a read-only, unauthenticated check on 2026-10-23. Not a certification: AAIF and the MCP project don't certify servers, and these lines are signals, not pass/fail. They don't change the Copilot Studio verdict. Own this server? modelcontextprotocol/conformance: test your own server.

All standards signals

Track changes like this weekly. New Copilot-ready MCP servers, breakages and auth changes, in one short email.
Is this wrong or out of date? Email us. Data built 2026-10-24.