Which integrations are available for this server?

Searches GitHub for Claude Code skills, plugins, and MCP servers to discover tools and solutions. Searches the npm registry for MCP servers and packages relevant to Claude Code.

How do I use claude-oracle-mcp?

1. Click on "Install Server". 2. Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state. 3. In the chat, type @ followed by the MCP server name and your instructions, e.g., "@claude-oracle-mcp search for PostgreSQL MCP servers" That's it! The server will respond to your query, and you can continue using it as needed. Here is a step-by-step guide with screenshots.

claude-oracle-mcp

by Vvkmnn

Overview Schema Related Servers Score Discussions

TypeScript

Remote

claude-oracle-mcp

An Model Context Protocol (MCP) server for discovering Claude Code skills, plugins, and MCP servers. Search 15,000+ resources from 17 registries + GitHub search + web search with zero setup.

claude-oracle-mcp

npm version License: MIT TypeScript Node.js Claude GitHub stars

install

Requirements:

Claude Code

From shell:

claude mcp add claude-oracle-mcp -- npx claude-oracle-mcp

From inside Claude (restart required):

Add this to our global mcp config: npx claude-oracle-mcp

Install this mcp: https://github.com/Vvkmnn/claude-oracle-mcp

From any manually configurable mcp.json: (Cursor, Windsurf, etc.)

{
  "mcpServers": {
    "claude-oracle-mcp": {
      "command": "npx",
      "args": ["claude-oracle-mcp"],
      "env": {
        "SKILLSMP_API_KEY": "optional-for-semantic-search",
        "GITHUB_TOKEN": "optional-for-higher-rate-limits"
      }
    }
  }
}

There is no npm install required -- no external dependencies or local databases, only search algorithms.

However, if npx resolves the wrong package, you can force resolution with:

npm install -g claude-oracle-mcp

Related MCP server: cc-session-search

skill

Optionally, install the skill to teach Claude when to proactively use oracle:

npx skills add Vvkmnn/claude-oracle-mcp --skill claude-oracle --global
# Optional: add --yes to skip interactive prompt and install to all agents

This makes Claude automatically search for relevant tools before planning, when encountering errors, or at session start. The MCP works without the skill, but the skill improves discoverability.

plugin

For automated tool discovery with hooks, install from the claude-emporium marketplace:

/plugin marketplace add Vvkmnn/claude-emporium
/plugin install claude-oracle@claude-emporium

The claude-oracle plugin provides:

Hooks (targeted, fires before external searches):

Before WebSearch/WebFetch → Check oracle for existing tools first
Before EnterPlanMode → Search for relevant plugins/skills

Command: /oracle-search <query>

Requires the MCP server installed first. See the emporium for other Claude Code plugins and MCPs.

features

MCP server that gives Claude access to 15,000+ skills, plugins, and MCP servers from 17 registries + GitHub search + web search. Fast discovery with smart prioritization.

Runs locally (with crystal vision 🔮):

`search`

Search across all resources for relevant tools and solutions.

🔮 search query=<query>
  > "Are there any MCP servers for PostgreSQL?"
  > "What testing frameworks exist for React?"
  > "Do we have authentication plugins?"

🔮 search | postgres

╭─ 🔮 ─────────────────────────────── Found 5 ─╮
│ • postgres-mcp (mcp)                         │
│   PostgreSQL database access                 │
│   smithery.ai • ⭐ verified                  │
│   Install: npx postgres-mcp                  │
│                                              │
│ • postgresql-mcp (mcp)                       │
│   PostgreSQL MCP server                      │
│   npmjs.com • ✨ quality                     │
│   Install: npx @scope/postgresql-mcp         │
│                                              │
│ Total: 19 sources • 15,000+ resources        │
╰──────────────────────────────────────────────╯

{
  "results": [
    {
      "name": "postgres-mcp",
      "type": "mcp",
      "description": "PostgreSQL database access",
      "source": "smithery.ai",
      "install_command": "npx postgres-mcp",
      "verified": true,
      "stars": 142
    },
    {
      "name": "postgresql-mcp",
      "type": "mcp",
      "description": "PostgreSQL MCP server",
      "source": "npmjs.com",
      "install_command": "npx @scope/postgresql-mcp",
      "quality_score": 0.85
    }
  ],
  "sources_searched": ["smithery.ai", "npmjs.com", "glama.ai", "modelcontextprotocol.io"],
  "total_available": 15000,
  "cached": false
}

