Skip to content

MCP servers › io.coremodels › coremodels

MCP server · registry snapshot 2026-11-17 · last tested 2026-11-17

coremodels MCP server

Registry name io.coremodels/coremodels

by coremodels.io · domain (the registry's namespace rule)Website ↗

Model, map and validate data schemas. Export JSON Schema, JSON-LD, LinkML, OWL, ShEx, SQL, Avro. — the publisher's description

1 of 2 record checks metRead-only · tools listed 2026-11-17version 1.1.0streamable HTTP41 tools

Summary

io.coremodels/coremodels is a remote MCP server listed in the official MCP registry at version 1.1.0, under the namespace of the domain coremodels.io. On 2026-11-17 ProtocolProbe connected to it in read-only mode and read its inventory: 41 tools, 0 resources and 0 prompts.

Record checks

1 of 2 record checks met · 7 do not apply

  • met: Registry entry is active and says how to run it
  • not met: Source repository link opens
  • not applicable: Repository is not archived
  • not applicable: Code pushed to the repository in the 90 days before our check
  • not applicable: Repository publishes a security policy (SECURITY.md)
  • not applicable: Package names its licence with a standard (SPDX) identifier
  • not applicable: The version the registry lists can be installed and is not withdrawn
  • not applicable: npm package carries build provenance (attestation)
  • not applicable: No known critical or high advisory in the package or its dependencies
  • Not ranked by downloads: a remote server publishes no download figure
  • Not ranked by stars: no public GitHub repository

From public records, not a safety rating. Each check with its reason

Operate this server? Correct a fact · README badge · Run the checks yourself · Claim it

Key facts

Runs
remote (hosted by the publisher)
Transport
streamable HTTP
Your own values
none declared (not a guarantee)
Sign-in
none needed to open a session
Tools
41
Last tested
2026-11-17

Tool list size

18,297 tokens on Claude Opus 5.5

Added to every request that loads this server's tools (41 tools). Counted with Anthropic's token counter on 2026-11-17, from the tool list we read on 2026-11-17. Median across 28,560 counted servers: 2,657 tokens. How it is counted

How a client gets in

Connects without signing in

Read from the server's public metadata on 2026-11-17 (go.coremodels.io), in our read-only connection; no tool was called. It may have changed since. How it is read

Tool list at the three APIs

Not sent yet for this version (1.1.0).

Add to your client

How fresh this is

Live-tested
yes, a real session (not a text-only review)
Last tested
2026-11-17
Mode
read-only (no tool calls)
Latest version
1.1.0, published 2026-11-16 (registry, as of the 2026-11-17 snapshot)
First listed version
2026-11-16 (earliest version still in the registry; older removed versions would be earlier)
Registry data
snapshot 2026-11-17
Package and repository
checked 2026-11-17
Engine
mcp-runtime-engine@0.1.0 · sdk@1.32.0

Dead or stale signals

None found in the records we hold

Looked for and not found: deprecated in the registry. Does not apply: listed version cannot be installed or is withdrawn; repository link does not open; repository archived; no push in over 365 days. Each line is a dated fact from a public record. It does not say whether the server still works, and a record can change after the date shown.

Changes since the last refresh

New in the registry: not in the list of 2026-11-16, listed on 2026-11-17 with version 1.1.0 (published 2026-11-16).

Source: the official MCP Registry list on 2026-11-16 and on 2026-11-17.

What it is

What does this server offer?

Observed inventory
41tools
0resources
0prompts

None of its 41 tools are described as changing anything. For 41 the reading was uncertain, so no mark is shown.

  • 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.”

    Publisher declares: read-only yes · open-world no

    5 inputs, 2 required
    • graphProjectIdstringrequired
    • templateIdstringrequired“Template id from list_artifact_templates, e.g.”
    • spaceIdstring
    • typeIdsarray“Optional type node ids; omit for every type in scope (optionally within spaceId).”
    • provenanceNotestring“Optional note stamped into provenance, for example 'pre-product bridge: rendered outside CoreModels from gated output'”
  • check_artifact_freshness

    “Check whether an artifact is still current.”

    Publisher declares: read-only yes · open-world no

    6 inputs, 3 required
    • graphProjectIdstringrequired
    • templateIdstringrequired
    • spaceIdstring
    • typeIdsarray
    • packHashstringrequired“stamp.packHash of the artifact.”
    • packobject“Optional.”
  • check_groundingon 3 other servers

    “Check an artifact output against its source pack (closed world).”

    Publisher declares: read-only yes · open-world no

    4 inputs, 3 required
    • graphProjectIdstringrequired
    • packobjectrequired“The pack object returned by build_source_pack, unchanged.”
    • outputobjectrequired“Your artifact output.”
    • stampobject“Optional.”
  • diff_source_packs

    “Compare two source packs by id: types, elements, taxonomy terms and relations that were added, removed or changed.”

    Publisher declares: read-only yes · open-world no

    3 inputs, 3 required
    • graphProjectIdstringrequired
    • fromPackobjectrequired“The older pack.”
    • toPackobjectrequired“The newer pack.”
  • list_artifact_templates

    “List the artifact templates (data dictionary, model map, change report, ...).”

    Publisher declares: read-only yes · open-world no

    4 inputs, 1 required
    • graphProjectIdstringrequired
    • audiencestring
    • familystring
    • includeContractboolean“Include each template's output contract (a JSON Schema).”
  • render_artifacton 1 other server

    “Render a grounded artifact output to text with a provenance footer (templateId, packHash, graphProjectId, builtAt, renderedAt).”

    Publisher declares: read-only yes · open-world no

    6 inputs, 4 required
    • graphProjectIdstringrequired
    • templateIdstringrequired
    • formatstringrequired
    • outputobject“The output that passed check_grounding.”
    • stampobjectrequired“The stamp returned by build_source_pack.”
    • packobject“Optional.”
  • export_avro

    “Export project data as an Avro (.avsc JSON) schema string.”

    Publisher declares: read-only yes · open-world no

    3 inputs, 1 required
    • graphProjectIdstringrequired
    • spaceIdstring
    • nodeIdsarray“Optional type node ids to export; omit to export all types (optionally scoped to a space).”
  • analyze_concept_impact

    “Answers 'what is affected if this concept changes?' for a governed type, element or controlled vocabulary.”

    Publisher declares: read-only yes · open-world no

    3 inputs, 2 required
    • graphProjectIdstringrequired
    • conceptstringrequired“The governed type, element or taxonomy — by node id, or by label (case-insensitive), e.g.”
    • spacesarray
  • audit_vendor_project

    “Audits vendor artifacts (e.g.”

    Publisher declares: read-only yes · open-world yes

    5 inputs, 2 required
    • graphProjectIdstringrequired
    • vendorstringrequired“Vendor connector key, e.g.”
    • artifactsobject“Artifact name -> raw content.”
    • artifactUrlsobject“Artifact name -> URL to fetch it from (for payloads too large to inline).”
    • spacesarray“Optional target space ids.”
  • generate_vendor_artifacts

    “Generates vendor artifacts from the governed CoreModels graph.”

    Publisher declares: read-only yes · open-world no

    7 inputs, 2 required
    • graphProjectIdstringrequired
    • vendorstringrequired“Vendor connector key, e.g.”
    • typeNamesarray“Restrict generation to these model/type names (empty = everything eligible).”
    • targetVersionstring“Vendor dialect/version.”
    • layoutstring“dbt file layout: 'model' (default) one property file per model colocated with its .sql; 'folder' one file per model directory; 'single' one repo-wide file.”
    • iriInDescriptionboolean“dbt: also append bound ontology IRIs to the column description so persist_docs carries them into the warehouse column comment.”
    • spacesarray
  • 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, artifac…”

    Publisher declares: read-only yes · open-world no

    3 inputs, 1 required
    • graphProjectIdstringrequired
    • vendorstring“Omit to list all registered vendor connectors.”
    • spacesarray
  • export_json_ld

    “Export project data in JSON-LD format using a configured export profile.”

    Publisher declares: read-only yes · open-world no

    11 inputs, 2 required
    • graphProjectIdstringrequired
    • configTypeIdstringrequired“JSON-LD export profile id (from fetch_json_ld_import_profiles)”
    • exportTypesboolean
    • exportElementsboolean
    • exportTaxonomiesboolean
    • exportDataTypesboolean
    • graphBasedboolean“true = graph-based (no root); false = tree-based (requires exactly one nodeId)”
    • spaceIdstring“Optional space id to filter export data; empty = all spaces”
    • nodeIdsarray“For tree-based export, exactly one root node id; for graph-based, optional”
    • includeSpaceboolean
    • useDefaultTypeboolean
Show 29 more tools
  • fetch_json_ld_import_profiles

    “Fetch JSON-LD import/export profiles available for a project (id and label each).”

    Publisher declares: read-only yes · open-world no

    2 inputs, 1 required
    • graphProjectIdstringrequired
    • configTypeIdstring“Optional.”
  • export_jsonschema

    “Export project data as a JSON Schema string.”

    Publisher declares: read-only yes · open-world no

    4 inputs, 1 required
    • graphProjectIdstringrequired
    • spaceIdstring
    • configTypeIdstring“Export profile id used for the JSON Schema export.”
    • rootNodeIdstring“Optional root node id; empty/omitted to export without a fixed root.”
  • fetch_json_schema_import_profiles

    “Fetch JSON Schema import/export profiles available for a project (id and label each).”

    Publisher declares: read-only yes · open-world no

    2 inputs, 1 required
    • graphProjectIdstringrequired
    • configTypeIdstring“Optional.”
  • validate_jsonon 20 other servers

    “Validate one or more JSON documents against a project's stored JSON Schema.”

    Publisher declares: read-only yes · open-world no

    6 inputs, 3 required
    • graphProjectIdstringrequired
    • configTypeIdstring“Profile id used to map mixins/relations to schema keywords”
    • rootNodeIdstringrequired“Node id used as the root when generating the JSON Schema”
    • spaceIdstring“Optional space id to scope the schema”
    • explainboolean“Add a plain-English explanation to each error alongside the raw structured fields.”
    • jsonStringsarrayrequired“The JSON documents to validate, each serialized as a string.”
  • export_linkml

    “Export project data as a LinkML (YAML) schema string.”

    Publisher declares: read-only yes · open-world no

    3 inputs, 1 required
    • graphProjectIdstringrequired
    • spaceIdstring
    • nodeIdsarray“Optional type node ids to export; omit to export all types (optionally scoped to a space).”
  • list_commentson 31 other servers

    “List the discussion (comments and replies) of a CoreModels project — the same threads users see in the app's grid collaboration panel.”

    Publisher declares: read-only yes · open-world no

    6 inputs, 1 required
    • graphProjectIdstringrequired“Id of the project whose discussion to read.”
    • anchorIdsarray“Optional cell anchor: return only comments whose anchor tag set equals exactly this set.”
    • textContainsstring“Optional text filter, matched in comments and replies.”
    • includeResolvedboolean“Also return resolved (closed) threads.”
    • includeRepliesboolean“Nest each thread's replies in the response.”
    • maxResultsinteger“Cap on returned top-level threads (newest first); truncated=true when more matched.”
  • get_job_statuson 37 other servers

    “Get the status of a background job in a project, e.g.”

    Publisher declares: read-only yes · open-world no

    2 inputs, 2 required
    • graphProjectIdstringrequired“Id of the project the job belongs to.”
    • jobDetailsIdstringrequired“The jobDetailsId returned by the tool that started the job.”
  • get_mixins_and_relation_groups

    “Get the project schema: all mixin definitions and all relation-group definitions.”

    Publisher declares: read-only yes · open-world no

    1 input, 1 required
    • graphProjectIdstringrequired
  • 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, …”

    Publisher declares: read-only yes · open-world no

    Takes no inputs.

  • get_project_summaryon 6 other servers

    “Labels and IDs of types, elements, and taxonomies in the project.”

    Publisher declares: read-only yes · open-world no

    3 inputs, 1 required
    • graphProjectIdstringrequired
    • pageinteger“0-based page index, applied independently to each category.”
    • pageSizeinteger
  • “List the user's CoreModels projects as [id,name,accessLevel] (see the response "format" field).”

    Publisher declares: read-only yes · open-world no

    5 inputs
    • searchTermstring“Optional case-insensitive substring to filter projects by name.”
    • includePublicProjectsboolean“When true, public projects the user is not a member of are also included.”
    • includeAISummaryboolean“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 …”
    • pageinteger“1-based page number.”
    • pageSizeinteger
  • core_models_get_mixins_info

    “Get information about all mixins in a CoreModels project.”

    Publisher declares: read-only yes · open-world no

    1 input, 1 required
    • graphProjectIdstringrequired
  • 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.”

    Publisher declares: read-only yes · open-world no

    4 inputs, 1 required
    • graphProjectIdstringrequired“Id of the project to query.”
    • querystring“GraphQL query document (query operations only; no variables — inline all literals).”
    • schemaOnlyboolean“Return the project's generated GraphQL schema as SDL without executing anything.”
    • maxCharsinteger“Cap on the serialized result size.”
  • core_models_get_relation_groups_info

    “Get information about relation groups for a CoreModels project.”

    Publisher declares: read-only yes · open-world no

    1 input, 1 required
    • graphProjectIdstringrequired
  • search_nodeson 9 other servers

    “Search nodes in a CoreModels project.”

    Publisher declares: read-only yes · open-world no

    13 inputs, 1 required
    • graphProjectIdstringrequired
    • nodeTypestring
    • nodeIdsarray
    • expressionstring“Partial substring match against the node label.”
    • spaceIdsarray
    • includeRelationsboolean
    • includeMixinsboolean
    • includeTimestampsboolean“Adds creationTime and updateTime (ISO 8601 UTC) to each node.”
    • sortAttrstring
    • sortDescboolean
    • pageSizeinteger
    • pageinteger“1-based page number.”
    • limitPerRelationGroupinteger“Only with includeRelations.”
  • “Who is calling: returns the identity and subscription plan of the MCP token in use.”

    Publisher declares: read-only yes · open-world no

    Takes no inputs.

  • suggest_ontology_terms

    “Suggest ontology-term candidates for a schema node from the public EMBL-EBI Ontology Lookup Service (OLS).”

    Publisher declares: read-only yes · open-world yes

    6 inputs, 1 required
    • graphProjectIdstringrequired
    • nodeIdstring“The schema node to ground.”
    • labelstring“A raw term label to search for.”
    • descriptionstring“Optional description text to refine the search ranking.”
    • ontologiesstring“Optional comma-separated ontology ids to restrict to, e.g.”
    • limitinteger“Maximum candidates to return (1-50).”
  • export_shex

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

    Publisher declares: read-only yes · open-world no

    4 inputs, 1 required
    • graphProjectIdstringrequired
    • spaceIdstring
    • nodeIdsarray“Optional type node ids to export; omit to export all types (optionally scoped to a space).”
    • includeCardinalityboolean“Whether to emit ShEx cardinality markers (?, *, +).”
  • “Export project data as a SQL DDL (CREATE TABLE) schema string.”

    Publisher declares: read-only yes · open-world no

    3 inputs, 1 required
    • graphProjectIdstringrequired
    • spaceIdstring
    • nodeIdsarray“Optional type node ids to export; omit to export all types (optionally scoped to a space).”
  • 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…”

    Publisher declares: read-only yes · open-world no

    2 inputs, 1 required
    • graphProjectIdstringrequired
    • spaceIdstring
  • 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 …”

    Publisher declares: read-only yes · open-world no

    6 inputs, 1 required
    • graphProjectIdstringrequired
    • spaceIdstring
    • baseIristring“Namespace subject IRIs are built under, e.g.”
    • sourceKindstring
    • sourceTemplatestring“Path or table per type, with {type} substituted, e.g.”
    • sourceFormstring“shorthand (default) is what RML engines accept today; rml-io is the newer structured source form”
  • generate_synapse_manifests

    “Generate Synapse curation-manifest CSV templates from a schema — the tabular companion to the transform_schema synapse export.”

    Publisher declares: read-only yes · open-world no

    4 inputs, 3 required
    • graphProjectIdstringrequired
    • sourceFormatstringrequired“jsonschema | shex | avro | jsonld | sql | osi | osi-json | owl | linkml | odm”
    • sourceSchemastringrequired“The source schema text.”
    • typeIdstring“Generate manifests for this type only (matched by id or label).”
  • transform_schema

    “Transform a schema from one format to another through the ARAMAI mapping engine.”

    Publisher declares: read-only yes · open-world yes

    13 inputs, 4 required
    • graphProjectIdstringrequired
    • sourceFormatstringrequired“jsonschema | shex | avro | jsonld | sql | osi | osi-json | owl | linkml | protobuf | odcs | graphql | odm”
    • sourceSchemastringrequired“The source schema text.”
    • targetFormatstringrequired“jsonschema | shex | avro | jsonld | sql | osi | osi-json | owl | linkml | protobuf | odcs | graphql | synapse”
    • vendorstring“For sql output: postgres (default) | mysql | sqlserver.”
    • synapseOrgstring“For synapse output: the Synapse Organization name for the $id (default 'example'; org.sagebionetworks is reserved).”
    • synapseNamestring“For synapse output: the schema name segment of the $id (default: derived from the root type).”
    • synapseVersionstring“For synapse output: the semver segment of the $id (default 0.0.1; Synapse rejects re-registering an existing version).”
    • targetHintFormatstring“Format of the optional target hint schema.”
    • targetHintSchemastring“The schema to map toward.”
    • mappingKindstring“inferred (default) | explicit | ai”
    • guidestring“For explicit mapping: the SIA mapping guide as JSON text.”
    • caseInsensitiveboolean“Inferred mapping: ignore label case (default true).”
  • schema_library_query_project

    “Query and retrieve details of a SchemaLibrary project including metadata, classifications, likes, cover images, and user permissions.”

    Publisher declares: read-only yes · open-world no

    1 input, 1 required
    • projectIdstringrequired“The SchemaLibrary project ID”
  • schema_library_get_metadata_options

    “Get available metadata options for SchemaLibrary projects (access methods, types, licenses, formats, domains, audiences, model sizes).”

    Publisher declares: read-only yes · open-world no

    1 input
    • categorystring“Filter by metadata category (optional)”
  • schema_library_get_classifications

    “Get available classification options for SchemaLibrary projects, used to categorize and tag projects.”

    Publisher declares: read-only yes · open-world no

    1 input
    • nameFilterstring“Filter by classification name (optional - 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.”

    Publisher declares: read-only yes · open-world no

    19 inputs
    • titlestring“Search by project title (partial match)”
    • graphProjectTypestring“Graph project type filter (e.g.”
    • pageSizeinteger
    • pageinteger
    • classificationIdsstring“Comma-separated classification IDs”
    • onlyFavoriteProjectsboolean“Authenticated only”
    • onlyMyProjectsboolean“Authenticated only”
    • isExternalboolean
    • isFeaturedboolean
    • publishStatestring
    • sortBystring
    • typeIdstring
    • licenseIdstring
    • modelSizeIdstring
    • accessTypeIdstring
    • accessMethodIdstring
    • formatIdsstring“Comma-separated format IDs”
    • domainIdsstring“Comma-separated domain IDs”
    • audienceIdsstring“Comma-separated audience IDs”
  • schema_library_get_use_case_types

    “Get available use case types for SchemaLibrary projects.”

    Publisher declares: read-only yes · open-world no

    Takes no inputs.

  • “Execute a JavaScript program that orchestrates this server's tools, and return only its result.”

    Publisher declares: read-only yes · open-world no

    3 inputs, 2 required
    • graphProjectIdstringrequired
    • codestringrequired“JavaScript to execute.”
    • dryRunboolean“When true, write-tool calls are collected and reported as plannedWrites instead of being executed.”

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-11-17.

How well are its tools described?

Features #4 and #5

How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.

Descriptions

AI reading of each description

No AI reading was available for this server's tools (the two runs did not agree, or the listing was not reviewed).

Counted from the listing

Parameters with a description
57% of 176
Tools with a description
100% of 41
Typical description length
445 characters

The tool set

Counted from the listing

Tools
41
Size of the list
about 12,205 tokens for an agent to load (characters ÷ 4)
Naming
40 of 41 names use snake_case

AI reading: easy to mix up

No pair found.

The AI items cover 0 of 41 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none, comparing tools within groups of 40. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.

How do I add it to my client?

Config from the registry entry

From the remote endpoint (Streamable HTTP)

Add to CursorAn install link in the format Cursor documents, holding the Cursor config below.

Claude Desktop or claude.ai
Settings → Connectors → Add custom connector, then paste:
https://go.coremodels.io/mcp
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
  "mcpServers": {
    "coremodels": {
      "url": "https://go.coremodels.io/mcp"
    }
  }
}
VS Code · .vscode/mcp.json
{
  "servers": {
    "coremodels": {
      "type": "http",
      "url": "https://go.coremodels.io/mcp"
    }
  }
}
VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"coremodels","type":"http","url":"https://go.coremodels.io/mcp"}'
Claude Code
claude mcp add --transport http coremodels https://go.coremodels.io/mcp
Cline · cline_mcp_settings.json (Cline CLI: ~/.cline/data/settings/; in the editor: MCP Servers → Configure → Configure MCP Servers)
{
  "mcpServers": {
    "coremodels": {
      "type": "streamableHttp",
      "url": "https://go.coremodels.io/mcp",
      "disabled": false,
      "autoApprove": []
    }
  }
}
Gemini CLI · ~/.gemini/settings.json, or .gemini/settings.json in a project
{
  "mcpServers": {
    "coremodels": {
      "httpUrl": "https://go.coremodels.io/mcp"
    }
  }
}
OpenAI Codex · ~/.codex/config.toml, or .codex/config.toml in a trusted project
[mcp_servers.coremodels]
url = "https://go.coremodels.io/mcp"
Zed · Zed settings file (command: zed: open settings file)
{
  "context_servers": {
    "coremodels": {
      "url": "https://go.coremodels.io/mcp"
    }
  }
}
Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 --server-url https://go.coremodels.io/mcp --transport http
  • The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
  • Zed's docs we read on 2026-10-26 describe remote servers by URL and do not name the transport.
  • The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21; Cline, Gemini CLI, OpenAI Codex and Zed 2026-10-26). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

What do the published files and outside lists say?

Read as text · nothing run · no tool called

Package files

  • MCP SDK in the package files. Not read yet: added with the next daily run.
  • Build workflow. Not read yet: added with the next daily run.

Outside lists

  • CVE records (NVD). No CVE record in the NVD feeds we read links this server's repository. Source: read 2026-11-17. This product uses the NVD API but is not endorsed or certified by the NVD.
  • GitHub advisories. No GitHub advisory names this entry's listed package. Source: read 2026-11-17. GitHub Advisory Database, CC BY 4.0
  • Docker MCP catalogue. Not in the Docker MCP catalogue on 2026-11-17. Source: read 2026-11-17.
  • Cline marketplace. Not in the Cline marketplace on 2026-11-17. Source: read 2026-11-17.

Own host

  • security.txt. No security.txt at https://go.coremodels.io/.well-known/ (HTTP 404, 2026-11-17). No security.txt at https://www.coremodels.io/.well-known/ (HTTP 404, 2026-11-17). Source: go.coremodels.io/.well-known/security.txt · read 2026-11-17.
  • A2A agent card. No A2A agent card at https://go.coremodels.io/.well-known/ (HTTP 404, 2026-11-17). An A2A agent card is published at https://www.coremodels.io/.well-known/agent-card.json (name, skills, supportedInterfaces). Source: go.coremodels.io/.well-known/agent-card.json · read 2026-11-17.

Read as text from published files and outside lists. Nothing was installed or run, and no tool was called. A fact, not a rating. How each fact is read

Does the registry listing match what we found?

Feature #6

The registry checks an entry when it is published (each new version), and nothing re-checks it on a schedule. A difference below is about the listing, not a judgement of the publisher.

Registry saysWe foundResultSource · date
Remote endpoint go.coremodels.io/mcpSession openedmatchesour test · 2026-11-17
No credential declared as requiredOpened a session without any credentialmatchesour test · 2026-11-17

Choosing

Record checks

Public records · not a safety rating

1 of 2 record checks met · 7 do not apply

  • Not ranked by downloads: a remote server publishes no download figure
  • Not ranked by stars: no public GitHub repository
  • MetRegistry entry is active and says how to run itActive, with a package or a remote address.
  • Not metSource repository link opensThe registry entry gives no repository link.What changes this check: This check opens the repository link in the registry entry. GitHub's documentation describes changing a repository's visibility in its Settings, under Danger Zone, Change visibility. GitHub: setting repository visibility
  • Does not applyRepository is not archivedNo public GitHub repository to read.
  • Does not applyCode pushed to the repository in the 90 days before our checkNo public GitHub repository to read.
  • Does not applyRepository publishes a security policy (SECURITY.md)No public GitHub repository to read.
  • Does not applyPackage names its licence with a standard (SPDX) identifierRemote server: it ships no package.
  • Does not applyThe version the registry lists can be installed and is not withdrawnRemote server: it ships no package.
  • Does not applynpm package carries build provenance (attestation)Remote server: it ships no package.
  • Does not applyNo known critical or high advisory in the package or its dependenciesRemote server: it ships no package.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-11-17. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating, and the same rules apply to every server. How each check works · Leaderboards · How we stay neutral

Common questions about io.coremodels/coremodels

Answered from the data above

Who publishes io.coremodels/coremodels?

The registry ties the namespace io.coremodels to the domain coremodels.io; only its owner can publish under it. These are facts from the registry and GitHub, not a rating.

Does io.coremodels/coremodels need an API key or sign-in?

It opened a session without any credential on 2026-11-17. The registry entry declares no required credential; no declaration is not a guarantee.

Has io.coremodels/coremodels been security tested?

Partly. 3 of the 15 checks that apply to it were exercised. We connected and read what the server declares, but did not call its tools: ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so). This is our choice, not a block by the server. ProtocolProbe publishes no security verdict for a named server.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

