OCI Database Service MCP server
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"oracle-oci-database-mcp-server","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# OCI Database MCP Server ## Overview This server provides tools to interact with the OCI Database service. ## Running the server ### STDIO transport mode ```sh uv run oracle.oci-database-mcp-server ``` ### HTTP streaming transport mode ```sh ORACLE_MCP_HOST=<bind_host> \ ORACLE_MCP_PORT=<port> \ ORACLE_MCP_BASE_URL=<public_base_url> \ OCI_REGION=<region> \ IDCS_DOMAIN=<idcs_domain> \ IDCS_CLIENT_ID=<client_id> \ IDCS_CLIENT_SECRET=<client_secret> \ IDCS_AUDIENCE=<audience> \ uv run oracle.oci-database-mcp-server ``` For the OCI IAM confidential application, register `${ORACLE_MCP_BASE_URL}/auth/callback` as the redirect URI. By default, the server requires `openid profile email oci_mcp.database.invoke`; set `IDCS_REQUIRED_SCOPES` to a space-delimited list or JSON array to override it. `stdio` uses the selected OCI credential mode, while HTTP exchanges each authenticated OCI IAM user's access token to make caller-specific OCI SDK requests. ## Environment Variables The server uses `oracle-mcp-common` to resolve OCI authentication. It supports the following environment variables: - `OCI_MCP_AUTH_TYPE`: authentication mode. The default, `auto`, selects session-token authentication when the selected profile directly declares a `security_token_file`; otherwise it uses API-key authentication. - `OCI_CONFIG_FILE`: OCI configuration file path (default: `~/.oci/config`). - `OCI_CONFIG_PROFILE`: OCI configuration profile name (default: "DEFAULT") Set `OCI_MCP_AUTH_TYPE` to use a non-profile authentication mode: `identity_domain_upst`, `instance_principal`, `resource_principal`, `instance_principal_delegation`, `resource_principal_delegation`, or `oke_workload_identity`. Those modes use the standard `oracle-mcp-common` configuration and OCI SDK prerequisites. HTTP mode uses the OCI IAM/IDCS configuration shown above rather than `OCI_MCP_AUTH_TYPE`. `oracle-mcp-common` validates `IDCS_DOMAIN`, `IDCS_CLIENT_ID`, `IDCS_CLIENT_SECRET`, `IDCS_AUDIENCE`, and `ORACL…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.