List your agent

coremodels

MCP server● Hosted · onlinev1.0.2

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

Reviews

No review yet. Used coremodels? Be the first to help others choose.

What it does

coremodels is an MCP server, a connector that lets an AI assistant use it as a tool. It is hosted: an assistant connects to it over the internet, nothing to install.

No capability identified yet from its description.

Facts come from the Official MCP Registry, as declared by the publisher. Capabilities are matched automatically (low confidence). None of this is a test of the tool.

At a glance

Hosted (remote)YES
Local installNO
Version1.0.2
PriceNot in the registry
First seen26 Sept 2026
Last checked1d ago

How to connect

As declared in the Official MCP Registry · hosted endpoint tested by Electra Index 12h ago (live check)

Hosted endpoint

  • https://go.coremodels.io/mcp streamable-http

In Claude Code: claude mcp add --transport http coremodels-1 https://go.coremodels.io/mcp

MCP settings (Claude Desktop, Cursor and other MCP clients)

{
  "mcpServers": {
    "coremodels-1": {
      "url": "https://go.coremodels.io/mcp"
    }
  }
}

Live check

Electra Index connected to the hosted endpoint 12h ago

ONLINE coremodels answered an MCP connection on 17 Nov 2026 and introduced itself as Schema Library MCP server with CoreModels support 1.0.0 (MCP protocol 2025-06-18).

