Security & trust

Your engineering data deserves better than a marketplace.

Every server is built and operated by our team — across ForgeMCP and FlowGuideAI, the same company. No marketplace, no external submissions, no supply-chain surprises in your Claude session. The few open-source components we use are highly reputable and fully audited before they ship.

Core commitments

Three commitments that never change

Owner-operated — no marketplace, no surprise code

Every tool and every deployment is ours, built and operated by our team. No marketplace, no community submissions, no surprise dependencies inside your Claude session. Where a tool relies on open source — currently only the Symbolic Math engine — we choose a highly reputable project, fully audit it, and run it on our own infrastructure. Everything else, we wrote.

Audit-ready infrastructure

Your engineering data passes through infrastructure we control and audit end-to-end. Full MCP server source code is available for review by Enterprise customers on request. Every call is logged and attributable.

Our controls are designed to align with SOC 2. We have not yet completed an independent SOC 2 audit; we run a full security review of the platform every quarter.

✓ SOC 2-aligned · quarterly security reviews

Hosted isolation · Enterprise VPC

Hosted plans (Solo, Engineer, Team, Business) run on isolated compute per workspace — no shared compute, no cross-tenant access. Enterprise adds VPC / BYO deployment: ForgeMCP runs inside your own infrastructure, credentials never leave your environment.

Infrastructure details

What we control and audit

Encryption

All data in transit uses TLS 1.3. Credentials are stored as OAuth token references — we never store raw vendor passwords. MCP session data is encrypted at rest using AES-256. Backups are encrypted with separate key material.

Authentication

All accounts support passkeys (FIDO2 / WebAuthn), four OAuth providers (Google, Microsoft, GitHub, Apple), TOTP 2FA, and backup codes. Enterprise adds SAML 2.0 SSO + SCIM 2.0 + OIDC with IdP-enforced MFA — no double-prompt for your engineers.

Audit logging

Business and Enterprise plans receive full audit logs: who called which tool, when, with what parameters, and what was returned. Logs are immutable and exportable. Enterprise audit logs are retained for 12 months.

Source review (Enterprise)

Enterprise customers can request a full source code review of any ForgeMCP MCP server under NDA. We walk your security team through the implementation, the data flow, and the infrastructure configuration. This is a standard Enterprise onboarding step.

Why not a marketplace?

The risks we eliminate by staying first-party

Prompt injection via tool descriptions
Malicious community servers can embed instructions in their tool descriptions that hijack your Claude session. We never allow external tool descriptions on our infrastructure.
Credential theft via tool implementations
A malicious tool implementation can silently exfiltrate credentials passed to it. Every tool we ship is code we wrote and can trace.
Supply-chain compromise
Community-built servers bring their own dependency trees. A compromised npm package in an MCP server becomes your problem. We control our entire dependency stack.
Reputational & regulatory exposure
One bad third-party server affects every customer on the platform. We cannot accept that liability, and neither can your legal or compliance team.

Working specifically with CAD data? See CAD AI security for a checklist tailored to connecting an assistant to CAD models and BOMs, and local bridge architecture for how the desktop connectors keep that data on your machine.

Questions about our security posture?

Enterprise customers can schedule a security review call. We walk your team through implementation, data flow, and infrastructure — under NDA.

Contact security team →