Developer Tools

coredevelopment.shop

Provides an interface to query and retrieve details about the ItemsCore scripting API, including methods, triggers, events, and item schemas.

1 endpoint12 known toolsFirst detected June 22, 2026Last detected August 6, 2026

ENDPOINT 1

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

No auth detected

MCP server metadata

Name: itemscore
Version: 5.0

Capabilities

tools.listChanged

Server instructions

ItemsCore is a Minecraft (Bukkit/Spigot) plugin that lets server owners build custom RPG items, stats and abilities with no Java. You can do everything: build and edit items, create and edit stats, and run any plugin command. BEFORE you build anything or tell the user the tooling is ready, CALL the health_check tool - the fact it returns proves this server is actually connected. Do not claim the tooling is set up just because you ran a command; claim it only after health_check returns, and do whatever its nextActions say. Do this at the start of every session. FIRST, find the ItemsCore plugin folder. It is the folder named ItemsCore inside the server's plugins folder (plugins/ItemsCore/) and it contains an items/ folder, a stats/ folder, and config.yml. Items go in its imports/ folder, stats live in stats/stats.yml. If you cannot find a folder with those markers from where you are running, ASK THE USER for the absolute path to their ItemsCore plugin folder and use that. Never guess a path or write outside that folder. ITEMS: use the API tools (search_methods/get_method/get_item_schema/generate_item_template), author a clean item JSON, validate it with validate_item, then save it with a .import extension (for example flame_sword.import) - never .item (.item is the plugin's own saved-item format). Put the .import file in plugins/ItemsCore/imports/ and have the user run /ic import <name>. To change an existing item, build the updated JSON with the SAME name and import again - it overwrites and keeps stats/recipe (run /ic export <name> first to get the current JSON). STATS: read get_stat_schema, edit plugins/ItemsCore/stats/stats.yml directly (it is plain YAML), validate each stat with validate_stat, then have the user run /ic reload stats. COMMANDS: call list_commands to know every in-game command so you can help with anything. Items authored this way stay editable in the in-game GUI.

Known tools 12

search_methods

Search the ItemsCore scripting API for methods by name, category, signature, or description.

Inferred read-only

get_method

Get the full details (signature, params, return, description, example) of a specific method.

Inferred read-only

list_triggers

List every action trigger (when an item's actions can run, e.g.

Inferred read-only

list_events

List the custom events and the global scripting variables (player, event, core, particles, etc.) available when writing item actions.

Inferred read-only

get_item_schema

Get the full schema and field reference for the clean item JSON that ItemsCore imports.

Inferred read-only

validate_item

Validate a clean item JSON object against the ItemsCore schema (unknown methods, wrong argument count, wrong argument order/type).

Inferred read-only

generate_item_template

Return a valid starter item JSON to build from.

Inferred read-only

get_stat_schema

Get the format and field reference for ItemsCore stats (the named values like Strength shown on items).

Inferred read-only

validate_stat

Validate a single stat object (name, fancyName, fancyValue, baseValue) before writing it into stats.yml.

Inferred read-only

list_commands

List every in-game command of the ItemsCore plugin (and common addon commands) with usage, description and permission, so you can help the user run the plugin: import/export/reload items, manage stats, open editors, install addons, and more.

Potential side effects

check_updates

Report whether the API in use is current.

Inferred read-only

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.

Inferred read-only

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.

TRUST AND VERIFICATION EVIDENCE

Trust Data Available

BuiltWith Trust API v2 evidence for coredevelopment.shop was fetched 2026-08-08T12:36:10.975Z.

Trust status Neutral

coredevelopment.shop is assessed as Neutral: No suspicious signals found, but no strong positive signal either

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.