`browse`

Browse resources by category, type, or popularity.

🔮 browse category=<category>
  > "Browse testing tools"
  > "Show MCP servers only"
  > "Find security-related skills"

🔮 browse | testing

╭─ 🔮 ─────────────────────────────── Found 8 ─╮
│ • tdd-workflows (plugin)                     │
│   Test-driven development workflow           │
│   claude-code-plugins-plus • 258 plugins     │
│                                              │
│ • pytest-mcp (mcp)                           │
│   Python testing framework                   │
│   smithery.ai • ⭐ verified                  │
│                                              │
│ Total: 19 sources • 15,000+ resources        │
╰──────────────────────────────────────────────╯

{
  "results": [
    {
      "name": "tdd-workflows",
      "type": "plugin",
      "description": "Test-driven development workflow",
      "source": "claude-code-plugins-plus",
      "install_command": "git clone https://github.com/user/tdd-workflows ~/.claude/plugins/tdd-workflows",
      "category": "testing"
    },
    {
      "name": "pytest-mcp",
      "type": "mcp",
      "description": "Python testing framework",
      "source": "smithery.ai",
      "install_command": "npx pytest-mcp",
      "verified": true
    }
  ],
  "sources_searched": ["claude-code-plugins-plus", "smithery.ai", "npmjs.com"],
  "total_available": 15000,
  "cached": true
}

`sources`

Show all available data sources and their status.

🔮 sources
  > "Which sources are available?"
  > "Check data source health"

🔮 sources | 19 total

╭─ 🔮 ─────────────────────────────── 15,000+ total ─╮
│ Plugins (303):                                     │
│   • claude-code-plugins-plus: 258 ✓                │
│   • claude-plugins-official: 45 ✓                  │
│                                                    │
│ MCP Servers (14,358):                              │
│   • smithery.ai: 500 ✓                             │
│   • playbooks.com: 1,000+ ✓                        │
│   • npmjs.com: 250 ✓                               │
│   • modelcontextprotocol.io: 248 ✓                 │
│   • glama.ai: 662 ✓                                │
│   • wong2/awesome-mcp-servers: 200+ ✓              │
│   • punkpeye/awesome-mcp-servers: 400+ ✓           │
│   • collabnix/awesome-mcp-lists: 100+ ✓            │
│                                                    │
│ Skills (339):                                      │
│   • awesome-agent-skills: 339 ✓                    │
│   • awesome-claude-code: 200+ ✓                    │
│   • jmanhype/awesome-claude-code: 50+ ✓            │
│   • skillsmp: 25,000 (optional key)                │
╰────────────────────────────────────────────────────╯

{
  "sources": [
    { "name": "claude-code-plugins-plus", "type": "plugin", "count": 258, "status": "ok" },
    { "name": "claude-plugins-official", "type": "plugin", "count": 45, "status": "ok" },
    { "name": "smithery.ai", "type": "mcp", "count": 500, "status": "ok" },
    { "name": "playbooks.com", "type": "mcp", "count": 1000, "status": "ok" },
    { "name": "npmjs.com", "type": "mcp", "count": 250, "status": "ok" },
    { "name": "modelcontextprotocol.io", "type": "mcp", "count": 248, "status": "ok" },
    { "name": "glama.ai", "type": "mcp", "count": 662, "status": "ok" },
    { "name": "awesome-agent-skills", "type": "skill", "count": 339, "status": "ok" },
    { "name": "skillsmp", "type": "skill", "count": 25000, "status": "no_key" }
  ],
  "total": 15000
}

methodology

How claude-oracle-mcp works:

 User: "What MCP servers exist for PostgreSQL?"
                        ↓
              ┌─────────────────────┐
              │  🔮 claude-oracle   │
              │     MCP Server      │
              └─────────┬───────────┘
                        │
         ┌──────────────┼──────────────┐
         │   PARALLEL SEARCH (19)       │
         └──────────────┬───────────────┘
                        │
    ┌───────────────────┼───────────────────┐
    │                   │                   │
