BootForm
Form backend for static sites: create forms, add email or Discord notifications, read submissions.
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 name | com.bootform/bootform |
| Endpoint used for verdict | https://mcp.bootform.com/mcp |
| Transports | streamable-http |
| Auth (Copilot Studio setting) | OAuth 2.0 – Dynamic discovery |
| Last endpoint check | 2026-10-23T22:51:13Z · HTTP 401 |
| Website | https://bootform.com/docs/mcp-and-ai-agents |
| Version | 1.0.0 |
| Registry updated | 2026-10-22 |
Standards signals
| Official MCP Registry | Listed (active) MCP Registry |
| server.json schema | 2025-12-11 · currentserver.json schema changelog |
| Transport | Streamable HTTP (remote) Transports: Streamable HTTP |
| Answers MCP | Needs sign-in, so not checked Lifecycle: initialization |
| RFC 9728 protected resource metadata | Published Authorization: RFC 9728 metadata |
| Client ID Metadata Documents | Advertised by the authorization server Client registration: CIMD |
| RFC 9207 issuer in responses | Advertised Authorization: RFC 9207 iss |
| Spec version spoken | Not observed Versioning |
| Supports 2026-07-28 | Not 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.
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.