INDIVIDUAL MCP TOOL

health_check

Verify the itemscore tooling before you tell the user anything is ready: confirms this MCP server is actually reachable (it answers), lists the available tools, and reports the API plugin version and method count.

coredevelopment.shopnone authenticationAvailability not checked

LIVE ENDPOINT

https://www.coredevelopment.shop/api/mcp

No auth detected

Connect to this endpoint to inspect the live schema for health_check 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

coredevelopment.shop

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.itemscore]
url = "https://www.coredevelopment.shop/api/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "itemscore": {
      "type": "http",
      "url": "https://www.coredevelopment.shop/api/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: itemscore
Remote MCP URL: https://www.coredevelopment.shop/api/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": {
    "itemscore": {
      "url": "https://www.coredevelopment.shop/api/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "itemscore": {
      "type": "http",
      "url": "https://www.coredevelopment.shop/api/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "itemscore",
  "transport": "streamable-http",
  "url": "https://www.coredevelopment.shop/api/mcp"
}

MCP Inspector

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

Related tools

search_methods — Search the ItemsCore scripting API for methods by name, category, signature, or description.
get_method — Get the full details (signature, params, return, description, example) of a specific method.
list_triggers — List every action trigger (when an item's actions can run, e.g.
list_events — List the custom events and the global scripting variables (player, event, core, particles, etc.) available when writing item actions.
get_item_schema — Get the full schema and field reference for the clean item JSON that ItemsCore imports.
validate_item — Validate a clean item JSON object against the ItemsCore schema (unknown methods, wrong argument count, wrong argument order/type).
generate_item_template — Return a valid starter item JSON to build from.
get_stat_schema — Get the format and field reference for ItemsCore stats (the named values like Strength shown on items).