┌───▼────┐        ┌────▼─────┐       ┌────▼─────┐
│Smithery│        │  npm     │       │ Glama.ai │
│  500   │        │  250     │       │   662    │
└────────┘        └──────────┘       └──────────┘
    │                   │                   │
    └───────────────────┼───────────────────┘
                        │
              ┌─────────▼───────────┐
              │   DEDUPLICATE &     │
              │   RANK RESULTS      │
              └─────────┬───────────┘
                        │
              ┌─────────▼───────────┐
              │  FORMAT & RETURN    │
              │   🔮 Beautiful      │
              │   Bordered Output   │
              └─────────────────────┘

Core features:

17 registries + GitHub search + web search: Smithery, npm, Glama.ai, GitHub, awesome lists + more
15,000+ resources: Skills, plugins, and MCP servers in one search
Parallel fetching: All sources searched simultaneously (~3 seconds)
Smart caching: In-memory TTL cache (6-24 hour expiry)
Keyword scoring: Weighted matching (exact > starts with > contains)
Quality signals: Stars, verified badges, quality scores boost ranking
Beautiful formatting: Bordered output with 🔮 identifier

Data sources (zero-config, 16/17 registries):

Source	Type	Count	Method
Smithery Registry	MCP	500	REST API (5 pages)
Playbooks	MCP	1,000+	XML Sitemaps
Official MCP Registry	MCP	248	REST API (3 iterations)
npm Registry	MCP/Plugin	250	Search API (1 page)
Glama.ai	MCP	662	RSS Feed
wong2/awesome-mcp-servers	MCP	200+	GitHub Markdown
punkpeye/awesome-mcp-servers	MCP	400+	GitHub Markdown
collabnix/awesome-mcp-lists	MCP	100+	GitHub Markdown
jmanhype/awesome-claude-code	Plugin/Skill	50+	GitHub Markdown
hesreallyhim/awesome-claude-code	Skill	200+	GitHub Markdown
awesome-agent-skills	Skill	339	GitHub Markdown
claude-code-plugins-plus	Plugin	258	Marketplace JSON
claude-plugins-official	Plugin	45	Marketplace JSON
superpowers-marketplace	Plugin	-	Marketplace JSON

Query-based (searched per query, zero-config):

Source	Type	Count	Method
GitHub (search)	MCP/Plugin	~20	REST API (per query)
Web (search)	MCP/Plugin	~10	DuckDuckGo Lite (per query)

Optional (requires API key):

SkillsMP: 25,000+ skills with semantic search (get key)
GITHUB_TOKEN: Higher GitHub API rate limits (10 → 30 req/min)

Note: Pagination is limited for faster responses (~3s). Full datasets available through caching on subsequent searches.

Design principles:

Aggregated search -- single query searches 17 registries + GitHub + web simultaneously
Zero-config -- 18/19 sources work without API keys (GITHUB_TOKEN optional for rate limits)
Deduplication -- cross-source result merging by name similarity
Relevance scoring -- weighted name match, description match, and popularity
Offline fallback -- graceful degradation when sources are unreachable

alternatives

Every MCP discovery tool either searches a single registry or requires separate accounts per source. Oracle aggregates 19 sources in one command.

Feature	oracle	1mcpserver	Single registry
Resource types	MCP + plugins + skills	MCP servers only	Usually one type
Sources	19 (registries + awesome lists + GitHub + web)	Registry searches	One source at a time
Skills/plugins	Yes (339 skills, 303 plugins)	No	Usually no
Setup	One MCP, one command	One MCP, one command	Separate account/API per registry
Cross-source	Deduplicated, ranked results	Per-registry	Manual comparison
Caching	In-memory TTL (6-24h)	Per-request	Varies
Install commands	Included in results	Included in results	Varies

1mcpserver -- MCP server discovery from multiple registries. Searches MCP servers only -- no plugins, no skills. Per-registry results without cross-source dedup or ranking. No caching between requests.