What did we test, and what did we leave out?

18 checks · features #1, #2

Not probed (no operator permission)

We connected and read what the server declares, but did not call its tools: ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so). This is our choice, not a block by the server. No security score is given; a check we did not run is never counted as passed.

The 18 checks at a glanceour test · 2026-11-17
  1. Inventory: exercised
  2. Hidden instructions: exercised
  3. Real execution: not run · our policy
  4. Secret leak: not run · nothing to check it against
  5. Internal addresses: not run · our policy
  6. Unconfirmed changes: not run · our policy
  7. Bad input: not run · our policy
  8. Model requests: not run · nothing to check it against
  9. Sensitive questions: not run · nothing to check it against
  10. Folder boundary: not run · our policy
  11. Log leaks: not run · nothing to check it against
  12. Hidden content: not run · nothing to check it against
  13. Fake assistant turns: not applicable
  14. Token passthrough: not applicable
  15. Token audience: not applicable
  16. Sign-in redirect: not run · our policy
  17. Consent handling: not testable from outside
  18. Sign-in metadata: exercised

3 exercised12 not run (reason given)3 not applicable

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 3 of the 15 checks that apply to it were exercised. We do not publish security-check outcomes for named servers. These 18 checks are separate from the record checks at the top of this page, which read public records only.

