INDIVIDUAL MCP TOOL

get_api

The full JSON record of one API by owner/slug: description, provider, license, every source with its last check, publisher-declared versions, lastCheckedAt / lastUpdatedAt, the latest content ref (latestVersionRef), operation and schema counts.

skmtc.devnone authenticationAvailability not checked

LIVE ENDPOINT

https://mcp.skmtc.dev/mcp

No auth detected

Connect to this endpoint to inspect the live schema for get_api and invoke it with your own arguments.

Indexed input schema

{}

Risk classification

Inferred read-only · medium confidence · heuristic, not a guarantee.

No write-capable action terms were found; this is not proof that invocation has no side effects.

Parent server

skmtc.dev

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.skmtc]
url = "https://mcp.skmtc.dev/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "skmtc": {
      "type": "http",
      "url": "https://mcp.skmtc.dev/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: skmtc
Remote MCP URL: https://mcp.skmtc.dev/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "skmtc": {
      "url": "https://mcp.skmtc.dev/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "skmtc": {
      "type": "http",
      "url": "https://mcp.skmtc.dev/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "skmtc",
  "transport": "streamable-http",
  "url": "https://mcp.skmtc.dev/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

Related tools

lookup_apis — Resolve a list of service or API names against the skmtc catalog in one call — the tool to start with when a project needs several APIs.
search_apis — Search the catalog's API cards (name and short description) with ranked results — for finding APIs by what they are called when lookup_apis has no owner match.
list_operations — Every operation of an API in one fetch, as the site's llms.txt: one line per operation with the address of its markdown page.
get_operation — One operation's documentation as markdown, at the API's latest revision: parameters, request body, responses, and a Changes section with its recorded history.
ask_catalog — Ask a natural-language question of the catalog and get an answer grounded in the indexed API content, with citations that name the API and operation.