mcpbeat Sign in

Geolithic MCP Server

by howardzheni Your server? Claim it
answering

Geolithic is answering right now. Last checked 1 min ago. It exposes 15 tools.

One face of the Earth, yours alone for one term, proven on a public chain. A dollar. Readings free.

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

What changed 8

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

13 Sep a tool appeared witness
11 Sep 3 tools appeared meet, open_ground, stamp
11 Sep 3 tool descriptions were rewritten hold_ground, open_ground, tick
11 Sep a tool changed the parameters it asks for tick

Geolithic does not always answer

Over the last week it answered 97.5% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not 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 1 min ago.

run in your terminal
claude mcp add geolithic --transport http https://geolithicintelligence.com/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "geolithic": {
      "url": "https://geolithicintelligence.com/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.geolithic]
url = "https://geolithicintelligence.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "geolithic": {
      "url": "https://geolithicintelligence.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "geolithic": {
      "url": "https://geolithicintelligence.com/mcp"
    }
  }
}

Available tools 15

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

attest
attest
Attach your own sha256 to the face-term you hold: the claim and the attach in one. The record chains beside the world's state at that place and moment, witnessed; at most one per tick of your term; no party is named. A due lease is paid on this same call — pass the x402 `payment` (see claim) or pay the card checkout first.
bid
bid
Bid for the NEXT term of a face-stratum (address F{base}·{digits}, level 4–7 by digit count; amount in degrees ≥ the reserve, ≤ 720, at most 12 decimals). Pass your own salt (16–64 hex characters) and the house never holds it; leave it empty and the house makes one. Returns a receipt: KEEP THE SALT — it is the only credential. The gavel strikes at the receipt's `gavel` tick; then use claim().
catalog
catalog
What is for lease: the strata (L4–L7), their terms on the Earth ladder, the reserve prices in degrees, how to bid and claim, and the founding period's stated limits.
claim
claim
After the gavel: present your bid's exact fields and salt. The winner receives the lease (bearer paper); a loser learns only the clearing price. A winner is first answered 402 with two ways to pay the clearing price: `pay.checkout_url` (a card checkout, for a person) or `x402` (pay it yourself: sign a USDC transfer for x402.accepts[0], build the x402 PaymentPayload, base64 it, and call claim() again with it as `payment`). The lease issues at once.
ground
ground
Where a face address stands on the earth — at the founding and at a tick's chained frame, with the parcel's drift in km.
hold
hold_ground
Hold the ground you work on, in one call: quote the face under the place for the session's length, bid, wait for the gavel (at most four minutes), then claim and attach your sha256 — paying by x402 on the way if you pass `payment` signed for the quote's requirements. Alone on the face you pay the reserve (two cents for a tick or an hour over x402; a dollar by card); contested, the 402 names the clearing price and you pay and attest with attest(). With wait=False it bids and returns the receipt; call attest() after claim_after.
meet
meet
Did two stamps meet? Pass the two stamps' chain.digest values. If both stand on faces sharing a parent at the same tick, the answer names the room (the deepest face both stood in) and its level — the same place at the same time, by the chain's own arithmetic.
open
open_ground
Your address and the contents of your facet, and nothing else: present the lease's own fields (the receipt's addr, start, amount_degrees, salt) and get, for the newest chained tick of your term or the `tick` you name, the address you hold — where you exist, where your stamps land, where another agent finds you by a meeting — and per mapped field its numbers on this facet: the wind at 10 m and 850 hPa (the corners' readings, the charge and its change, the Merkle opening to the tick's chained root, verifiable with hashes alone), and more as fields are mapped (the measured magnet joins when its observatories' terms allow); plus the tick's record, the chained census inside the facet and the stamps on it. The whole tick is never served. `field` narrows to wind_10m, wind_850, magnet.
quote
quote_ground
The plan to hold the ground under a place for a session: the face at the level the duration asks (a tick, an hour, six hours, a day), the next term, the reserve, the dollars if you bid alone, the claim_url — and the exact x402 requirements to sign before the gavel. Pass your own salt (16–64 hex) and the house never holds it.
rent
rent_roll
The public rent roll: every strike (prices always, parties never) with each record's chain identity, plus current occupancy. The market data that prices the market.
stamp
stamp
Stamp the moment: chain your sha256 beside the Earth's tick — the clock's now, with the world's last witnessed state beside it — for two cents over x402, no account. Name where, if you like: an address, or lat and lon for the face under a place. Without `payment` the answer is the 402 with the requirements to sign; call again with `payment`. Two stamps on faces in one parent at one tick are a witnessed meeting: see meet().
tell
tell_the_house
Say what confused you, what you wanted, what you would pay for — a person reads every word and the door itself changes. `where` may name the tool or route you were on. Nothing is promised back but a reading.
tick
tick
The newest tick of the Earth, free. By default the hash and nothing else: the clock and the chain's links — the commitment a stamp binds to, trusted because the atlas shows what it fingerprints and a person can see that it is the world. With light=True, the light: the field arrays at the given mesh level (2–5), unsworn, with the poles' eyes and the measured magnet's zeros. The reading itself is chained and never served; the face you hold opens with open_ground().
verify
verify_lease
Verify a lease LOCALLY against the public chain. Fetches the named rent-roll record with its chain identity, then redoes the arithmetic here: sha256(canonical record) must equal the served digest and the lease's roll.digest; sha256(prev_chained + digest) must equal the served link; the link must match the ledger's own listing at /api/commitments; the row must carry this lease's term, serial, clearing price and winner envelope; and, given the salt, sha256(addr|level|start|amount|salt) must open winner_env — with the receipt's amount_degrees if the bid differed from the clearing price. Nothing is taken on the door's say-so: every hash is recomputed. What remains trusted is the chain's content itself, whose external witnesses are the anchors in server/anchors/.
witness
witness
Ask what the Earth was doing: the wind at a place at a moment as the chain committed it — the nest face's three corners at 10 m and 850 hPa with their coordinates, the Merkle opening to the tick's chained root, the chain identity of that state, and the outside anchor that covers it. `at` is an ISO hour or tick (UTC); without it, the newest chained tick. A moment not yet chained is refused, never substituted (ticks chain about three hours behind the clock). Two cents over x402: without `payment` the answer is the 402 with the requirements; call again with `payment`. One payment opens a face-tick for everyone after; `addr` (from an earlier answer) re-reads one. Settle on it: two of you stamp sealed claims into one triangle at one tick (stamp()), meet() proves you did so together, the witness resolves it after the target tick chains, and you settle between yourselves — the house holds nothing.

Endpoints

URLTransportStateLatencyChecked
https://geolithicintelligence.com/mcp streamable-http answering 386 ms 1 min ago

Alternatives to Geolithic

same job, measured the same way
Pixelgust
by pixelgust

Weather, climate, terrain, fire and flood risk data for any point or polygon on Earth. Free tier.

9 tools answering
D
The Wire
by workers-qualium-the-wire

A public meeting place for agents to exchange reviews and coordinate work.

11 tools answering
Ip Geolocation Mcp
by varvararatta

Unlock the power of IP geolocation with our tool! Whether you're a developer needing location data

3 tools answering
I
API Sorties MCP
by mabari2505

Search French events and things to do, built for AI agents — geo, city, date, category filters.

20 installs/wk local only
Glippy MCP
by jbobbink

GEO (Generative Engine Optimization) analysis: check any domain's AI-readiness for LLM search

63 installs/wk local only
Georgia Prisoners' Speak Public Data
by gps

Read-only public data on Georgia's prisons: population, facilities, deaths, contraband, statutes.

18 tools answering
Momentic
by momenticmarketing

Free SEO, GEO, and AEO audits: analyze any page or domain, AI-crawler access, agent readiness.

11 tools answering
Georgia Archives
by pipeworx-io

National Archives of Georgia MCP — the three catalogues the archives publish.

answering

Geolithic — questions

Answers built from our own checks of this server.

What can Geolithic do?
It exposes 15 tools, read directly from the server on our last check. Among them: attest, bid, catalog, claim, ground, hold_ground and 9 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 Geolithic working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 475 ms. The bar chart above shows every period we have measured.
How do I connect Geolithic?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Geolithic need an API key?
No. Geolithic completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 15 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Geolithic?
It answers our handshake in 475 ms on average, which is faster than 32% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.