# io.github.IvandeMurard/paris-compass-mcp (npm · paris-compass-mcp)

Paris commercial premises from open data: shopfront history, street turnover, sourced figures.

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

## Components

- npm · `paris-compass-mcp`: 78/100 (this document), [markdown](https://verifymcp.io/servers/ivandemurard-paris-compass-mcp/paris-compass-mcp.md), [page](https://verifymcp.io/servers/ivandemurard-paris-compass-mcp/paris-compass-mcp)

## Channel facts

- Registry: `npm`
- Package: `paris-compass-mcp`
- Version: `0.1.2`
- 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-24.

- **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 104 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (Apache-2.0).
  - Actively maintained (last published 20 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 66/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1389 tokens (~231/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 70/100
  - Stability observed for 21 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 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.IvandeMurard/paris-compass-mcp server?

io.github.IvandeMurard/paris-compass-mcp runs locally as an npm package, launched with npx -y paris-compass-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 ivandemurard-paris-compass-mcp -- npx -y paris-compass-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "ivandemurard-paris-compass-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "paris-compass-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ivandemurard-paris-compass-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "paris-compass-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add ivandemurard-paris-compass-mcp -- npx -y paris-compass-mcp
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add ivandemurard-paris-compass-mcp --command npx --arg -y --arg paris-compass-mcp
```

### Hermes

```yaml
mcp_servers:
  ivandemurard-paris-compass-mcp:
    command: "npx"
    args: ["-y", "paris-compass-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "ivandemurard-paris-compass-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "paris-compass-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add ivandemurard-paris-compass-mcp -t stdio -c npx -a -y paris-compass-mcp
```

### Other

```json
{
  "mcpServers": {
    "ivandemurard-paris-compass-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "paris-compass-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-23 (score 78, +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-21 (score 77, +1)

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

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

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

### 2026-09-17 (score 75, +1)

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

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

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

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

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

### 2026-09-11 (score 72, +4)

- [functional improvement] Stability: unverified → 0.27

### 2026-09-04 (score 68, +15)

- [security improvement] Malware scan: unverified → pass

## MCP tools (6)

### `list_sources` (~37 tokens)

List data sources

Every dataset the Compass tools actually draw from, with licence and freshness. Not a marketing list — only sources a tool call here will really touch.

### `score_location` (~341 tokens)

Score a location

Scores one point on five amenity categories (schools, healthcare, groceries, parks, transit), walkability, a footfall proxy, and a road-noise proxy — each figure carrying its source, licence, date and method. No single score out of 100: PERIMETRE.md refuses one on the grounds that weights depend on the trade, so axes are returned separately.

Input parameters:

- `lat` (number, required): Latitude. Bornée à l'emprise réelle de Paris (48,8156–48,9022), mesurée sur les 80 quartiers. Un point dans ces bornes peut malgré tout être hors du recensement — Boulogne, Levallois, Saint-Mandé et…
- `lng` (number, required): Longitude. Bornée à l'emprise réelle de Paris (2,2241–2,4698), mesurée sur les 80 quartiers. Voir la remarque sur la latitude : la boîte est un rectangle, le corpus ne l'est pas.
- `radius_m` (number): Search radius in metres. Capped at 2000 — beyond that the question stops being 'this neighbourhood' (compass_max_radius_m).
- `vintage_year`: BDCom survey year for the premises layer (occupancy, vacancy). Only 2023 is ODbL: 2017 and 2020 carry an APUR licence that has not been read, so a public caller receives neither their contents nor th…

### `compare_locations` (~193 tokens)

Compare two locations

Scores two points with score_location's method and returns both sets side by side, plus a per-axis numeric delta (b minus a). No combined verdict: a single score would average axes that pull in opposite directions for different trades, which is exactly what this product refuses to do (PERIMETRE.md §4).

Input parameters:

- `a` (object, required): First location
- `b` (object, required): Second location
- `radius_m` (number): Search radius in metres, applied to BOTH points so the two score sets stay comparable. Capped at 2000 (compass_max_radius_m).
- `vintage_year`: BDCom survey year for the premises layer. Only 2023 is ODbL: 2017 and 2020 carry an APUR licence that has not been read, so a public caller receives neither their contents nor their counts, and the s…

### `explain_score` (~324 tokens)

Explain one score

Full detail on a single axis of score_location — value, source, licence, date, method and caveat — as a sentence and as structured data. Use after score_location to justify one figure rather than re-deriving it from the full response.

Input parameters:

- `lat` (number, required): Latitude. Bornée à l'emprise réelle de Paris (48,8156–48,9022), mesurée sur les 80 quartiers. Un point dans ces bornes peut malgré tout être hors du recensement — Boulogne, Levallois, Saint-Mandé et…
- `lng` (number, required): Longitude. Bornée à l'emprise réelle de Paris (2,2241–2,4698), mesurée sur les 80 quartiers. Voir la remarque sur la latitude : la boîte est un rectangle, le corpus ne l'est pas.
- `metric` (string, required): Which axis of score_location to explain in detail.
- `radius_m` (number): Search radius in metres. Pass the same value score_location was called with, otherwise the explanation describes a different question. Capped at 2000 (compass_max_radius_m).
- `vintage_year`: BDCom survey year for the premises layer. Only 2023 is ODbL: 2017 and 2020 carry an APUR licence that has not been read, so a public caller receives neither their contents nor their counts, and the s…

### `find_premises` (~336 tokens)

Find premises near a point

Ground-floor premises surveyed by APUR's door-to-door BDCom census near a point, each with the location_id that trace_premise takes. Returns candidates, not a single match: premises routinely share an address and a coordinate, so picking one is the caller's decision. Vintage 2023 only (the sole ODbL vintage) — a premise that stopped being retail before 2023 is not listed here, and trace_premise is where its earlier life shows up.

Input parameters:

- `lat` (number, required): Latitude. Bornée à l'emprise réelle de Paris (48,8156–48,9022), mesurée sur les 80 quartiers. Un point dans ces bornes peut malgré tout être hors du recensement — Boulogne, Levallois, Saint-Mandé et…
- `limit` (integer): Maximum premises returned, capped at 200. `total_matched` carries the count BEFORE this cut, so a truncated answer still has its denominator.
- `lng` (number, required): Longitude. Bornée à l'emprise réelle de Paris (2,2241–2,4698), mesurée sur les 80 quartiers. Voir la remarque sur la latitude : la boîte est un rectangle, le corpus ne l'est pas.
- `radius_m` (number): Search radius in metres. Capped at 500, well below the 2000 the database allows: this call identifies a shopfront, it does not describe a neighbourhood. Widen it only when the coordinates are approxi…

### `trace_premise` (~158 tokens)

Trace one premise's history

Everything known about one premise in chronological order: APUR BDCom survey rows (2017, 2020, 2023) and BODACC legal notices — business sales with their published price, safeguard, receivership and liquidation proceedings. Every row carries the record it came from, its evidence, and a derived confidence level with the rule that produced it. Answers 'has a restaurant ever been here', 'has this unit already changed use', 'was there a vacant spell', and 'what did the business last sell for'. Takes a location_id from find_premises.

Input parameters:

- `location_id` (integer, required): A location_id returned by find_premises. Not a BDCom `ordre` and not a SIRET.

## Diagnostics

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

## Score history

- 2026-09-24: 78
- 2026-09-23: 78
- 2026-09-22: 77
- 2026-09-21: 77
- 2026-09-20: 76
- 2026-09-19: 76
- 2026-09-18: 75
- 2026-09-17: 75
- 2026-09-16: 74
- 2026-09-15: 74
- 2026-09-14: 73
- 2026-09-13: 73
- 2026-09-12: 72
- 2026-09-11: 72
- 2026-09-10: 68
- 2026-09-09: 68
- 2026-09-08: 68
- 2026-09-07: 68
- 2026-09-06: 68
- 2026-09-05: 68
- 2026-09-04: 68
- 2026-09-03: 53

## Common questions

### What is the io.github.IvandeMurard/paris-compass-mcp server?

io.github.IvandeMurard/paris-compass-mcp is listed in the public MCP registry as io.github.IvandeMurard/paris-compass-mcp. Paris commercial premises from open data: shopfront history, street turnover, sourced figures. This page covers its npm package (paris-compass-mcp).

### Is the io.github.IvandeMurard/paris-compass-mcp server safe to use?

io.github.IvandeMurard/paris-compass-mcp scores 78 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 24 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.IvandeMurard/paris-compass-mcp server expose?

io.github.IvandeMurard/paris-compass-mcp exposes 6 tools: list_sources, score_location, compare_locations, explain_score, find_premises, trace_premise. Their descriptions and schemas cost roughly 1,389 tokens of context every time the server is loaded.

### Is the io.github.IvandeMurard/paris-compass-mcp server still maintained?

io.github.IvandeMurard/paris-compass-mcp is still listed as active in the MCP registry. We last reached this channel on 24 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.IvandeMurard/paris-compass-mcp server under?

io.github.IvandeMurard/paris-compass-mcp declares the Apache-2.0 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/paris-compass-mcp
- Socket report: https://socket.dev/npm/package/paris-compass-mcp
- Repository: https://github.com/IvandeMurard/paris-compass
- Changelog RSS feed: https://verifymcp.io/servers/ivandemurard-paris-compass-mcp/paris-compass-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/ivandemurard-paris-compass-mcp/paris-compass-mcp.json
- HTML version of this page: https://verifymcp.io/servers/ivandemurard-paris-compass-mcp/paris-compass-mcp