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.

Grideōs Facts

REMOTE · GRIDEOS.COM

Read-only facts about Grideōs from its signed, hash-chained ledger. Verify before you cite.

Available components

+3 this week 82 Trust /100

Last scanned (3 hours ago)

Scores higher than 85% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Search and Retrieval

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 Security80
Transport & Reachability100
Schema Quality & AI Usability79
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 432 tokens (~48/item across 9 items; 7 tools + 2 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management57
  • Stability observed for 17 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 9 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
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.

  • 4 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

  • 2 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

  • 31 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

  • 29 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

  • 27 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 24 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

  • 22 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

  • 20 Oct 26 +1
    • Stability: unverified → 0.03 ▲ functional
    • Server version: 7.10.0 → 7.10.5 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 5 Nov 2026 · Probed https://grideos.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=grideos.com CN=YE1,O=Let's Encrypt,C=US 11 Sept 2026 10 Dec 2026 ECDSA 256 ECDSA-SHA384 618e25ded04452f2a149f22b093bf89d05c
SANs: grideos.com, www.grideos.com
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of grideos.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
grideos.com. 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=31536000
x-content-type-options nosniff

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://grideos.com/mcp Verified 200
http (plaintext) http://grideos.com/mcp HTTPS enforced 301 https://grideos.com/mcp
MCP tools · 7 exposed · ~349 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
contact_info ~26

Email, office address and the URL of the brief form. This server cannot send messages.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_claim ~53

Return one ledger entry by ID (for example GRD-007) with its evidence links, status, hash and the hash of the previous entry.

NameTypeReqDescription
idstringyesClaim ID such as GRD-007

No output schema declared.

No examples provided.

get_company_profile ~37

Who Grideōs is: definition, legal entity, location, contact, people, applications, method and trust layer, with links.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_claims ~72

List the claims in the signed Grideōs facts ledger, optionally filtered by topic (identity, location, people, what, ironwall, programs, relationships, contact, machine-access, privacy, work). A superseded claim names the entry that replaced it.

NameTypeReqDescription
topicstring–Optional topic filter

No output schema declared.

No examples provided.

list_dispatches ~26

Dated Grideōs updates with titles, summaries and URLs, newest first.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

search_site ~60

Keyword search across grideos.com answers, pages and dispatches. Returns short passages with their URLs for citation.

NameTypeReqDescription
limitinteger–Maximum passages to return (default 5)
querystringyesWhat to look for, in plain words

No output schema declared.

No examples provided.

verify_claim ~75

Recompute a ledger entry's SHA-256 hash and chain link, and optionally compare a quoted claim text with the ledger text. Returns where to verify the Ed25519 signature independently.

NameTypeReqDescription
idstringyesClaim ID such as GRD-007
textstring–Optional claim text to compare with the ledger

No output schema declared.

No examples provided.

Install

How do I install the Grideōs Facts MCP server?

Grideōs Facts is a hosted endpoint at https://grideos.com/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 · grideos.com

# add to Claude Code
claude mcp add --transport http com-grideos-facts 'https://grideos.com/mcp'
Common questions

What is the Grideōs Facts MCP server?

Grideōs Facts is an MCP server listed in the public MCP registry as com.grideos/facts. Read-only facts about Grideōs from its signed, hash-chained ledger. Verify before you cite. This page covers its hosted endpoint (https://grideos.com/mcp).

Is the Grideōs Facts MCP server safe to use?

Grideōs Facts scores 82 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 Grideōs Facts MCP server expose?

Grideōs Facts exposes 7 tools: get_company_profile, search_site, list_claims, get_claim, verify_claim, and 2 more. Their descriptions and schemas cost roughly 349 tokens of context every time the server is loaded.

Does the Grideōs Facts MCP server require authentication?

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

Is the Grideōs Facts MCP server still maintained?

Grideōs Facts is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.