Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

SUBSTRATE

REMOTE · SUBSTRATE.GARMOLABS.COM · 2 COMPONENTS · SCANNED SEP 29

Persistent AI entity framework with causal memory, emotional state, and identity.

Available components

remote · substrate.garmolabs.com 0 npm · substrate-mcp 31
−50 this week 0 Trust /100
Trust breakdown (7 categories)

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 Security11
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
  • Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
  • Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified

Unverified: 5 categories

Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

Install

How do I install the SUBSTRATE MCP server?

SUBSTRATE is a hosted endpoint at https://substrate.garmolabs.com/mcp-server/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 · substrate.garmolabs.com

# add to Claude Code
claude mcp add --transport http pkaldone-substrate 'https://substrate.garmolabs.com/mcp-server/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "pkaldone-substrate": {
      "url": "https://substrate.garmolabs.com/mcp-server/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "pkaldone-substrate": {
      "type": "http",
      "url": "https://substrate.garmolabs.com/mcp-server/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.pkaldone-substrate]
url = "https://substrate.garmolabs.com/mcp-server/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pkaldone-substrate": {
      "type": "remote",
      "url": "https://substrate.garmolabs.com/mcp-server/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add pkaldone-substrate --url 'https://substrate.garmolabs.com/mcp-server/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  pkaldone-substrate:
    url: "https://substrate.garmolabs.com/mcp-server/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "pkaldone-substrate": {
      "Transport": "http",
      "Url": "https://substrate.garmolabs.com/mcp-server/mcp"
    }
  }
}
# add to Vellum
assistant mcp add pkaldone-substrate -t streamable-http -u 'https://substrate.garmolabs.com/mcp-server/mcp'
// mcp.json
{
  "mcpServers": {
    "pkaldone-substrate": {
      "type": "http",
      "url": "https://substrate.garmolabs.com/mcp-server/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

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.

  • 18 Sept 26 −10

    The score moved with no change recorded against any check. We would rather say so than guess.

  • 17 Sept 26 −10

    The score moved with no change recorded against any check. We would rather say so than guess.

  • 16 Sept 26 −10

    The score moved with no change recorded against any check. We would rather say so than guess.

  • 15 Sept 26 −10

    The score moved with no change recorded against any check. We would rather say so than guess.

  • 14 Sept 26 −10

    The score moved with no change recorded against any check. We would rather say so than guess.

  • 12 Sept 26 0
    • Endpoint reachability: reachable → unreachable ▼ security
    • DNSSEC: fail → unverified ▼ security
    • Stability: pass → unverified ▼ security
    • TLS certificate: pass → unverified ▼ security
    • HSTS header: pass → unverified ▼ security
    • Transport: pass → fail ▼ security
    • Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
    • Capabilities: fail → unverified ▼ functional
    • First check of Schema quality: unverified functional
  • 11 Sept 26 0
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 10 Sept 26 0
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
Diagnostics

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 18 Sept 2026 · Probed https://substrate.garmolabs.com/mcp-server/mcp

TLS unreached

Background: What to check on a remote MCP endpoint →

DNSSEC inconclusive

Validation of substrate.garmolabs.com. — Inconclusive

Zone DS Keys Algorithms Outcome
substrate.garmolabs.com. Error no A/AAAA/CNAME RRset answered for the name
Authentication Inconclusive

We could not reach the endpoint well enough to judge its authorisation posture.

Result Inconclusive

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://substrate.garmolabs.com/mcp-server/mcp Unreachable
http (plaintext) http://substrate.garmolabs.com/mcp-server/mcp HTTPS enforced
MCP tools

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 →

No tool schema has been captured from this endpoint yet.

Common questions

What is the SUBSTRATE MCP server?

SUBSTRATE is an MCP server listed in the public MCP registry as io.github.PKaldone/substrate. Persistent AI entity framework with causal memory, emotional state, and identity. This page covers its hosted endpoint (https://substrate.garmolabs.com/mcp-server/mcp).

Is the SUBSTRATE MCP server safe to use?

SUBSTRATE scores 0 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.

Does the SUBSTRATE MCP server require authentication?

Its publisher declares no required credentials for SUBSTRATE. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

Is the SUBSTRATE MCP server still maintained?

SUBSTRATE has been unreachable for long enough that we treat it as dead, and its score is pinned to zero. We last reached this channel on 11 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.