Exercised · 3
  • 1Inventory
    tool-list
    Reads the declared tools, resources and prompts.exercised
  • 2Hidden instructions
    description-poisoning
    Looks for hidden instructions in tool descriptions.exercised
  • 18Sign-in metadata
    oauth-url-scheme
    Checks the published sign-in metadata for unsafe URLs.exercised
Not run, with the reason · 12
  • 3Real execution
    real-execution
    Calls a tool and checks what really happens.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy
  • 4Secret leak
    canary-leak
    Plants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 5Internal addresses
    ssrf
    Checks whether a tool can be steered to internal addresses.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy
  • 6Unconfirmed changes
    write-without-confirmation
    Checks whether tools that change data act without asking.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy
  • 7Bad input
    error-handling
    Sends bad input and watches how the server answers.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy
  • 8Model requests
    sampling
    Checks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 9Sensitive questions
    elicitation-sensitive-data
    Checks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 10Folder boundary
    root-boundary
    Checks whether the server reaches outside the folders it was given.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy
  • 11Log leaks
    logging-side-channel
    Checks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 12Hidden content
    audience-hiding
    Checks resources that hide content from the user.This check needs content the server returns, and nothing was read or called.not run · nothing to check it against
  • 16Sign-in redirect
    open-redirect
    Checks the sign-in redirect for abuse.Testing the sign-in redirect means sending probes to the operator's sign-in service, which we do not do.not run · our policy
  • 17Consent handling
    confused-deputy
    Checks consent handling when one service acts for another.Depends on the operator's own consent screen, which differs per server and cannot be tested from outside.not testable from outside
