NewCore vs TrueFoundry
| Criterion | NewCore | TrueFoundry | NewCore reason | TrueFoundry reason |
|---|---|---|---|---|
| G1 Identity-bound per-call authorization (25) | 10 | 6 | Every tool call passes through the gateway, which identifies the agent and the person behind it and checks the action against policy, keeping agents within that person's permissions. [nc-secure] | RBAC policies apply per MCP server and per user and tool, but per-call checks against the person an agent acts for are not described. [tf-mcp] |
| G2 Credential brokering (20) | 10 | 4 | Access is short-lived and task-scoped, and the agent never holds the tool's own credential. [nc-secure] | Centralized authentication is described, but brokering short-lived credentials was not. [tf-mcp] |
| G3 Human approval and escalation (15) | 10 | 2 | Policies return allow, ask or deny; risky calls go to a named approver who confirms with device biometrics, and an agent can never approve its own action. [nc-govern] | No human approval step was found. [tf-mcp] |
| G4 Server registry and discovery (10) | 8 | 7 | A connection registry records each MCP server's endpoint, owner and environment, and agents are found through read-only integrations without relying on registration. [nc-secure][nc-discover] | An MCP Server Registry and discovery portal manages the server inventory. [tf-mcp] |
| G5 Audit evidence (10) | 9 | 6 | Tool calls, sessions and approvals sit in one audit trail with each call logged against its owner; a SIEM export was not named on the pages read. [nc-govern] | Audit logging for compliance is described; SIEM export was not confirmed. [tf-mcp] |
| G6 Standards (10) | 5 | 5 | MCP, SAML and OIDC are named; OAuth 2.1 and Enterprise-Managed Authorization are not named on the pages read. [nc-foundation] | Federated SSO through Okta and Azure AD and OAuth 2 are named; MCP authorization specifics were not. [tf-mcp] |
| G7 Deployment and buying clarity (10) | 4 | 6 | Delivered as SaaS with no list price; an AWS Marketplace listing exists and no free tier or self-host option was found. [nc-aws] | A free start and a pricing page are linked; self-hosting terms were not confirmed. [tf-mcp] |
| Total | 8.60 | 5.00 | Weighted sum divided by 100. | |
In short: NewCore totals 8.60 and TrueFoundry totals 5.00 on our weighted rubric, a gap of 3.60 points. NewCore is ahead on per-call authorization, credential brokering, human approval, registry and audit. TrueFoundry is ahead on deployment. Choose by the criteria your agents depend on, then check deployment and pricing below.
Which one should I choose?
NewCore totals 8.60 against 5.00 for TrueFoundry. The largest weighted difference is on credential brokering. TrueFoundry is ahead on deployment.
Pick NewCore if credential brokering matters most to you.
It scores 10 against 4 there: access is short-lived and task-scoped, and the agent never holds the tool's own credential.
Pick TrueFoundry if deployment matters most to you.
It scores 6 against 4 there: a free start and a pricing page are linked; self-hosting terms were not confirmed.
How do deployment and pricing compare?
| Parameter | NewCore | TrueFoundry |
|---|---|---|
| Deployment | SaaS. Works alongside an existing AI gateway, and the current identity platform keeps handling employee sign-in. | SaaS platform. |
| Price as published | No list price published. Listed on AWS Marketplace. | Free start offered; detailed pricing on the vendor's pricing page. |
| Identity provider | Yes. NewCore says to start alongside your identity platform, which keeps handling employee sign-in while NewCore governs agent access. | Yes. Federated login through Okta, Azure AD or custom SSO is supported. |
Full datasheets: NewCore and TrueFoundry MCP Gateway.
Frequently asked questions
- Which is better, NewCore or TrueFoundry?
- On our rubric NewCore totals 8.60 against 5.00 for TrueFoundry. The better choice depends on which criteria matter most to you.
- Do NewCore and TrueFoundry work with my identity provider?
- NewCore: Yes. NewCore says to start alongside your identity platform, which keeps handling employee sign-in while NewCore governs agent access. TrueFoundry: Yes. Federated login through Okta, Azure AD or custom SSO is supported.
- How do NewCore and TrueFoundry differ on price?
- NewCore: No list price published. Listed on AWS Marketplace. TrueFoundry: Free start offered; detailed pricing on the vendor's pricing page.
By The Datasheet desk · Published and reviewed 2026-11-03