# io.github.Geepers4242/geepers-mcp (npm · geepers-mcp)

Resolve Geepers physical handles to exact coordinates + navigation for AI agents.

- Trust score: 74/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-21

## Components

- npm · `geepers-mcp`: 74/100 (this document), [markdown](https://verifymcp.io/servers/geepers4242-geepers-mcp/geepers-mcp.md), [page](https://verifymcp.io/servers/geepers4242-geepers-mcp/geepers-mcp)

## Channel facts

- Registry: `npm`
- Package: `geepers-mcp`
- Version: `0.1.1`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-21.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 31 of 96 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 19/100
  - Repository check failed: no source repository is declared.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 22 days ago).
  - Security-disclosure policy not yet verified: we couldn't inspect the source repository.
- **Schema Quality & AI Usability**: 69/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 73/100
  - Stability observed for 22 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add geepers4242-geepers-mcp -- npx -y geepers-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "geepers4242-geepers-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "geepers-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "geepers4242-geepers-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "geepers-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add geepers4242-geepers-mcp -- npx -y geepers-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "geepers4242-geepers-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "geepers-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add geepers4242-geepers-mcp --command npx --arg -y --arg geepers-mcp
```

### Hermes

```yaml
mcp_servers:
  geepers4242-geepers-mcp:
    command: "npx"
    args: ["-y", "geepers-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "geepers4242-geepers-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "geepers-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add geepers4242-geepers-mcp -t stdio -c npx -a -y geepers-mcp
```

### Other

```json
{
  "mcpServers": {
    "geepers4242-geepers-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "geepers-mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-21 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-19 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-16 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-14 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-12 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-10 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-08 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-06 (score 67, +3)

- [functional improvement] Stability: unverified → 0.23

## MCP tools (4)

### `resolve_geep` (~192 tokens)

Resolve a Geepers name to an exact place

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.

Input parameters:

- `name` (string, required): The Geepers name, with or without the leading `!` (e.g. `!demo-farm` or `amp.370george..pp234`).

### `get_geep_structure` (~141 tokens)

Get a place's full structure (layout)

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.

Input parameters:

- `name` (string, required): The root geep whose structure you want (e.g. `!demo-farm.farm` or `!amp.370george`).

### `search_geeps` (~201 tokens)

Find a geep within a known namespace

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.)

Input parameters:

- `query` (string): A name fragment to match (case-insensitive). Omit to list everything under `under`.
- `type` (string): Filter by kind.
- `under` (string, required): The root/namespace geep to search within (e.g. `!amp.370george`).

### `create_geep` (~262 tokens)

Mint a new Geepers name for a physical thing

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).

Input parameters:

- `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, required): The full geep name WITHOUT the leading `!` (e.g. `myco.depot.bay3`). Dots = nesting.
- `visibility` (string): Default public.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/geepers4242-geepers-mcp/geepers-mcp#diagnostics

## Score history

- 2026-09-21: 74
- 2026-09-20: 73
- 2026-09-19: 73
- 2026-09-18: 72
- 2026-09-17: 72
- 2026-09-16: 72
- 2026-09-15: 71
- 2026-09-14: 71
- 2026-09-13: 70
- 2026-09-12: 70
- 2026-09-11: 69
- 2026-09-10: 69
- 2026-09-09: 68
- 2026-09-08: 68
- 2026-09-07: 67
- 2026-09-06: 67
- 2026-09-05: 64
- 2026-09-04: 64
- 2026-09-03: 64
- 2026-09-02: 64
- 2026-09-01: 64
- 2026-08-31: 64
- 2026-08-30: 49

## Common questions

### 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 74 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 September 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 21 September 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.

## Links

- npm package: https://www.npmjs.com/package/geepers-mcp
- Socket report: https://socket.dev/npm/package/geepers-mcp
- Changelog RSS feed: https://verifymcp.io/servers/geepers4242-geepers-mcp/geepers-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/geepers4242-geepers-mcp/geepers-mcp.json
- HTML version of this page: https://verifymcp.io/servers/geepers4242-geepers-mcp/geepers-mcp