Smithery, Glama, SkillsMP -- Individual registries, each searchable independently. Requires separate accounts or API access per registry. Each covers a subset of the ecosystem -- no single source has everything. Manual comparison across registries to find the best option. Oracle aggregates all of these (and 16 more sources) with deduplicated, ranked results in one query.

development

git clone https://github.com/Vvkmnn/claude-oracle-mcp && cd claude-oracle-mcp
npm install && npm run build
npm test

Package requirements:

Node.js: >=20.0.0 (ES modules)
Runtime: @modelcontextprotocol/sdk, fast-xml-parser
Zero external databases -- works with npx

Development workflow:

npm run build          # TypeScript compilation with executable permissions
npm run dev            # Watch mode with tsc --watch
npm run start          # Run the MCP server directly
npm run lint           # ESLint code quality checks
npm run lint:fix       # Auto-fix linting issues
npm run format         # Prettier formatting (src/)
npm run format:check   # Check formatting without changes
npm run typecheck      # TypeScript validation without emit
npm run test           # Lint + type check
npm run prepublishOnly # Pre-publish validation (build + lint + format:check)

Git hooks (via Husky):

pre-commit: Auto-formats staged .ts files with Prettier and ESLint

Contributing:

Fork the repository and create feature branches
Test with multiple data sources before submitting PRs
Follow TypeScript strict mode and MCP protocol standards

Learn from examples:

Official MCP servers for reference implementations
TypeScript SDK for best practices
Creating Node.js modules for npm package development

license

MIT

Aeneas and the Cumaean Sibyl by Claude Mellan. The oracle who guided Aeneas through the underworld.

Available Tools

3 tools

browseBrowse ToolsB

Read-onlyIdempotent

Browse skills, plugins, and MCP servers by category or popularity.

ParametersJSON Schema

Name	Required	Description
`sort`	No	Sort order (default: popular)
`type`	No	Filter by resource type (default: all)
`limit`	No	Max results (default: 10)
`category`	No	Category filter (e.g., testing, database, security)

TDQS

B3.3/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint. The description adds no behavioral traits beyond what annotations provide (e.g., does not mention pagination, result truncation, or dynamic nature). It merely restates filtering capabilities that are already in the schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence of 10 words, front-loading the key action and scope. Every word is essential; no redundancy or filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple browse tool with 4 optional parameters and no output schema, the description covers the basic purpose and filtering. However, it lacks guidance on output format or pagination behavior, and does not help distinguish from siblings in usage context. The annotations compensate partially for behavioral transparency.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, with each parameter already documented in the input schema. The description's phrase 'by category or popularity' maps to the category and sort parameters but adds no new meaning or constraints beyond the schema. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Browse skills, plugins, and MCP servers by category or popularity' clearly specifies the verb (browse), the resources (skills, plugins, MCP servers), and the filtering methods (category, popularity). This distinguishes it from sibling tools like 'search' (likely keyword-based) and 'sources' (likely listing data sources). It follows a 'specific verb+resource' structure.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description does not provide any guidance on when to use this tool versus alternatives (search, sources). It lacks 'when not to use' or explicit context for selection. While siblings are named, no comparative guidance is given.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

searchSearch ToolsA

Read-onlyIdempotent

Search for Claude Code skills, plugins, and MCP servers. Returns install commands.

ParametersJSON Schema

Name	Required	Description
`type`	No	Filter by resource type (default: all)
`limit`	No	Max results (default: 5, max: 20)
`query`	Yes	Search term or description
`semantic`	No	Use AI semantic search (requires SKILLSMP_API_KEY)

TDQS

A3.9/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint, establishing safe read and idempotent behavior. The description adds the crucial behavioral detail that the tool 'returns install commands', which is not covered by annotations or schema. This adds value beyond the structured fields.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences: the first clearly states the action and resources, and the second states the output. Every word earns its place; no redundancy or fluff.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has 4 parameters (including an enum and a semantic option) and no output schema, the description is somewhat sparse. It does not explain behavior differences across type filters, the semantic search requirement, or the return format beyond 'install commands'. The schema provides parameter details, but the description lacks high-level completeness for a search tool of this complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents all parameters. The description does not add meaning beyond what is already in the schema; it summarizes the purpose but not parameter-level details. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool searches for Claude Code skills, plugins, and MCP servers, and returns install commands. It specifies the verb 'search' and identifies the resource (skills, plugins, MCP servers), distinguishing it from sibling tools like 'browse' and 'sources' which likely have different purposes.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for searching installable resources but provides no explicit guidance on when to use this tool versus siblings or when not to use it. No alternatives or exclusions are mentioned, leaving the agent to infer usage context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

