Elva · Authentication Profile

Elva Authentication

Authentication

Elva declares 2 security scheme(s) across its OpenAPI definitions.

API ManagementMCP ServerMCP LogsMCP InsightsAPI ClientAPI ContractAPI GovernanceAPI DiscoveryOpenAPIAPI TestingDeveloper ToolsAI Agent Infrastructure
Methods: Schemes: 2 OAuth flows: API key in:

Security Schemes

none none
oauth2 oauth2
· flows:

Source

Authentication Profile

elva-authentication.yml Raw ↑
generated: '2026-09-07'
method: searched
source: https://docs.getelva.ai/quality-and-scoring/score-a-spec-via-api
docs: https://docs.getelva.ai/agent-ready-with-mcp/mcp-authentication-and-oauth
note: >-
  Two distinct surfaces. (1) The public Spec Scoring API at api.getelva.ai is
  deliberately unauthenticated — "no account and no key" — for GET /api/review/checks
  and POST /api/review; everything else in Elva's API (repos, catalog, collections,
  MCP, chat, testing) sits behind authentication inside the app. (2) The platform's
  own MCP resource at app.getelva.ai/mcp is OAuth 2.0-protected, discovered via
  RFC 8414 + RFC 9728 metadata (probed 2026-09-07): authorization_code + PKCE S256,
  dynamic client registration. Separately, Elva's hosted-MCP runtime RELAYS customer
  upstream auth (no_auth, api_key, bearer_token, jwt, basic_auth, oauth_2_0
  client-credentials/password, openid_connect) — a stateless in-memory token relay,
  documented for customer deployments, not an auth scheme of Elva's own API.
schemes:
  - name: none
    type: none
    surface: Spec Scoring API (api.getelva.ai)
    detail: GET /api/review/checks and POST /api/review are open to everyone, no key.
  - name: oauth2
    type: oauth2
    surface: Elva platform MCP (app.getelva.ai/mcp)
    flows:
      authorizationCode:
        authorizationUrl: https://app.getelva.ai/oauth/authorize
        tokenUrl: https://app.getelva.ai/oauth/token
    detail: >-
      PKCE S256 required; dynamic client registration at
      https://app.getelva.ai/oauth/register; token endpoint auth
      client_secret_post or none. No scopes_supported published in the metadata.

Work with this as data

Every security artifact here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for security posture

4 MCP tools reach this
  • find_securityBrowse and filter every security artifact in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This security artifact
curl "https://apis.io/api/v1/security/elva-authentication"
All security posture
curl "https://apis.io/api/v1/security?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.