io.github.joegra2003/metamodel
REMOTE · WWW.METAMODEL.APP · 2 COMPONENTS · SCANNED SEP 21
AI-callable calculators and engineering models with real formulas. No hallucinated math.
Available components
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. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 1 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability82
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 433 tokens (~108/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the io.github.joegra2003/metamodel MCP server?
io.github.joegra2003/metamodel is a hosted endpoint at https://www.metamodel.app/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · www.metamodel.app
claude mcp add --transport http joegra2003-metamodel 'https://www.metamodel.app/api/mcp'
{
"mcpServers": {
"joegra2003-metamodel": {
"url": "https://www.metamodel.app/api/mcp"
}
}
} {
"servers": {
"joegra2003-metamodel": {
"type": "http",
"url": "https://www.metamodel.app/api/mcp"
}
}
} [mcp_servers.joegra2003-metamodel] url = "https://www.metamodel.app/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"joegra2003-metamodel": {
"type": "remote",
"url": "https://www.metamodel.app/api/mcp",
"enabled": true
}
}
} openclaw mcp add joegra2003-metamodel --url 'https://www.metamodel.app/api/mcp' --transport streamable-http
mcp_servers:
joegra2003-metamodel:
url: "https://www.metamodel.app/api/mcp" {
"McpServers": {
"joegra2003-metamodel": {
"Transport": "http",
"Url": "https://www.metamodel.app/api/mcp"
}
}
} assistant mcp add joegra2003-metamodel -t streamable-http -u 'https://www.metamodel.app/api/mcp'
{
"mcpServers": {
"joegra2003-metamodel": {
"type": "http",
"url": "https://www.metamodel.app/api/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 30 Aug 26 −7
- Authorization: partial → unverified ▼ security
- Schema quality: 330 → 433 ▼ functional
- New tool “metamodel_export_kn” functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 +1
- Stability: 0.97 → pass security
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 0
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Sept 2026 · Probed https://www.metamodel.app/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=www.metamodel.app | CN=YR2,O=Let's Encrypt,C=US | 28 Aug 2026 | 26 Nov 2026 | RSA 2048 | SHA256-RSA | 5e7698e7bd36250d2f897438f2ff4db22eb |
| SANs: www.metamodel.app | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of www.metamodel.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| metamodel.app. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.metamodel.app/api/mcp | Verified | 200 | |
| http (plaintext) | http://www.metamodel.app/api/mcp | HTTPS enforced | 308 | https://www.metamodel.app/api/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
metamodel_compute ~145
Run a computation on a MetaModel project. Send input values and get computed outputs from all models. Inputs are auto-routed to the correct model by property name. Models marked "presentation": true in results are display scaffolding, not engineering outputs. Use metamodel_get_schema first to discover available inputs and outputs.
| Name | Type | Req | Description |
|---|---|---|---|
| inputs | object | – | Input values as key-value pairs (e.g., {"width": 12}). Auto-routed to the correct model. Omitted inputs use defaults. |
| model | string | – | Target a specific model by name. When omitted, returns outputs from ALL models (recommended). |
| token | string | yes | The publish token of the project |
No output schema declared.
No examples provided.
metamodel_export_kn ~103
Export a published MetaModel project as KN notation — a human-readable text spelling of the model: nested Component blocks, "Name: value" literals, "Name: expression" formulas, dotted cross-references. Deliberately lossy (rules, indicators, validations, table data and views are omitted). Useful for reading or diffing the engineering knowledge behind a project.
| Name | Type | Req | Description |
|---|---|---|---|
| token | string | yes | The publish token of the project (from metamodel_list_projects) |
No output schema declared.
No examples provided.
metamodel_get_schema ~91
Get the input/output schema for a published MetaModel project. Returns model names, input parameters (with types, defaults, validation), and output fields. Models marked "presentation": true are display scaffolding (3D scenes etc.) — skip them for engineering analysis. Use a token from metamodel_list_projects.
| Name | Type | Req | Description |
|---|---|---|---|
| token | string | yes | The publish token of the project (from metamodel_list_projects) |
No output schema declared.
No examples provided.
metamodel_list_projects ~35
Browse available MetaModel calculators and engineering models. Returns project names, descriptions, tokens, and model names for each published project.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the io.github.joegra2003/metamodel MCP server?
io.github.joegra2003/metamodel is an MCP server listed in the public MCP registry as io.github.joegra2003/metamodel. AI-callable calculators and engineering models with real formulas. No hallucinated math. This page covers its hosted endpoint (https://www.metamodel.app/api/mcp).
Is the io.github.joegra2003/metamodel MCP server safe to use?
io.github.joegra2003/metamodel scores 80 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.joegra2003/metamodel MCP server expose?
io.github.joegra2003/metamodel exposes 4 tools: metamodel_list_projects, metamodel_get_schema, metamodel_export_kn, metamodel_compute. Their descriptions and schemas cost roughly 374 tokens of context every time the server is loaded.
Does the io.github.joegra2003/metamodel MCP server require authentication?
No. We connected to io.github.joegra2003/metamodel without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.joegra2003/metamodel MCP server still maintained?
io.github.joegra2003/metamodel is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.