sourcesData SourcesA

Read-onlyIdempotent

Show available data sources and their status.

ParametersJSON Schema

Name	Required	Description	Default
No parameters

TDQS

A4.3/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint and idempotentHint, covering safety and idempotency. The description adds 'status' context but does not delve into behavioral details beyond what annotations provide.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, front-loaded sentence with no wasted verbiage, perfectly appropriate for this simple tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (no parameters, no output schema, clear annotations), the description fully covers purpose and output without gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With zero parameters and 100% schema coverage, the description adds no parameter info, but baseline for zero parameters is 4, and the description is adequate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'Show' and the resource 'available data sources and their status,' effectively distinguishing it from siblings like 'browse' and 'search'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear context for when to use the tool (to view data sources and status) but does not explicitly exclude scenarios or mention alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

A3.8/5.0

Disambiguation4/5

Tools are generally distinct: browse is for exploring categories, search is for querying, and sources lists data sources. However, there is minor potential confusion between browse and search.

Naming Consistency4/5

All tool names are single lowercase words ('browse', 'search', 'sources'), which is a consistent but simple pattern. No mixing of conventions.

Tool Count5/5

Three tools is well-scoped for a discovery server: browse, search, and sources cover the core functionality without excess.

Completeness4/5

The set covers browsing, searching, and viewing sources, which is complete for discovery. Missing a dedicated 'get details' tool is minor.

Maintenance

ActivityInactive

ResponsivenessSyncing

Resources

Need Help?

Related Servers

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

MCP Marketplace A
io.mcp-marketplace
Search and install 4,000+ security-scanned MCP servers from inside any MCP-aware AI client.
Developer Tools Search
72
H-Index A
ai.xr-utilities
Capability registry for the agentic economy. Semantic search over verified MCP server listings.
Search Documentation Access
32
Skill of Skills A
io.911fund.skills
Quality-ranked, cross-platform directory of AI coding skills, plugins and MCP servers.
Developer Tools AI & Machine Learning
6211
Find MCP - Agentage MCP Directory A
io.agentage
Search the official MCP registry: 17,000+ servers with trust grades, stars, tools, install config.
Search Developer Tools Documentation Access
32

Related MCP Servers

Skillz
Developer Tools Autonomous Agents Code Execution
214140846
A
license
Not graded
quality
Not graded
maintenance
An MCP server that transforms Claude-style skills and resources into callable tools for any MCP-compatible agent or client. It automatically discovers, exposes, and executes scripts from skills organized in local directories or packaged archives.
Updated 7 months ago (2026-01-18 02:51 UTC)
cc-session-search
Developer Tools Search
bwads001
F
license
B
quality
D
maintenance
An MCP server that provides tools for searching and analyzing Claude Code conversation history.
Updated a year ago (2025-09-20 23:15 UTC)
8
4
SkillSync MCP
Developer Tools AI & Machine Learning Security
adityasugandhi
A
license
Not graded
quality
C
maintenance
An MCP server for searching, security scanning, installing, and managing skills from the SkillsMP marketplace, designed for Claude Code and other MCP-compatible clients.
Updated 6 months ago (2026-02-23 02:53 UTC)
14
4
MIT
skillsmp-mcp-server
Developer Tools AI & Machine Learning
anilcancakir
A
license
A
quality
C
maintenance
This MCP server enables AI agents to search, discover, and install skills from the SkillsMP marketplace, with support for keyword and semantic search, skill content retrieval, and installation to various coding agents.
Updated 7 months ago (2026-01-21 22:57 UTC)
5
1,647
3
MIT

Latest Blog Posts

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Vvkmnn/claude-oracle-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server