Geolithic
REMOTE · GEOLITHICINTELLIGENCE.COM · SCANNED SEP 20
One face of the Earth, yours alone for one term, proven on a public chain. A dollar. Readings free.
Available components
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
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 15 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability51
- AI-judged instruction clarity (fair).Partial
- Context-footprint check failed: tool/resource definitions use about 2166 tokens (~144/item across 15 items; 15 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 Management37
- Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 15 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 16 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
How do I install the Geolithic MCP server?
Geolithic is a hosted endpoint at https://geolithicintelligence.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 · geolithicintelligence.com
claude mcp add --transport http howardzheni-geolithic 'https://geolithicintelligence.com/mcp'
{
"mcpServers": {
"howardzheni-geolithic": {
"url": "https://geolithicintelligence.com/mcp"
}
}
} {
"servers": {
"howardzheni-geolithic": {
"type": "http",
"url": "https://geolithicintelligence.com/mcp"
}
}
} [mcp_servers.howardzheni-geolithic] url = "https://geolithicintelligence.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"howardzheni-geolithic": {
"type": "remote",
"url": "https://geolithicintelligence.com/mcp",
"enabled": true
}
}
} openclaw mcp add howardzheni-geolithic --url 'https://geolithicintelligence.com/mcp' --transport streamable-http
mcp_servers:
howardzheni-geolithic:
url: "https://geolithicintelligence.com/mcp" {
"McpServers": {
"howardzheni-geolithic": {
"Transport": "http",
"Url": "https://geolithicintelligence.com/mcp"
}
}
} assistant mcp add howardzheni-geolithic -t streamable-http -u 'https://geolithicintelligence.com/mcp'
{
"mcpServers": {
"howardzheni-geolithic": {
"type": "http",
"url": "https://geolithicintelligence.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 20 Sept 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 165 → 144 ▲ functional
- 19 Sept 26 +1
- Injection markers: unverified → pass ▲ security
- TLS certificate: unverified → pass ▲ security
- HSTS header: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 15 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- Endpoint reachability: unreachable → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Stability: unverified → 0.33 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- 18 Sept 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- Stability: 0.27 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- HSTS header: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 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.
- 13 Sept 26 0
- Schema quality: 2226 → 2488 ▼ functional
- New tool “witness” functional
- 11 Sept 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “hold_ground” rewrote its description, which is the text the model reads security
- Tool “tick” rewrote its description, which is the text the model reads security
- Schema quality: 138 → 159 ▼ functional
- Schema quality: good → fair functional
- New tool “meet” functional
- New tool “open_ground” functional
- New tool “stamp” functional
- “tick” added an optional parameter “light” cosmetic
- 10 Sept 26 −2
- The server rewrote its instructions, which are the text every model session reads security
- Tool “claim” rewrote its description, which is the text the model reads security
- Schema quality: 121 → 138 ▼ functional
- Stability: unverified → 0.03 ▲ functional
- New tool “attest” functional
- New tool “hold_ground” functional
- New tool “quote_ground” functional
- “claim” added an optional parameter “payment” cosmetic
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 20 Sept 2026 · Probed https://geolithicintelligence.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=geolithicintelligence.com | CN=YE2,O=Let's Encrypt,C=US | 8 Sept 2026 | 7 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 6db350d0dc44411ac160c05354b09d288a6 |
| SANs: geolithicintelligence.com | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| 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 geolithicintelligence.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| geolithicintelligence.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 |
| referrer-policy | no-referrer |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://geolithicintelligence.com/mcp | Verified | 200 | |
| http (plaintext) | http://geolithicintelligence.com/mcp | HTTPS enforced | 308 | https://geolithicintelligence.com/mcp |
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 →
attest ~139
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.
| Name | Type | Req | Description |
|---|---|---|---|
| addr | string | yes | – |
| amount_degrees | string | yes | – |
| hash | string | yes | – |
| label | string | – | – |
| payment | string | – | – |
| salt | string | yes | – |
| start | string | yes | – |
No output schema declared.
No examples provided.
bid ~138
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().
| Name | Type | Req | Description |
|---|---|---|---|
| addr | string | yes | – |
| amount_degrees | string | yes | – |
| salt | string | – | – |
No output schema declared.
No examples provided.
catalog ~52
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
claim ~164
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.
| Name | Type | Req | Description |
|---|---|---|---|
| addr | string | yes | – |
| amount_degrees | string | yes | – |
| payment | string | – | – |
| salt | string | yes | – |
| start | string | yes | – |
No output schema declared.
No examples provided.
ground ~51
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.
| Name | Type | Req | Description |
|---|---|---|---|
| addr | string | yes | – |
| tick_iso | string | – | – |
No output schema declared.
No examples provided.
hold_ground ~205
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.
| Name | Type | Req | Description |
|---|---|---|---|
| amount_degrees | string | – | – |
| hash | string | yes | – |
| hours | number | yes | – |
| label | string | – | – |
| lat | number | yes | – |
| lon | number | yes | – |
| payment | string | – | – |
| salt | string | – | – |
| wait | boolean | – | – |
No output schema declared.
No examples provided.
meet ~83
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.
| Name | Type | Req | Description |
|---|---|---|---|
| a | string | yes | – |
| b | string | yes | – |
No output schema declared.
No examples provided.
open_ground ~244
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.
| Name | Type | Req | Description |
|---|---|---|---|
| addr | string | yes | – |
| amount_degrees | string | yes | – |
| field | string | – | – |
| salt | string | yes | – |
| start | string | yes | – |
| tick | string | – | – |
No output schema declared.
No examples provided.
quote_ground ~121
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.
| Name | Type | Req | Description |
|---|---|---|---|
| hours | number | – | – |
| lat | number | yes | – |
| lon | number | yes | – |
| salt | string | – | – |
No output schema declared.
No examples provided.
rent_roll ~49
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
No output schema declared.
No examples provided.
stamp ~150
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().
| Name | Type | Req | Description |
|---|---|---|---|
| addr | string | – | – |
| hash | string | yes | – |
| label | string | – | – |
| lat | – | – | – |
| lon | – | – | – |
| payment | string | – | – |
No output schema declared.
No examples provided.
tell_the_house ~72
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.
| Name | Type | Req | Description |
|---|---|---|---|
| where | string | – | – |
| words | string | yes | – |
No output schema declared.
No examples provided.
tick ~133
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().
| Name | Type | Req | Description |
|---|---|---|---|
| light | boolean | – | – |
| slice | integer | – | – |
No output schema declared.
No examples provided.
verify_lease ~211
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/.
| Name | Type | Req | Description |
|---|---|---|---|
| amount_degrees | string | – | – |
| lease_json | string | yes | – |
| salt | string | – | – |
No output schema declared.
No examples provided.
witness ~262
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.
| Name | Type | Req | Description |
|---|---|---|---|
| addr | string | – | – |
| at | string | – | – |
| lat | – | – | – |
| lon | – | – | – |
| payment | string | – | – |
No output schema declared.
No examples provided.
What is the Geolithic MCP server?
Geolithic is an MCP server listed in the public MCP registry as io.github.HowardZheni/geolithic. One face of the Earth, yours alone for one term, proven on a public chain. A dollar. Readings free. This page covers its hosted endpoint (https://geolithicintelligence.com/mcp).
Is the Geolithic MCP server safe to use?
Geolithic scores 65 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 Geolithic MCP server expose?
Geolithic exposes 15 tools: catalog, tick, open_ground, rent_roll, ground, and 10 more. Their descriptions and schemas cost roughly 2,074 tokens of context every time the server is loaded.
Does the Geolithic MCP server require authentication?
No. We connected to Geolithic without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Geolithic MCP server still maintained?
Geolithic is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.