Does not apply to this server · 3
  • 13Fake assistant turns
    fake-assistant-turn
    Checks prompts that pose as the assistant's own words.The server exposes no prompts.not applicable
  • 14Token passthrough
    token-passthrough
    Checks whether the server forwards a user's token to other services.The server opened a session without sign-in, so there is no token flow to check.not applicable
  • 15Token audience
    token-audience-validation
    Checks whether tokens meant for another service are accepted.The server opened a session without sign-in, so there is no token flow to check.not applicable

Source: our own test, 2026-11-17, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.

What happened during the test?

Feature #8

The steps in order, as the test record holds them.

  1. 0 msStarted a read-only session with the server's remote endpoint
  2. 1,732 msConnected after 0 redirects. No credential was sent or needed.
  3. Read the inventory: 41 tools, 0 resources, 0 prompts.
  4. 6,109 msFinished: 3 checks exercised.

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified
pending: added at the next monthly refresh
listed 2026-11-17; not classified yet
Pricing modelAI-classified
pending: added at the next monthly refresh
the website is not read yet
Programming language
does not apply
no existing GitHub repository (server declares no repository link, so there is nothing to fetch)
Hosting type
registry · 2026-11-17
MCP capability
logging, prompts, resources, tools
our test · 2026-11-17
Transport
streamable HTTP
registry · 2026-11-17
Required credentials
none declared
registry · 2026-11-17 · no declaration is not a guarantee
Package registry
does not apply
remote-only server: no package is shipped, so there is no package registry
Freshness
0–30 days
registry updatedAt · 2026-11-17
Lifecycle status
registry · 2026-11-17
License class
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Integrity hash
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Signature / provenance
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Dependency advisories
does not apply
ships no package, so there are no dependencies to audit
Popularity
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Publisher signals
not stated
no readable GitHub owner to describe
Maintenance
does not apply
server declares no repository link, so there is nothing to fetch
Environment
the publisher's infrastructure
where it runs, from the hosting type · 2026-11-17

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “io.coremodels/coremodels: MCP server record.” Data checked 2026-11-17. https://protocolprobe.com/mcp/servers/io.coremodels/coremodels

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

ProtocolProbe: 1 of 2 record checks met

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/io.coremodels/coremodels)](https://protocolprobe.com/mcp/servers/io.coremodels/coremodels)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here, except for a server whose operator has claimed it and given permission (that server's page says so).

Write to hello@protocolprobe.com · corrections log · methodology