mcpbeat

Coremodels MCP Server

io.github.qg-aramai/coremodels
answering

Coremodels is answering right now. Last checked 9 min ago. It exposes 11 tools.

Schema modeling in JSON, JSON-LD, and other formats with CoreModels platform.

Uptime history 41 hours of history
41 hours agonow
100.0%
Uptime 24h
91 of 91 checks
11
Tools
read from the server
978 ms
Response time
average over 24h
open, no key
Access
streamable-http

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 9 min ago.

run in your terminal
claude mcp add coremodels --transport http https://go.coremodels.io/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "coremodels": {
      "url": "https://go.coremodels.io/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.coremodels]
url = "https://go.coremodels.io/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "coremodels": {
      "url": "https://go.coremodels.io/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "coremodels": {
      "url": "https://go.coremodels.io/mcp"
    }
  }
}

Available tools 11

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

export
export_json_ld
Export project data in JSON-LD format using a configured export profile. Use `fetch_json_ld_import_profiles` first to discover the configTypeId. At least one of exportTypes/exportElements/exportTaxonomies/exportDataTypes must be true. Tree-based mode (graphBased=false) requires exactly one nodeId; graph-based mode allows multiple or none.
export_jsonschema
Export project data as a JSON Schema string.
export_shex
Export project data as a ShEx (Shape Expressions) schema string.
json
fetch_json_ld_import_profiles
Fetch JSON-LD import/export profiles available for a project.
fetch_json_schema_import_profiles
Fetch JSON Schema import/export profiles available for a project.
code
run_code
Execute a JavaScript program that orchestrates this server's tools, and return only its result. Prefer this over many individual tool calls when a task needs several steps, looping, filtering, or combining data: intermediate results stay in the sandbox, so only what you return reaches the model. Inside the script: - listTools() -> [{name, summary}] discover available tools - getToolDoc(name) -> {name, description, parameters, required} inspect one tool's inputs - tools.<name>(args) -> parsed result call a tool (graphProjectId is injected automatically; do NOT pass it) - console.log(...) captured and returned alongside the result - return <value> JSON-serialized and returned Environment: sandboxed JavaScript, no network or filesystem, with limits on time, memory, statements and number of tool calls. Currently only read-only tools are callable from code.
mixins
get_mixins_and_relation_groups
Get the project schema: all mixin definitions and all relation-group definitions. Use this once at the start of a session to discover the IDs needed by other tools (mixinId, columnId, relationGroupId). Returns compact positional arrays - see the "format" field for the layout.
nodes
search_nodes
Search nodes in a CoreModels project. Returns compact positional arrays; the response "format" field describes the layout. Filters (provide at least one; they combine with AND): - nodeIds: exact id lookup - nodeType: one of Element, Type, Taxonomy, Exemplar, Component, Space, Tag, Mixin - expression: partial substring match on the node label (plain text, no wildcards) - spaceIds: restrict to specific spaces Optional flags: includeRelations, includeMixins, sortAttr, sortDesc, pageSize. Pagination: - First call: omit pagingToken. - If the response has a pagingToken, more pages exist. Repeat the same call with that exact token to get the next page. - If the response has no pagingToken, this was the last page.
project
get_project_summary
Labels and IDs of types, elements, and taxonomies in the project. Each category is paginated independently. Pagination: - First call: omit page (defaults to 0). - Each category reports page, pageSize and hasMore. Re-request with page+1 for any category whose hasMore is true.
projects
list_projects
List the user's CoreModels projects as [id,name,accessLevel] (see the response "format" field). Use a returned id as graphProjectId for other tools. Pass searchTerm to filter by name (case-insensitive substring). Set includePublicProjects=true to also include public projects. Set includeAISummary=true to also return each project's saved AI-generated summary and the time it was generated (4th and 5th elements). Paged: page is 1-based; increment page up to the returned totalPages to get all results.
validate
validate_json
Validate a JSON document against a project's stored JSON Schema. The schema is regenerated from the project using the supplied configTypeId (the export profile id) and rootNodeId. Provide the JSON to validate as a serialized string.

Endpoints

URLTransportStateLatencyChecked
https://go.coremodels.io/mcp streamable-http answering 1098 ms 9 min ago

Coremodels — questions

Answers built from our own checks of this server.

What can Coremodels do?
It exposes 11 tools, read directly from the server on our last check. Among them: export_json_ld, export_jsonschema, export_shex, fetch_json_ld_import_profiles, fetch_json_schema_import_profiles, get_mixins_and_relation_groups and 5 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
What is Coremodels mostly used for?
Its tools cluster around export and json. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.
Is Coremodels working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 978 ms. The bar chart above shows every period we have measured.
How do I connect Coremodels?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Coremodels need an API key?
No. Coremodels completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 11 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Coremodels?
It answers our handshake in 978 ms on average, which is faster than 5% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.