mcp-registry/com.materialscodegraph/mcg · v0.1.0
As of 2026-10-22 02:37 UTC, the Materialscodegraph Mcg MCP server is up with a Glimind reliability score of 96/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Materials simulations for AI agents over MCP: binding token quote before every run, record after it.
Claude Code
claude mcp add --transport http materialscodegraph-mcg-mcp-server https://api.materialscodegraph.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"materialscodegraph-mcg-mcp-server": {
"type": "http",
"url": "https://api.materialscodegraph.com/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
1 tool definition(s) exceed ~1,200 tokens each (largest: mcg_quote, ~1,204).
Move long reference material out of descriptions (link a doc or expose a resource), drop repeated examples, and collapse large enums. Trimming these to ~600 tokens saves ~604 tokens every session. How to fix →
1 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.
Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
3 of 12 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
In the last 30 days: 0 tool(s) removed and 2 schema change(s).
Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.materialscodegraph%2Fmcg/fixes
{
"name": "mcg_run",
"description": "Launch the quoted simulation. SPENDS TOKENS: provisions hardware and bills the account. Requires the quote_id and quote_hash from mcg_quote (a stale hash or an expired quote REJECTS: re-quote and retry) and a client-generated idempotency_key (replaying it returns the existing run instead of launching twice). Optional max_tokens is a hard ceiling: a quote above it REJECTS the launch, never clamps. Returns run_id.",
"inputSchema": {
"type": "object",
"required": [
"quote_id",
"quote_hash",
"idempotency_key"
],
"properties": {
"quote_id": {
"type": "string",
"description": "The quote_id returned by mcg_quote."
},
"max_tokens": {
"type": "integer",
"minimum": 1,
"description": "Hard token ceiling: the launch is REJECTED if the quote exceeds it."
},
"quote_hash": {
"type": "string",
"description": "The quote_hash mcg_quote returned: proves the launch prices the exact quote the client saw."
},
"idempotency_key": {
"type": "string",
"description": "Client-generated key; retrying a launch with the same key must not double-charge."
}
}
},
"annotations": {
"idempotentHint": false,
"readOnlyHint": false,
"destructiveHint": false
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/com.materialscodegraph/mcg"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/com.materialscodegraph/mcg"}) over MCP.
mcg_quote ~1,204 tokensmcg_stage ~503 tokensmcg_run ~288 tokensmcg_get_run ~188 tokensmcg_catalog ~164 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fcom.materialscodegraph%2Fmcg?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fcom.materialscodegraph%2Fmcg?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.materialscodegraph%2Fmcg.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.materialscodegraph%2Fmcg.svg :target: https://glimind.com/server/mcp-registry%2Fcom.materialscodegraph%2Fmcg?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:acf432524f0d163b…, first seen 2026-10-18, included at leaf 21162 of 43,023. Version history · verify what your client received.
Compare: most reliable data servers · most reliable other servers · most reliable database servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-22 02:37 UTC, the Materialscodegraph Mcg MCP server is up with a Glimind reliability score of 96/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Materialscodegraph Mcg MCP server advertises 12 tools, including mcg_cancel_run, mcg_catalog, mcg_clusters, mcg_fetch_artifacts, mcg_get_artifact.
Point your MCP client at this streamable-http endpoint: https://api.materialscodegraph.com/mcp
Glimind scanned all 12 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.