41 tools offered to AI assistants

  • build_source_pack · Build the source pack for an artifact: a deterministic, sorted extract of the types, elements, taxonomies and relations in scope, plus a stamp with its packHash. Write the artifact only from this pack, then call check_grounding with the pac
  • check_artifact_freshness · Check whether an artifact is still current. Rebuilds the source pack for the same template and scope and compares its hash with the packHash the artifact was built from. state is current or stale. Pass the old pack too to get a diffSummary
  • check_grounding · Check an artifact output against its source pack (closed world). Every name in output.refs, every *Ref / *Refs value, every `backticked` name and every first cell of a table row must exist in the pack. Returns passed, checked, unresolved [{
  • diff_source_packs · Compare two source packs by id: types, elements, taxonomy terms and relations that were added, removed or changed. Use it as the basis of a change report. Read-only.
  • list_artifact_templates · List the artifact templates (data dictionary, model map, change report, ...). Each template has a family, audiences, formats, a pack recipe and an output contract. Your response for an artifact must follow its output contract; pass includeC
  • render_artifact · Render a grounded artifact output to text with a provenance footer (templateId, packHash, graphProjectId, builtAt, renderedAt). Formats: md (sections in contract order), mermaid (class diagram drawn from the pack; model-map only), json. Wit
  • export_avro · Export project data as an Avro (.avsc JSON) schema string.
  • analyze_concept_impact · Answers 'what is affected if this concept changes?' for a governed type, element or controlled vocabulary. Returns: where it is used inside the model (blast radius), which vendor estates carry it and by what path, which external standards i
  • audit_vendor_project · Audits vendor artifacts (e.g. a dbt manifest) against the governed CoreModels graph — read-only. Reports coverage (what is/isn't governed, canonical-mapping coverage), drift (fields added/removed/retyped, enum changes, contract flips), and
  • generate_vendor_artifacts · Generates vendor artifacts from the governed CoreModels graph. For dbt: a schema.yml with enforced model contracts — column data types, not_null/unique constraints and tests, accepted_values tests from governed taxonomies, relationships tes
  • get_vendor_integration_status · Lists the registered vendor connectors (dbt, ...) with capabilities and expected artifacts, and — when 'vendor' is given — the project's last-import state for that vendor (when, tool version, artifact versions, fingerprint, counts, governed
  • 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-
Show 29 more
  • fetch_json_ld_import_profiles · Fetch JSON-LD import/export profiles available for a project (id and label each). Pass configTypeId to read that one profile's field mapping instead: every JSON-LD key it knows and what the key imports as - importAs is mixin (target = mixin
  • export_jsonschema · Export project data as a JSON Schema string.
  • fetch_json_schema_import_profiles · Fetch JSON Schema import/export profiles available for a project (id and label each). Pass configTypeId to read that one profile's field mapping instead: every JSON Schema keyword it knows and what the keyword imports as - importAs is mixin
  • validate_json · Validate one or more JSON documents against a project's stored JSON Schema. The schema is regenerated from the project using the supplied configTypeId (the export profile id) and rootNodeId, then reused for every document - so validating a
  • export_linkml · Export project data as a LinkML (YAML) schema string.
  • list_comments · List the discussion (comments and replies) of a CoreModels project — the same threads users see in the app's grid collaboration panel. Viewer access is required. Comments are anchored by tag sets: a comment left on a grid cell carries that
  • get_job_status · Get the status of a background job in a project, e.g. the copy started by copy_project or a background import_owl. Returns { jobDetailsId, projectId, type, status, createdAt, lastUpdatedAt } where status is "inProgress", "success" or "faile
  • 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 - se
  • get_modeling_guide · Returns the CoreModels modeling guide (markdown): how to import vs build, what each relation group means and which direction it runs (Domain Includes, Range Includes, Controlled List, Has List Item, Inheritance, Derived From), bulk_create c
  • 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
  • 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=t
  • core_models_get_mixins_info · Get information about all mixins in a CoreModels project. Mixins define structured metadata used for mapping models, system integrations, and other extensions. Mixin values are attached to nodes; use search_nodes with includeMixins to see t
  • query_model_graphql · Run a read-only GraphQL query against a CoreModels project's model — the general query escape hatch for precise questions (projections, traversals, counts) that the fixed read tools don't answer. Viewer access is required, same as the app.
  • core_models_get_relation_groups_info · Get information about relation groups for a CoreModels project. Use the relation groups to create a relation between two 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 of the first three; they combine with AND): - nodeIds: exact id lookup - nodeType: one
  • whoami · Who is calling: returns the identity and subscription plan of the MCP token in use. No project id needed. Returns { userId, name, email, organizationId, plan }. plan holds the raw tier and expiry from the token plus the derived limits and p
  • suggest_ontology_terms · Suggest ontology-term candidates for a schema node from the public EMBL-EBI Ontology Lookup Service (OLS). ADVISORY ONLY: this is a read-only search — it calls the external EBI OLS API and returns ranked candidates, and it NEVER writes anyt
  • export_shex · Export project data as a ShEx (Shape Expressions) schema string.
  • export_sql · Export project data as a SQL DDL (CREATE TABLE) schema string.
  • export_owl · Export project schema as an OWL ontology (Turtle): owl:Class per Type, Datatype/ObjectProperty per Element with domain/range, rdfs:subClassOf inheritance, cardinality restrictions preserving required/array-ness, SKOS concept schemes per Tax
  • export_rml · Export the project as an RML mapping document (RML-Core + RML-IO, namespace http://w3id.org/rml/): one rml:TriplesMap per Type, an rml:logicalSource per source file or table, a subject template from the identifier element, one rml:predicate
  • generate_synapse_manifests · Generate Synapse curation-manifest CSV templates from a schema — the tabular companion to the transform_schema synapse export. Two artifacts per type: {name}.manifest.csv (the blank entry grid, header row only, loadable as a Curator RecordS
  • transform_schema · Transform a schema from one format to another through the ARAMAI mapping engine. Formats: jsonschema | shex | avro | jsonld | sql | osi | osi-json | owl | linkml | protobuf | odcs | graphql | odm | synapse (odm decodes only; osi-json is the
  • schema_library_query_project · Query and retrieve details of a SchemaLibrary project including metadata, classifications, likes, cover images, and user permissions. Authenticated callers receive additional user-specific data (e.g. ILiked, Role).
  • schema_library_get_metadata_options · Get available metadata options for SchemaLibrary projects (access methods, types, licenses, formats, domains, audiences, model sizes). Use these IDs when creating or updating projects. Optionally filter by category.
  • schema_library_get_classifications · Get available classification options for SchemaLibrary projects, used to categorize and tag projects. Optionally filter by classification name (partial match supported).
  • schema_library_projects_section · Search and retrieve a filtered, paginated list of SchemaLibrary projects with advanced filtering options including metadata, classifications, and project attributes.
  • schema_library_get_use_case_types · Get available use case types for SchemaLibrary projects. Use these types when creating new use cases for a project.
  • 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

What "online" means: the server answered an MCP connection at the time of the check. It is not a guarantee of security, quality or continuous uptime. How we test: we open an MCP session and ask for the tool list, as an AI assistant would. We never run a tool and never send a key. Checked every few days. Method

Is this your server? Monitoring Pro: a check every 30 minutes and an email within the hour when it stops answering. Launch offer: $39.99 once, for life.

Facts & evidence

Each fact shows where it was seen and when.
FactValueEvidenceSourceLast confirmed
Hosted endpointhttps://go.coremodels.io/mcpDECLAREDSRC-001 Official MCP Registry1d ago
Local install (package)noDECLAREDSRC-001 Official MCP Registry1d ago
Remote access (hosted)yesDECLAREDSRC-001 Official MCP Registry1d ago
Registry statusactiveDECLAREDSRC-001 Official MCP Registry1d ago
Version1.0.2DECLAREDSRC-001 Official MCP Registry1d ago
MCP serveryesDECLAREDSRC-001 Official MCP Registry1d ago

Change history

Baseline
No change detected yet. History builds up as the robots revisit this server.

Is this page accurate?

Flag it and our robot re-checks the official source. Reports never change a score.

Do you run coremodels? Know when it stops answering

For publishers · optional

Its hosted endpoint can be monitored. Monitoring Pro connects every 30 minutes like an AI assistant, emails you within the hour when it stops answering, keeps a 90-day availability history and adds your answer rate to your badge.

Monitor coremodelsLaunch offer $39.99 once, for life instead of $9.99/month · All plans

Monitoring never changes a score or a rank.

Are you the publisher of coremodels?

Free · show your listing

An independent listing builds trust with your buyers. Announce it, and add the badge to your website or README.

Announce it on LinkedIn
Listed on Electra IndexListed on Electra Index
<a href="https://electraindex.com/mcp/coremodels-1?utm_source=badge&utm_medium=share&utm_campaign=listing"><img src="https://electraindex.com/api/badge/coremodels-1/card" width="260" height="72" alt="Listed on Electra Index"></a>

Questions about coremodels

How do I connect coremodels?

Use the hosted endpoint https://go.coremodels.io/mcp in your assistant's MCP settings. The exact settings are in "How to connect" above, as declared in the Official MCP Registry.

What tools does coremodels offer?

When Electra Index connected on 17 Nov 2026, it listed 41 tools: build_source_pack, check_artifact_freshness, check_grounding, diff_source_packs, list_artifact_templates, render_artifact, export_avro, analyze_concept_impact and more. The full list is in "Live check" above.

Is coremodels online?

Yes. Its hosted endpoint answered an MCP connection from Electra Index 12h ago.