restor3d · Authentication Profile

Restor3D Authentication

Authentication

restor3d declares 3 security scheme(s) across its OpenAPI definitions.

Medical DevicesHealthOrthopedics3D PrintingAdditive ManufacturingImplantsSurgeryArtificial IntelligenceManufacturingCompany
Methods: Schemes: 3 OAuth flows: API key in:

Security Schemes

oauth2
http
scheme: basic
none

Source

Authentication Profile

restor3d-authentication.yml Raw ↑
generated: '2026-08-26'
method: probed
source: >-
  https://www.restor3d.com/.well-known/oauth-authorization-server (HTTP 200),
  https://www.restor3d.com/.well-known/oauth-protected-resource (HTTP 200) and the
  `authentication` block of https://www.restor3d.com/wp-json/ (HTTP 200), all fetched 2026-08-26.
  Derived from no OpenAPI - restor3d publishes none.
api: restor3d Website Content API (WordPress REST + MCP)
summary: >-
  restor3d publishes no developer authentication documentation of any kind. Everything below was
  read off machine-readable metadata its website serves, not off a docs page. Anonymous read
  access is available on the public WordPress REST content routes; every write route and both MCP
  servers are gated.
schemes:
- id: oauth2_mcp
  type: oauth2
  flow: authorization_code
  applies_to: https://www.restor3d.com/wp-json/mcp/mcp-oauth-server
  issuer: https://www.restor3d.com
  authorization_endpoint: https://www.restor3d.com/oauth/authorize
  token_endpoint: https://www.restor3d.com/oauth/token
  revocation_endpoint: https://www.restor3d.com/oauth/revoke
  response_types_supported:
  - code
  grant_types_supported:
  - authorization_code
  - refresh_token
  pkce:
    required_methods:
    - S256
  token_endpoint_auth_methods_supported:
  - none
  client_registration: >-
    client_id_metadata_document_supported = true - clients are identified by a URL that resolves
    to a client metadata document (the emerging CIMD pattern) rather than by pre-registration.
  scopes:
  - mcp
  bearer_methods_supported:
  - header
- id: application_passwords
  type: http
  scheme: basic
  applies_to: https://www.restor3d.com/wp-json/wp/v2/*
  note: >-
    WordPress Application Passwords are advertised in the REST index at
    https://www.restor3d.com/wp-json/ with authorization endpoint
    https://www.restor3d.com/wp-admin/authorize-application.php. Issuance requires an existing
    WordPress account on the site; there is no public sign-up.
- id: anonymous
  type: none
  applies_to: public GET routes under https://www.restor3d.com/wp-json/wp/v2/
  note: >-
    Read access to published content types (pages, posts, event, resource, procedure,
    product-family, product-category, asset-type, content-type, module) is unauthenticated.
gaps:
- No authentication documentation is published anywhere on restor3d.com.
- No API key programme, no developer sign-up, no partner credential flow.
- No OpenID Connect - /.well-known/openid-configuration returns 404.

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/restor3d-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 email required.

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