mcpbeat Sign in

Grideōs Facts MCP Server

by grideos Your server? Claim it
answering

Grideōs Facts is answering right now. Last checked 2 min ago. It exposes 7 tools.

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

Uptime history 15 days of history · worst day 99%
15 days agonow
100.0%
Uptime 24h
92 of 92 checks
7
Tools
read from the server
681 ms
Response time
average over 24h
open, no key
Access
streamable-http

What changed 1

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 20 October 2026. No other catalogue keeps this.

20 Oct a tool changed version

Grideōs Facts missed one check this week

Everything else answered, so this is steady rather than shaky. We check every 15 minutes, which is how a one-off gets told apart from the start of a pattern, and how you hear about the next one within the hour instead of from your users.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 2 min ago.

run in your terminal
claude mcp add facts --transport http https://grideos.com/mcp
Settings → Connectors → Add custom connector, then paste this address
https://grideos.com/mcp
~/.codex/config.toml
[mcp_servers.facts]
url = "https://grideos.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "facts": {
      "url": "https://grideos.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "facts": {
      "type": "http",
      "url": "https://grideos.com/mcp"
    }
  }
}

Available tools 7

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

claim
get_claim
Return one ledger entry by ID (for example GRD-007) with its evidence links, status, hash and the hash of the previous entry.
claims
list_claims
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.
company
get_company_profile
Who Grideōs is: definition, legal entity, location, contact, people, applications, method and trust layer, with links.
contact
contact_info
Email, office address and the URL of the brief form. This server cannot send messages.
dispatches
list_dispatches
Dated Grideōs updates with titles, summaries and URLs, newest first.
site
search_site
Keyword search across grideos.com answers, pages and dispatches. Returns short passages with their URLs for citation.
verify
verify_claim
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.

Endpoints

URLTransportStateLatencyChecked
https://grideos.com/mcp streamable-http answering 554 ms 2 min ago

Alternatives to Grideōs Facts

same job, measured the same way
FactStamp
by com-alpineai

Verify a company, figure or citation before you rely on it. Card or crypto; signed receipt.

18 tools answering
Attest
by dev-prathap

Decide by policy, gate behind a human, verify by read-back, record a hash-chained ledger.

local only
Verity MCP
by meloliva14

Fail-closed verify-before-you-act gate for AI agents. Signed receipts. Pay-per-call via x402.

105 installs/wk local only
Scrapecheck
by fieldmodellc

Verify before your agent acts on data it paid for. Signed verdicts, checkable offline, via x402.

3 tools answering
Invinoveritas
by babyblueviper

Second opinion before an irreversible agent action; signed proofs, free verify, public ledger.

10 tools answering
CrawlCheck
by emmanuelorta

Verification layer for the agentic web: a signed answer about any site before an agent acts.

25 tools answering
Verified Rec
by zaojiaoci

Hash-chained audit ledger for AI agent work — record, verify and replay what the agent did.

332 installs/wk local only
Vahtian
by heidihelena

Freeze a corpus, check it for drift, keep a hash-chained audit ledger. Local-first, stdlib-only.

81 installs/wk local only

Grideōs Facts — questions

Answers built from our own checks of this server.

What can Grideōs Facts do?
It exposes 7 tools, read directly from the server on our last check. Among them: contact_info, get_claim, get_company_profile, list_claims, list_dispatches, search_site and 1 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Grideōs Facts working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 681 ms. The bar chart above shows every period we have measured.
How do I connect Grideōs Facts?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Grideōs Facts need an API key?
No. Grideōs Facts completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 7 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Grideōs Facts?
It answers our handshake in 681 ms on average, which is faster than 14% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.