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.

GuestGraph

REMOTE · MCP.GUESTGRAPH.IO · SCANNED SEP 28

GuestGraph: One guest, not five strangers

67 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 Security63
Transport & Reachability100
Schema Quality & AI Usability72
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 2159 tokens (~154/item across 14 items; 14 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
  • Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage88
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 56% of tool parameters carry a description.Partial
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 14 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 15 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the GuestGraph MCP server?

GuestGraph is a hosted endpoint at https://mcp.guestgraph.io/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 · mcp.guestgraph.io

# add to Claude Code
claude mcp add --transport http io-guestgraph-mental-model 'https://mcp.guestgraph.io/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "io-guestgraph-mental-model": {
      "url": "https://mcp.guestgraph.io/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "io-guestgraph-mental-model": {
      "type": "http",
      "url": "https://mcp.guestgraph.io/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.io-guestgraph-mental-model]
url = "https://mcp.guestgraph.io/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-guestgraph-mental-model": {
      "type": "remote",
      "url": "https://mcp.guestgraph.io/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add io-guestgraph-mental-model --url 'https://mcp.guestgraph.io/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  io-guestgraph-mental-model:
    url: "https://mcp.guestgraph.io/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "io-guestgraph-mental-model": {
      "Transport": "http",
      "Url": "https://mcp.guestgraph.io/mcp"
    }
  }
}
# add to Vellum
assistant mcp add io-guestgraph-mental-model -t streamable-http -u 'https://mcp.guestgraph.io/mcp'
// mcp.json
{
  "mcpServers": {
    "io-guestgraph-mental-model": {
      "type": "http",
      "url": "https://mcp.guestgraph.io/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.

  • 28 Sept 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 Sept 26 +1
    • Server version: 0.30.0 → 0.31.0 functional
    • New tool “diagram” functional
  • 25 Sept 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 24 Sept 26 65

    First indexed and scored.

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 28 Sept 2026 · Probed https://mcp.guestgraph.io/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mcp.guestgraph.io CN=WR3,O=Google Trust Services,C=US 24 Sept 2026 23 Dec 2026 RSA 2048 SHA256-RSA a38a8f9960c095490ad74df11585e2c1
SANs: mcp.guestgraph.io
CN=WR3,O=Google Trust Services,C=US (CA) CN=GTS Root R1,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 RSA 2048 SHA256-RSA 7ff005a91568d63abc22861684aa4b5a
CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 19 Jun 2020 28 Jan 2028 RSA 4096 SHA256-RSA 77bd0d6cdb36f91aea210fc4f058d30d
CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 1 Sept 1998 28 Jan 2028 RSA 2048 SHA1-RSA 40000000001154b5ac394

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.guestgraph.io. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
io. present 57355 8 Verified
guestgraph.io. 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=31556926

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.guestgraph.io/mcp Verified 200
http (plaintext) http://mcp.guestgraph.io/mcp HTTPS enforced 301 https://mcp.guestgraph.io/mcp
MCP tools · 14 exposed · ~1,819 tokens

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 →

Tool Tokens
describe_errors ~98

What a refused call looks like. A tool's output schema covers its answers only, so use this once, to branch on refusals or validate them. No input. Returns `errors`, every `code` with `when` it is raised and the JSON Schema of its `details`, and `schema`, the JSON Schema of a whole refusal: `error` with `code`, `message`, `rule`, `details`, beside `model`.

Input schema present but exposes no named parameters.

NameTypeReqDescription
errorsarrayyes–
modelobjectyes–
schemaobjectyes–

No examples provided.

describe_relations ~127

What the schemas declare between types: references with form and cardinality, ownership, enums, joins, list kinds. Use for a diagram or audit; for one type's full schema use describe_schema. Optional `type` narrows every list, `direction` (declares, declared-to, both; needs `type`) one side of relations, `via` relations and enums. Returns those lists, with `forms` and `reading` explaining every term. Not paged.

NameTypeReqDescription
directionstring––
typestring––
viastring––
NameTypeReqDescription
enumsarrayyes–
formsobjectyes–
joinsarrayyes–
listsarrayyes–
modelobjectyes–
ownershiparrayyes–
readingobjectyes–
relationsarrayyes–

No examples provided.

describe_rule ~82

One rule as written. Input: `rule`, a number from list_rules such as R9, in either case. Returns `rule`, `title`, `part`, `text` and the file's `url`. An unknown number is refused with the known ones listed.

NameTypeReqDescription
rulestringyesA rule's number from list_rules, such as R9
NameTypeReqDescription
modelobjectyes–
partstring|nullyes–
rulestringyes–
textstringyes–
titlestringyes–
urlstring|nullyes–

No examples provided.

describe_schema ~98

One type's schema: its sections as written and its declared relations as data. Use to learn what an entity of the type may hold; for the whole vocabulary use describe_relations. Input: `type`. Returns `url`, the schema's own file, `sections`, and `relations`: owner, owns, references both ways, enums, joins and lists.

NameTypeReqDescription
typestringyesA type name from list_types, such as skill
NameTypeReqDescription
modelobjectyes–
namestringyes–
relationsobjectyes–
sectionsarrayyes–
taglinestringyes–
typestringyes–
urlstring|nullyes–

No examples provided.

diagram ~173

A picture of the model as Mermaid, from its edges or its schemas. Use to show connections; for edges as data use list_references. Input: `shape`; `id`, `domain` or `type` narrow it. Returns `mermaid`, `nodes`, `links`, `title`, `edges`, `omitted`, schema's `everyType`. A process draws each gate's failure dashed, to a phase or one Stop node, outside `nodes`. At most 50 nodes.

NameTypeReqDescription
domainstring–A domain's id, to draw its concepts
idstring–The process to draw, or the entity at the middle of a neighborhood
shapestringyes–
typestring–A type, to draw its schema and the types it is declared with
NameTypeReqDescription
edgesintegeryes–
everyTypearray––
linksarrayyes–
mermaidstringyes–
modelobjectyes–
nodesarrayyes–
omittedintegeryes–
shapestringyes–
titlestring|nullyes–

No examples provided.

fetch ~87

One entity's page as written. Use to quote or display the source; for structured fields and references use get_entity. Input: `id`, from search, list_entities or any reference. Returns `id`, `title`, `type`, `url` and `text`, the Markdown source. Takes no name: search with match "name" finds the id.

NameTypeReqDescription
idstringyes–
NameTypeReqDescription
idstringyes–
modelobjectyes–
textstringyes–
titlestringyes–
typestringyes–
urlstring|nullyes–

No examples provided.

find_evidence ~170

Every edge into one skill, grouped by the type of the page that drew it. Use to check a claimed skill against its evidence. Input: `skill`, an id or canonical name; optional `limit`, `cursor`. Returns `skill`, `evidence` and `page`; a profile's claim arrives via Skills.Skill with its level, an evidence row via Evidence.Skill. Attributes are verbatim.

NameTypeReqDescription
cursorstring–`page.nextCursor` from the previous answer, sent with the same arguments; omit it for the first page.
limitinteger–Entries per page: 50 by default, clamped to 1–200, so 0 returns one entry and 1000 returns 200.
skillstringyesThe skill's id or canonical name
NameTypeReqDescription
evidenceobjectyes–
modelobjectyes–
pageobjectyes–
skillobjectyes–

No examples provided.

get_entity ~133

One entity as structured data: fields, sections, tables and its references both ways. Use to reason over an entity; for its page as written use fetch. Input: `id`, or `type` and `name`; an ambiguous name is refused with candidate ids. Returns `entity`. Each reference list holds at most 50 edges; `referenceCounts` gives the totals and list_references the rest.

NameTypeReqDescription
idstring–The entity's id, as any answer gives it
namestring–The canonical name, the entity's H1; needs type
typestring––
NameTypeReqDescription
entityobjectyes–
modelobjectyes–

No examples provided.

list_checks ~84

The checks the model's own gate runs, from the checker release this server was built with. Use to see which rules a script enforces and which are left to a reader. No input. Returns `checks`, each with `name`, `rule` and that rule's `title`, and `ranBy`. A list and no verdict: this server runs none of them.

Input schema present but exposes no named parameters.

NameTypeReqDescription
checksarrayyes–
modelobjectyes–
ranBystringyes–

No examples provided.

list_entities ~196

The entities of one type, by id. Use to browse a type; to find an entity by words or by name use search. Input: `type`, optional `owner` (an id) to keep one owner's entities, `limit` (default 50, at most 200) and `cursor`. Returns `entities` with `id`, `type`, `name`, `tagline`, `owner`, and `page`; follow `page.nextCursor` while `page.hasMore`.

NameTypeReqDescription
cursorstring–`page.nextCursor` from the previous answer, sent with the same arguments; omit it for the first page.
limitinteger–Entries per page: 50 by default, clamped to 1–200, so 0 returns one entry and 1000 returns 200.
ownerstring–An owner's id, to keep its entities
typestringyes–
NameTypeReqDescription
entitiesarrayyes–
modelobjectyes–
pageobjectyes–
typestringyes–

No examples provided.

list_references ~202

The model's edges, filtered and paged. Use to inspect one entity's relations or one kind of reference without taking whole entities. Optional `entity` (an id), `direction` (out, in, both; needs `entity`), `via`, `type` (the far end's type, or either end's without `entity`), `limit`, `cursor`. Returns `edges`, each `from`, `via`, `to`, `attrs`, and `page`.

NameTypeReqDescription
cursorstring–`page.nextCursor` from the previous answer, sent with the same arguments; omit it for the first page.
directionstring––
entitystring––
limitinteger–Entries per page: 50 by default, clamped to 1–200, so 0 returns one entry and 1000 returns 200.
typestring––
viastring––
NameTypeReqDescription
edgesarrayyes–
modelobjectyes–
pageobjectyes–

No examples provided.

list_rules ~83

The rules the model is held to, from the CONVENTIONS.md its core vendors. Use to resolve a rule number that a schema or a refusal cites, such as R9. No input. Returns `tagline`, the file's `url`, and `rules`, each with `rule`, `title` and `part`; describe_rule gives one rule's text.

Input schema present but exposes no named parameters.

NameTypeReqDescription
modelobjectyes–
rulesarrayyes–
taglinestringyes–
urlstring|nullyes–

No examples provided.

list_types ~71

Every type the model's schemas declare. Use first, to learn which types exist before listing or describing one. No input. Returns `types`, each with `type`, `name`, `tagline`, `owner` (the type it nests under, or null) and `count`, the entities it holds.

Input schema present but exposes no named parameters.

NameTypeReqDescription
modelobjectyes–
typesarrayyes–

No examples provided.

search ~215

Find entities by words, substring or exact name. `match: "words"` needs every query word's stem in name, tagline, fields, sections or cells; `"text"` (default) is a case-insensitive substring over the same; `"name"` the exact canonical name. Optional `type`, `owner`, `limit`, `cursor`. Returns `results` with `id`, `title`, `type`, `matched`, `words` in words mode, and `page`: name matches first, then a listing.

NameTypeReqDescription
cursorstring–`page.nextCursor` from the previous answer, sent with the same arguments; omit it for the first page.
limitinteger–Entries per page: 50 by default, clamped to 1–200, so 0 returns one entry and 1000 returns 200.
matchstring––
ownerstring–An owner's id, to keep its entities
querystringyes–
typestring––
NameTypeReqDescription
matchstringyes–
modelobjectyes–
pageobjectyes–
querystringyes–
resultsarrayyes–
wordsarray––

No examples provided.

Common questions

What is the GuestGraph MCP server?

GuestGraph is an MCP server listed in the public MCP registry as io.guestgraph/mental-model. GuestGraph: One guest, not five strangers. This page covers its hosted endpoint (https://mcp.guestgraph.io/mcp).

Is the GuestGraph MCP server safe to use?

GuestGraph scores 67 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 GuestGraph MCP server expose?

GuestGraph exposes 14 tools: list_types, describe_schema, describe_relations, list_rules, describe_rule, and 9 more. Their descriptions and schemas cost roughly 1,819 tokens of context every time the server is loaded.

Does the GuestGraph MCP server require authentication?

No. We connected to GuestGraph without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the GuestGraph MCP server still maintained?

GuestGraph is still listed as active in the MCP registry. We last reached this channel on 28 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.