Geolithic MCP server
io.github.HowardZheni/geolithicHowardZhenistreamable-httpv0.1.0Scanned
One face of the Earth, yours alone for one term, proven on a public chain. A dollar. Readings free.
15 tools: 15 change things.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- 1 finding
Tools listed without sign-in. Remote posture
With Anlyon
15 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Geolithic MCP server can do
The Geolithic MCP server is published by the GitHub account HowardZheni. It has 15 tools. It can create or change data (15 tools: catalog, tick, open_ground, rent_roll and 11 more), but cannot delete data. None of its tools only reads.
None of its tools reads private data, brings in text other people write, or sends data out.
The fixed checks matched 1 finding (credentials-mention). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 16, 2026, version 0.1.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
15 tools
Changes things 15Claude Code: ask
attestAttach your own sha256 to the face-term you hold: the claim and the attach in one.No findings
Why it is in this group
- The description's first verb is "attach": a word for a change.
Description, as the server wrote it 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.
bidBid 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).1 finding
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Findings
- Info
The description mentions "credential".
What this check looks forMatched text
description: "...receipt: KEEP THE SALT — it is the only credential. The gavel strikes at the receipt's `ga..."
Description, as the server wrote it 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().
catalogWhat 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.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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.
claimAfter the gavel: present your bid's exact fields and salt.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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.
groundWhere a face address stands on the earth — at the founding and at a tick's chained frame, with the parcel's drift in km.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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_groundHold 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…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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.
meetDid two stamps meet?No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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_groundYour 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…No findings
Why it is in this group
- The name "open_ground" says "open": a word for a change.
Description, as the server wrote it 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_groundThe 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…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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_rollThe public rent roll: every strike (prices always, parties never) with each record's chain identity, plus current occupancy.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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.
stampStamp 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.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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_the_houseSay what confused you, what you wanted, what you would pay for — a person reads every word and the door itself changes.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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.
tickThe newest tick of the Earth, free.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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_leaseVerify a lease LOCALLY against the public chain.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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/.
witnessAsk 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 openi…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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.
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:58 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 15
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 15 tools that change things (15 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://geolithicintelligence.com/mcp: tools/list returned 15 tools to an anonymous client, including catalog (write), tick (write), open_ground (write), rent_roll (write), ground (write) and 10 more
Findings
Matches of fixed checks, with the text they matched.
- Infobid
The description mentions "credential".
What this check looks forMatched text
description: "...receipt: KEEP THE SALT — it is the only credential. The gavel strikes at the receipt's `ga..."
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 0.1.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http geolithic https://geolithicintelligence.com/mcpclaude mcp add --transport http geolithic https://geolithicintelligence.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [],
"ask": [
"mcp__geolithic__catalog",
"mcp__geolithic__tick",
"mcp__geolithic__open_ground",
"mcp__geolithic__rent_roll",
"mcp__geolithic__ground",
"mcp__geolithic__bid",
"mcp__geolithic__claim",
"mcp__geolithic__attest",
"mcp__geolithic__stamp",
"mcp__geolithic__meet",
"mcp__geolithic__witness",
"mcp__geolithic__quote_ground",
"mcp__geolithic__hold_ground",
"mcp__geolithic__tell_the_house",
"mcp__geolithic__verify_lease"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as geolithic. Review it before you use it.
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.HowardZheni/geolithic/verify?hash=dd46ce2d5d7856f59b75897f80a4f6745c4523f15053be3f810e53b0f13577c3" | jq -e '.changed == false'Pinned hash dd46ce2d5d78, from Nov 16, 2026, 17:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.HowardZheni/geolithic/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.HowardZheni/geolithic)Source: MCP Registry. Synced Oct 21, 2026, 18:16 UTC.
Geolithic MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Geolithic MCP server safe?
- No scan can promise that. What its definitions show: 15 tools, 15 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Geolithic MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Geolithic MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Geolithic MCP server have?
- 15 tools: 15 write. catalog, tick, open_ground, rent_roll, ground, bid, claim, attest and 7 more.
Does the Geolithic MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Geolithic MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Geolithic MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 16, 2026.