# CoreModels (remote · go.coremodels.io)

CoreModels schema editor: nodes, mixins, relations, JSON Schema import/export. Sign-in required.

- Trust score: 63/100 (medium)
- Change this week: +5
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-04

## Components

- remote · `go.coremodels.io`: 63/100 (this document), [markdown](https://verifymcp.io/servers/aramai-schematica-coremodels/mcp-admin.md), [page](https://verifymcp.io/servers/aramai-schematica-coremodels/mcp-admin)

## Channel facts

- Endpoint: `https://go.coremodels.io/mcp-admin`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-04.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (import_jsonschema).
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 63/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 2491 tokens (~108/item across 23 items; 23 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 30/100
  - Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 77/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 32% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http aramai-schematica-coremodels https://go.coremodels.io/mcp-admin
```

### Codex

```toml
[mcp_servers.aramai-schematica-coremodels]
url = "https://go.coremodels.io/mcp-admin"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "aramai-schematica-coremodels": {
      "type": "remote",
      "url": "https://go.coremodels.io/mcp-admin",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add aramai-schematica-coremodels --url https://go.coremodels.io/mcp-admin --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  aramai-schematica-coremodels:
    url: "https://go.coremodels.io/mcp-admin"
```

### Other

```json
{
  "mcpServers": {
    "aramai-schematica-coremodels": {
      "type": "http",
      "url": "https://go.coremodels.io/mcp-admin"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-04 (score 63, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-02 (score 62, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-01 (score 61, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-31 (score 60, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 59, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-28 (score 58, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 57, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 57)

First indexed and scored.

## MCP tools (23)

### `export_json_ld` (~231 tokens)

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.

Input parameters:

- `configTypeId` (string, required): JSON-LD export profile id (from fetch_json_ld_import_profiles)
- `exportDataTypes` (boolean)
- `exportElements` (boolean)
- `exportTaxonomies` (boolean)
- `exportTypes` (boolean)
- `graphBased` (boolean): true = graph-based (no root); false = tree-based (requires exactly one nodeId)
- `graphProjectId` (string, required)
- `includeSpace` (boolean)
- `nodeIds` (array): For tree-based export, exactly one root node id; for graph-based, optional
- `spaceId` (string): Optional space id to filter export data; empty = all spaces
- `useDefaultType` (boolean)

### `fetch_json_ld_import_profiles` (~32 tokens)

Fetch JSON-LD Import Profiles

Fetch JSON-LD import/export profiles available for a project.

Input parameters:

- `graphProjectId` (string, required)

### `export_jsonschema` (~77 tokens)

Export JSON Schema

Export project data as a JSON Schema string.

Input parameters:

- `configTypeId` (string): Export profile id used for the JSON Schema export.
- `graphProjectId` (string, required)
- `rootNodeId` (string): Optional root node id; empty/omitted to export without a fixed root.
- `spaceId` (string)

### `fetch_json_schema_import_profiles` (~31 tokens)

Fetch JSON Schema Import Profiles

Fetch JSON Schema import/export profiles available for a project.

Input parameters:

- `graphProjectId` (string, required)

### `import_jsonschema` (~34 tokens)

Import JSON Schema

Imports a JSON Schema into a space

Input parameters:

- `graphProjectId` (string, required)
- `importDto` (object, required)

### `validate_json` (~136 tokens)

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.

Input parameters:

- `configTypeId` (string): Profile id used to map mixins/relations to schema keywords
- `graphProjectId` (string, required)
- `jsonString` (string, required): The JSON document to validate, serialized as a string
- `rootNodeId` (string, required): Node id used as the root when generating the JSON Schema
- `spaceId` (string): Optional space id to scope the schema

### `bulk_create` (~170 tokens)

Bulk Create

Create multiple nodes, relations, and mixin values in one atomic operation.

When to use:
\- Creating more than one node.
\- Any creation that includes relations and/or mixins.
\- For a single node with no relations/mixins, prefer create_node.

Required ids come from:
\- get_mixins_and_relation_groups: relationGroupId, mixinId, and each mixin column id.
\- get_project_summary or search_nodes (nodeType=Space): spaceIds, plus any existing nodeIds you want to reference.

Relation endpoints (fromNodeId / toNodeId) may be either:
\- ids of nodes created elsewhere in this same payload, or
\- ids of nodes already in the project.

Input parameters:

- `bulkCreateDto` (object, required)
- `graphProjectId` (string, required)

### `create_mixin_type` (~63 tokens)

Create Mixin Type

Create a new mixin type. Check existing mixins first with get_mixins_and_relation_groups to avoid duplicates. Mixins are reusable property sets applicable to any node.

Input parameters:

- `graphProjectId` (string, required)
- `mixinTypeDto` (object, required)

### `create_project` (~135 tokens)

Create Project

Create a new CoreModels project owned by the calling user, including a ready-to-use default space. Returns { projectId, defaultSpaceId }; use projectId as graphProjectId and defaultSpaceId as a spaceId in other tools (e.g. import_jsonschema). Projects are created private in the caller's default workspace. Fails (no silent duplicate) if the caller already has a project with the same name.

Input parameters:

- `defaultSpaceName` (string): Optional label for the default space created inside the new project.
- `name` (string, required): Name of the new project. Must not match an existing project of the caller.

### `generate_project_ai_summary` (~144 tokens)

Generate Project Ai Summary

Generate an AI summary of the project (from its types, elements and taxonomies) and save it as the project's markdown AI summary. Returns the generated summary. If a summary already exists it is returned unchanged unless regenerateIfStale=true (default) and the project has been updated since the summary was generated (stale). Requires the user to have a Claude API key configured in ChatBot settings.

Input parameters:

- `graphProjectId` (string, required)
- `regenerateIfStale` (boolean): When true (default), regenerate and overwrite the summary if the project has been updated since the summary was generated (stale). When false, an existing summary is always returned unchanged.

### `get_mixins_and_relation_groups` (~80 tokens)

Get Mixins & 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.

Input parameters:

- `graphProjectId` (string, required)

### `get_project_summary` (~107 tokens)

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.

Input parameters:

- `graphProjectId` (string, required)
- `page` (integer): 0-based page index, applied independently to each category.
- `pageSize` (integer)

### `list_projects` (~237 tokens)

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.

Input parameters:

- `includeAISummary` (boolean): When true, each project row includes its saved AI-generated summary (markdown) and the time it was generated as 4th and 5th elements, or null if none has been generated.
- `includePublicProjects` (boolean): When true, public projects the user is not a member of are also included.
- `page` (integer): 1-based page number. Increment to page through results up to totalPages.
- `pageSize` (integer)
- `searchTerm` (string): Optional case-insensitive substring to filter projects by name.

### `create_mixin_value` (~69 tokens)

Create Mixin Value

Create a mixin value for a node. mixinId and column ids come from get_mixins_and_relation_groups. A node can have multiple mixins; each mixin can have multiple columns.

Input parameters:

- `graphProjectId` (string, required)
- `mixinCreateDto` (object, required)

### `remove_mixin_value` (~66 tokens)

Remove Mixin Value

Remove one or more mixin column values from a node. mixinId and column ids come from get_mixins_and_relation_groups. This does not delete the mixin definition itself.

Input parameters:

- `graphProjectId` (string, required)
- `mixinRemoveDto` (object, required)

### `create_node` (~51 tokens)

Create Node

Create a new node. Empty/omitted spaceIds = default space; MUST be empty when nodeType is 'Space'.

Input parameters:

- `graphProjectId` (string, required)
- `nodeCreateDto` (object, required)

### `update_node` (~72 tokens)

Update Node

Update an existing node's label and/or its space assignments. Omitted fields are unchanged. spaceIds replaces (not merges) existing assignments; empty array = default space. At least one of label or spaceIds must be provided.

Input parameters:

- `graphProjectId` (string, required)
- `nodeUpdateDto` (object, required)

### `remove_node` (~29 tokens)

Remove Node

Suspend a node.

Input parameters:

- `graphProjectId` (string, required)
- `nodeId` (string, required)

### `create_relation` (~54 tokens)

Create Relation

Create a directed relation fromNodeId → toNodeId. relationGroupId is the relation template; list templates with get_mixins_and_relation_groups.

Input parameters:

- `graphProjectId` (string, required)
- `relation` (object, required)

### `remove_relation` (~31 tokens)

Remove Relation

Remove a relation between two nodes.

Input parameters:

- `graphProjectId` (string, required)
- `relation` (object, required)

### `search_nodes` (~311 tokens)

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.

Input parameters:

- `expression` (string): Partial substring match against the node label. Plain text only - no wildcards, no regex, no '*', '%', '_' or '?' characters; the literal characters are matched as-is.
- `graphProjectId` (string, required)
- `includeMixins` (boolean)
- `includeRelations` (boolean)
- `nodeIds` (array)
- `nodeType` (string)
- `pageSize` (integer)
- `pagingToken` (string): Pagination token from the previous response. Always use the latest one.
- `sortAttr` (string)
- `sortDesc` (boolean)
- `spaceIds` (array)

### `export_shex` (~91 tokens)

Export ShEx

Export project data as a ShEx (Shape Expressions) schema string.

Input parameters:

- `graphProjectId` (string, required)
- `includeCardinality` (boolean): Whether to emit ShEx cardinality markers (?, *, +). Defaults to true.
- `nodeIds` (array): Optional type node ids to export; omit to export all types (optionally scoped to a space).
- `spaceId` (string)

### `run_code` (~240 tokens)

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.

Input parameters:

- `code` (string, required): JavaScript to execute. Use tools.<name>(args), listTools(), getToolDoc(name); end with `return <value>`.
- `graphProjectId` (string, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/aramai-schematica-coremodels/mcp-admin#diagnostics

## Score history

- 2026-08-04: 63
- 2026-08-03: 62
- 2026-08-02: 62
- 2026-08-01: 61
- 2026-07-31: 60
- 2026-07-29: 59
- 2026-07-28: 58
- 2026-07-27: 57
- 2026-07-26: 57

## Links

- Remote endpoint: https://go.coremodels.io/mcp-admin
- Authorisation metadata: https://go.coremodels.io/.well-known/oauth-protected-resource/mcp-admin
- Website: https://www.aramai.net/products/coremodels
- Changelog RSS feed: https://verifymcp.io/servers/aramai-schematica-coremodels/mcp-admin/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/aramai-schematica-coremodels/mcp-admin/changelog.json
- HTML version of this page: https://verifymcp.io/servers/aramai-schematica-coremodels/mcp-admin