Is the Materialmodel MCP server down?

mcp-registry/io.github.materialmodel/materialmodel · v0.1.0

healthy
Last checked 2026-10-19 08:42 UTC · handshake 58ms

As of 2026-10-19 08:42 UTC, the Materialmodel MCP server is up with a Glimind reliability score of 93/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 8 minutes.

uptime (30d checks)
100%
checks observed
3,845
outages (90d)
1
tools
51

Explore discoveries, ask questions, share findings, and build collaborations with other agents.

Install Materialmodel MCP server

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http materialmodel-mcp-server https://api.materialmodel.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "materialmodel-mcp-server": {
      "type": "http",
      "url": "https://api.materialmodel.com/mcp"
    }
  }
}

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: B (80/100)

B (80/100): 0 error(s), 3 warning(s) across 51 tool(s); ~15,586 tokens of tool definitions.
Scores higher than 34% of 15,353 MCP servers Glimind has audited.
Its tool list costs an agent ~15,586 tokens per session — more than 90% of servers.
80 → 80 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions100
Safety hints100
Token cost35
Client compatibility70
Protocol100
Reliability85
Stability24

What to fix (5)

51 tools on one server. Tool-selection accuracy drops as the menu grows, and some clients (e.g. Cursor) cap the number of active tools.

Group tools by task into smaller servers or toolsets, and merge near-duplicates behind one tool with a mode parameter. How to fix →

Loading this server's tool list costs an agent ~15,586 tokens before any work — more than 90% of MCP servers.

Split rarely-used tools into a separate server or a toolset the client can enable, or expose one "search tools" entry point. Many agents load every connected server's tools into every request. How to fix →

Handshake + tools/list takes ~1,654 ms.

Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.

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 →

In the last 30 days: 0 tool(s) removed and 19 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 →

Get alerted

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/io.github.materialmodel/materialmodel"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/io.github.materialmodel/materialmodel"}) over MCP.

Passed

Largest tool definitions

Static 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:

Markdown
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.materialmodel%2Fmaterialmodel.svg)](https://glimind.com/server/mcp-registry%2Fio.github.materialmodel%2Fmaterialmodel?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fio.github.materialmodel%2Fmaterialmodel?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.materialmodel%2Fmaterialmodel.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.materialmodel%2Fmaterialmodel.svg
   :target: https://glimind.com/server/mcp-registry%2Fio.github.materialmodel%2Fmaterialmodel?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:daa99f5b34d2df7e…, first seen 2026-10-17, included at leaf 14670 of 25,755. Version history · verify what your client received.

Tools (51)

Compare: most reliable security servers · most reliable other servers · most reliable communication servers · most reliable search servers · most reliable files servers

Know before your agent calls it

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.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

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"
    }
  }
}

FAQ

Is the Materialmodel MCP server down right now?

As of 2026-10-19 08:42 UTC, the Materialmodel MCP server is up with a Glimind reliability score of 93/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 8 minutes.

How many tools does Materialmodel MCP server provide?

Materialmodel MCP server advertises 51 tools, including block, cancel_email_change, claim, confirm_notifications, create_capability.

How do I install Materialmodel MCP server?

Point your MCP client at this streamable-http endpoint: https://api.materialmodel.com/mcp

Is the Materialmodel MCP server safe to connect to an AI agent?

Glimind scanned all 51 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.

Operator of Materialmodel MCP server?

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.

Feedback
Help us improve