Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, email [email protected] and we’ll put it right.

io.github.marcelo-ochoa/oracle

NPM · @MARCELO-OCHOA/SERVER-ORACLE · SCANNED AUG 3

MCP server for interacting with Oracle databases

+11 this week 61 Trust /100
Trust breakdown (6 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score →

Supply Chain Security87
  • No malware found by supply-chain analysis.Pass
  • Only part of the dependency tree could be resolved (96 of 100), so this covers what we could see, not the whole tree.Partial
  • No install/post-install scripts declared.Pass
  • Only part of the dependency tree could be resolved (96 of 100), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability58
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (fair).Partial
  • Context-footprint check failed: tool/resource definitions use about 1270 tokens (~254/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage97
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 92% of tool parameters carry a description.Partial
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

npm · @marcelo-ochoa/server-oracle

# add to Claude Code
claude mcp add marcelo-ochoa-oracle -- npx -y @marcelo-ochoa/server-oracle
# add to Codex CLI
codex mcp add marcelo-ochoa-oracle -- npx -y @marcelo-ochoa/server-oracle
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "marcelo-ochoa-oracle": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@marcelo-ochoa/server-oracle"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add marcelo-ochoa-oracle --command npx --arg -y --arg @marcelo-ochoa/server-oracle
# ~/.hermes/config.yaml
mcp_servers:
  marcelo-ochoa-oracle:
    command: "npx"
    args: ["-y", "@marcelo-ochoa/server-oracle"]
// mcp.json
{
  "mcpServers": {
    "marcelo-ochoa-oracle": {
      "command": "npx",
      "args": [
        "-y",
        "@marcelo-ochoa/server-oracle"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 2 Aug 26 +37
    • Provenance: unverified → fail security
    • Install scripts: unverified → pass security
    • Known CVEs: unverified → partial security
    • Malware scan: unverified → pass security
    • Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
    • Tool coverage: 100 → unverified functional
    • Schema quality: 100 → unverified functional
    • License: unverified → pass functional
    • Schema quality: unverified → fair functional
    • Maintenance: unverified → pass functional
    • MCP protocol: unverified → pass functional
    • Dependency health: unverified → partial functional
    • Licence: MIT functional
  • 31 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 −26
    • Tool coverage: 100 → unverified functional
    • Schema quality: 100 → unverified functional
  • 27 Jul 26 50

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 3 Aug 2026 · Analysed npm/@marcelo-ochoa/[email protected]

Provenance none

Ecosystem: npm · Outcome: none

Dependencies 96 packages

96 packages in the resolved dependency tree · 95 deprecated · 29 stale.

The dependency tree was only partially resolved, so these counts may be incomplete.

MCP tools — 5 exposed · ~1,270 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.

Tool Tokens
orcl-awr ~248

Generate an Automatic Workload Repository (AWR) report or AWR SQL report for Oracle database performance analysis. AWR reports provide comprehensive performance metrics including database statistics, wait events, top SQL statements, system resources, and performance recommendations. If no sql_id is provided, generates a full AWR database report with: - Database instance information and configuration - Load profile and instance efficiency metrics - Top wait events and time model statistics - SQL statistics ordered by various metrics (elapsed time, CPU time, executions, etc.) - Segment statistics and I/O statistics - Memory and SGA statistics - System and session statistics If a sql_id is provided, generates an AWR SQL report focused on that specific SQL statement with: - SQL text and execution statistics - Execution plans and plan history - Bind variable information - Wait events specific to the SQL - Performance metrics over time Args: sql_id (optional): The SQL ID for generating an AWR SQL report. If omitted, generates a full AWR database report. Returns: Comprehensive performance report in text or HTML format with actionable insights for database tuning and optimization.

NameTypeReqDescription
sql_idstring

No output schema declared.

No examples provided.

orcl-connect ~160

Provides an interface to connect to a specified database. If a database connection is already active, prompt the user for confirmation before switching to the new connection. The `model` argument should only be used to specify the name and version of the LLM (Large Language Model) you are using, with no additional information. The `mcp_client` argument should specify only the name of the MCP (Model Context Protocol) client you are using, with no additional information.

NameTypeReqDescription
connectionStringstringyesThe Oracle connect string (e.g. host.docker.internal:1521/freepdb1
passwordstringyesThe Oracle password (e.g. tiger
userstringyesThe Oracle user (e.g. scott

No output schema declared.

No examples provided.

orcl-explain ~253

Generate and display the execution plan for a given SQL query using Oracle's EXPLAIN PLAN command. This tool helps you understand how Oracle will execute your query, including information about table access methods, join operations, indexes used, estimated costs, and cardinality estimates. Args: sql: The SQL query to explain. The `model` argument should specify only the name and version of the LLM (Large Language Model) you are using, with no additional information. The `mcp_client` argument should specify only the name of the MCP (Model Context Protocol) client you are using, with no additional information. Returns: Detailed execution plan showing how Oracle will process the query, including operation types, object names, costs, bytes, and cardinality estimates.

NameTypeReqDescription
mcp_clientstringyesSpecify the name and version of the MCP client implementation being used (e.g. Copilot, Claude, Cline...)
modelstringyesThe name (and version) of the language model being used by the MCP client to process requests (e.g. gpt-4.1, claude-sonnet-4, llama4...)
sqlstringyesThe SQL query to explain

No output schema declared.

No examples provided.

orcl-query ~348

This tool executes SQL queries in a READY ONLY session connected to an Oracle database. If no active connection exists, it uses MCP server registration argument and environment variables ORACLE_USER and ORACLE_PASSWORD. You should: Execute the provided SQL query. Return the results in Json format. Args: sql: The SQL query to execute. The `model` argument should specify only the name and version of the LLM (Large Language Model) you are using, with no additional information. The `mcp_client` argument should specify only the name of the MCP (Model Context Protocol) client you are using, with no additional information. Returns: Json-formatted query results. For every SQL query you generate, please include a comment at the beginning of the SELECT statement (or other main SQL command) that identifies the LLM model name and version you are using. Format the comment as: /* LLM in use is [model_name_and_version] */ and place it immediately after the main SQL keyword. For example: SELECT /* LLM in use is claude-sonnet-4 */ column1, column2 FROM table_name; Please apply this format consistently to all SQL queries you generate, using your actual model name and version in the comment

NameTypeReqDescription
mcp_clientstringyesSpecify the name and version of the MCP client implementation being used (e.g. Copilot, Claude, Cline...)
modelstringyesThe name (and version) of the language model being used by the MCP client to process requests (e.g. gpt-4.1, claude-sonnet-4, llama4...)
sqlstringyesThe SQL query to execute

No output schema declared.

No examples provided.

orcl-stats ~261

Get comprehensive statistics for a specific Oracle database object (table, index, or view). This tool retrieves detailed information including row counts, block statistics, segment size, index information, column statistics, partition details, and other metadata that can help optimize queries and understand data distribution. Args: name: The name of the database object to get statistics for. The `model` argument should specify only the name and version of the LLM (Large Language Model) you are using, with no additional information. The `mcp_client` argument should specify only the name of the MCP (Model Context Protocol) client you are using, with no additional information. Returns: Json-formatted object statistics including row counts, block usage, size information, indexes, partitions, and column details with histograms and data distribution metrics.

NameTypeReqDescription
mcp_clientstringyesSpecify the name and version of the MCP client implementation being used (e.g. Copilot, Claude, Cline...)
modelstringyesThe name (and version) of the language model being used by the MCP client to process requests (e.g. gpt-4.1, claude-sonnet-4, llama4...)
namestringyesSQL Object to get stats

No output schema declared.

No examples provided.