io.github.Geepers4242/geepers-mcp
NPM · GEEPERS-MCP
Resolve Geepers physical handles to exact coordinates + navigation for AI agents.
Available components
Last scanned (1 hour ago)
Scores higher than 46% of npm servers
Category Maps and Location
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: no source repository is declared. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 67 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability69
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 796 tokens (~199/item across 4 items; 4 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 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
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.
- 2 Nov 26 +1
- Stability: 0.97 → pass security
- 1 Nov 26 −1
- Stability: pass → 0.97 functional
- 26 Oct 26 +1
- Stability: 0.97 → pass security
- 25 Oct 26 −1
- Stability: pass → 0.97 functional
- 24 Oct 26 −5
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- 19 Oct 26 +1
- Stability: 0.97 → pass security
- 17 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
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 · Analysed npm/geepers-mcp@0.1.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
create_geep Mint a new Geepers name for a physical thing ~262
Mint a NEW Geepers name for a physical thing (a point, gate, track, or sub-geep) on behalf of a user or business — a permanent, resolvable, verified handle other agents and humans can navigate to. USE THIS when acting in the world creates a place worth a durable address (a delivery point, a job site, an asset, a meeting spot). Names nest with dots (`org.site.gate2`); the immediate parent must already exist and be owned by your account. Requires a Geepers account token (env GEEPERS_TOKEN, or GEEPERS_EMAIL + GEEPERS_PASSWORD). Per-namespace leaf names are unique (a clash returns the next free name).
| Name | Type | Req | Description |
|---|---|---|---|
| data_value | string | – | For a data geep (e.g. a URL, email, phone). |
| geep_type | string | – | static (default) | data | pointer. |
| lat | number | – | Latitude for a point geep. |
| lon | number | – | Longitude for a point geep. |
| name | string | yes | The full geep name WITHOUT the leading `!` (e.g. `myco.depot.bay3`). Dots = nesting. |
| visibility | string | – | Default public. |
No output schema declared.
No examples provided.
get_geep_structure Get a place's full structure (layout) ~141
Get the full PUBLIC structure of a place-geep — its geofence boundary, gates/points, tracks (paths), and all public sub-geeps, each with coordinates and type. USE THIS to understand a place's layout before acting: which gate to route through, where the tracks/paths run, what sub-locations exist. Returns a tree an agent can reason over (e.g. to pick the right delivery point or plan a route through a site). Public.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | The root geep whose structure you want (e.g. `!demo-farm.farm` or `!amp.370george`). |
No output schema declared.
No examples provided.
resolve_geep Resolve a Geepers name to an exact place ~192
Resolve a Geepers name — a verified physical handle, e.g. `!amp.370george..pp234` or `!demo-farm` — to EXACT coordinates, the place type, and a ready-to-use directions link. USE THIS INSTEAD OF guessing a street address or inventing a lat/long: whenever you need a precise, verified physical location that a human can also act on (deliver, dispatch, meet, navigate). Geeps resolve deterministically from a live registry — stop hallucinating addresses. Supports the `..` shortcut to skip middle levels (`!amp.370george..pp234` finds pp234 anywhere under that building). Public — no auth needed.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | The Geepers name, with or without the leading `!` (e.g. `!demo-farm` or `amp.370george..pp234`). |
No output schema declared.
No examples provided.
search_geeps Find a geep within a known namespace ~201
Find a specific geep by name-fragment or type WITHIN a known namespace/property (e.g. find `pp234`, or all `gate`s, under `!amp.370george`). Provide `under` = the root geep and `query` = a name fragment (and optionally `type` = point|gate|track|boundary). USE THIS when you know the organisation/property but need to locate the exact sub-geep to act on. For an exact known name use resolve_geep; this is discovery within a namespace. Public. (Global/nearby search across all of Geepers is not yet exposed.)
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | – | A name fragment to match (case-insensitive). Omit to list everything under `under`. |
| type | string | – | Filter by kind. |
| under | string | yes | The root/namespace geep to search within (e.g. `!amp.370george`). |
No output schema declared.
No examples provided.
How do I install the io.github.Geepers4242/geepers-mcp server?
io.github.Geepers4242/geepers-mcp runs locally as an npm package, launched with npx -y geepers-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · geepers-mcp
claude mcp add geepers4242-geepers-mcp -- npx -y geepers-mcp
What is the io.github.Geepers4242/geepers-mcp server?
io.github.Geepers4242/geepers-mcp is listed in the public MCP registry as io.github.Geepers4242/geepers-mcp. Resolve Geepers physical handles to exact coordinates + navigation for AI agents. This page covers its npm package (geepers-mcp).
Is the io.github.Geepers4242/geepers-mcp server safe to use?
io.github.Geepers4242/geepers-mcp scores 73 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 November 2026. It declares no install or post-install scripts. 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 io.github.Geepers4242/geepers-mcp server expose?
io.github.Geepers4242/geepers-mcp exposes 4 tools: resolve_geep, get_geep_structure, search_geeps, create_geep. Their descriptions and schemas cost roughly 796 tokens of context every time the server is loaded.
Is the io.github.Geepers4242/geepers-mcp server still maintained?
io.github.Geepers4242/geepers-mcp 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.
What licence is the io.github.Geepers4242/geepers-mcp server under?
io.github.Geepers4242/geepers-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.