InsForge
InsForge is an MCP server published by InsForge, verified on MCP revision 2025-11-25; support for the current revision (2026-07-28) is not yet confirmed. Last verified 2026-08-20.
Does InsForge support the current MCP specification (2026-07-28)?
Not yet confirmed. InsForge is verified on revision 2025-11-25; we have not confirmed support for the current revision (2026-07-28) as of 2026-08-20.
Is InsForge a first-party (official) MCP server?
Undetermined. We have not verified the publisher relationship for InsForge (as of 2026-08-20).
How do I connect to InsForge?
InsForge is available via a hosted remote endpoint at https://mcp.insforge.dev/mcp, the package npm:@insforge/mcp, the official MCP Registry under io.github.InsForge/insforge-mcp, the source repository at https://github.com/insforge/insforge-mcp. Authentication: oauth. Transports: streamable-http.
Does InsForge support MCP revision 2025-11-25?
Yes. InsForge supports MCP revision 2025-11-25 (checked 2026-08-20).
Does InsForge support MCP revision 2026-07-28?
No. InsForge was checked against MCP revision 2026-07-28 and does not support it (checked 2026-08-20).
When were InsForge's facts last verified?
2026-08-20. Each fact on this page links to the sources used to verify it.
MCP server for InsForge BaaS - database, storage, edge functions, and deployments
Which MCP spec revisions does InsForge support?
InsForge has 2 verified spec-support records. Each row lists the revision, the verified status, the evidence URL, and the date that fact was last checked.
| Spec revision | Status | Last checked | Evidence |
|---|---|---|---|
| MCP 2025-11-25 | Supported | Source | |
| MCP 2026-07-28 | Not supported | Source |
How widely adopted is InsForge?
Ranked #240 in The MCP 500 with Adoption Index 49.63 (snapshot , methodology v1).
| Measurement | Value | Source |
|---|---|---|
| Official MCP Registry | yes | API · |
| Docker MCP Catalog | no | API · |
| npm downloads (weekly) | 544 | API · |
| GitHub stars | 35 | API · |
| GitHub forks | 13 | API · |
| Last push | 2026-09-10T17:40:28Z | API · |
| Repository archived | no | API · |
Repository and package signals for InsForge
Measured directly from the source registries, not asserted from a document. Each figure carries the date it was read; none of it affects the verified spec status above.
Repository as of
- Created
- Open issues
- 14
- Primary language
- TypeScript
- License (repository)
- Apache-2.0
- Continuous integration
- Present
- Tests
- Present
- Security policy
- None
Package (npm) as of
- Latest version
1.2.11- Last published
- First published
- Releases
- 78
- License (package)
- Apache-2.0
- Maintainers
- 5
- Direct dependencies
- 11
- Unpacked size
- 220 KB
- Registry signature
- Signed
- Build provenance
- No attestation
How was this verified, and what are the sources?
Verified · method: sdk-protocol-constant
· confidence 0.85 (Good).
- Official MCP Registry record for io.github.InsForge/insforge-mcp at version 1.2.6 - lists remote endpoint https://mcp.insforge.dev/mcp and repository https://github.com/insforge/insforge-mcp - accessed
- Endpoint probe of https://mcp.insforge.dev/mcp - authorization required on initialize (HTTP 401) - accessed
- npm registry metadata for @insforge/mcp at published version 1.2.11, retrieved 2026-08-20 - declares a dependency on @modelcontextprotocol/sdk, which resolves to @modelcontextprotocol/sdk@1.30.0 - accessed
- Published artifact of @modelcontextprotocol/sdk@1.30.0, retrieved 2026-08-20 - the artifact declares LATEST_PROTOCOL_VERSION 2025-11-25 and carries no 2026-07-28 implementation. Read from the artifact itself, not from release notes - accessed