Elva

What it is

Elva (getelva.ai) sits between your codebase and the consumers of your APIs — humans, partners, and AI agents. Verified from their site (2026-09-22): it discovers endpoints from repo code (OpenAPI not required up front), scores design/security/AI-readiness, lets you define per-audience contracts (fields, PII exclusion, approval gates), and can host MCP servers with OAuth, per-tool scopes, and call logs. Free plan marketing lists 1 repo and 1,000 tool calls/month; paid Startup/Business tiers are listed on the FAQ. Built by Theneo.

It is explicit that Elva is not your runtime API gateway for ordinary HTTP — except for MCP, where they host and gate the server themselves.

Who it’s for

Teams shipping agent-facing APIs who need a catalog + contract + MCP gateway without hand-maintaining five OpenAPI forks. Startups through enterprises show up in their security FAQ (SSO/SCIM, SOC2/ISO on infrastructure). Solo makers with one public API and no partners may find it heavy; a hand-written MCP server can still be enough for a weekend ship.

Why we listed it

Product Hunt launch 2026-09-14, live URL verified 2026-09-22. Clear maker angle: turn a repo into governed MCP tools without pretending Postman is a system of record. Matches the agent-era pain we keep seeing on this board.

Caveats

Enterprise certifications and SLA language are vendor claims — ask for the report pack if that’s your buy bar. Hosted MCP means auth and logs live on their infra (or your VPC/on-prem per their deploy options); design threat models accordingly. Pricing and call quotas change — confirm on their site the day you budget. We haven’t load-tested their discovery against a messy monorepo.