Compass MCP server

Official sources — npm package paris-compass-mcp, MCP Registry entry io.github.IvandeMurard/paris-compass-mcp, source code IvandeMurard/paris-compass, website paris-compass.lovable.app. Free, no account. A listing found elsewhere is not operated by the author unless one of these sources says so.

PLAN.md §4.1, PERIMETRE.md §8 — the same scoring core the browser uses (../src/core), reached with the same trust boundary an anonymous visitor has: the Supabase anon key, never a service key. list_sources describes only what these tools actually call — never a source no tool here touches.

Install

Nothing to configure. The package carries the public project's read-only endpoint — the same URL and anonymous key the website already hands to every browser that opens it. There is no account to create and no key to request, because there is no key that is yours to keep.

Add it to an MCP client's configuration:

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

Claude Code, in one line:

claude mcp add paris-compass -- npx -y paris-compass-mcp

Node 20.12 or later. To read a different Supabase project — a derived deployment, w7-kit — set SUPABASE_URL and SUPABASE_ANON_KEY in the client's env block: the environment wins over the built-in values.

Ce qu'on peut lui demander

Une fois branché, à coller tel quel dans une conversation avec l'agent :

Tu as accès au serveur MCP paris-compass, qui décrit les locaux commerciaux de Paris intra-muros à partir de données publiques. Avant de répondre, appelle list_sources et tiens-t'en à ce qu'il annonce : chaque chiffre porte sa source, sa licence, sa date et son degré de certitude, et tu dois les citer. Ne combine jamais les axes en une note unique, et ne comble jamais un trou par une estimation — « indéterminé » est une réponse valide, une moyenne inventée n'en est pas une. Pour l'historique d'une vitrine : find_premises d'abord, qui rend des candidats et non une correspondance, puis trace_premise sur le location_id retenu.

Run from the repository

For development in this repository, where the server runs from source rather than from the published bundle:

npm.cmd install
npm.cmd run start

Speaks MCP over stdio. Point an MCP client at npx tsx src/index.ts from this directory. .env is optional here too — copy .env.example to .env only to override the public values.

If tsx refuses to start — spawn UNKNOWN, errno -4094 — it is not this package: an application-control policy on the development machine blocks the esbuild binary inside mcp-server/node_modules (docs/REPRISE.md). Build with the repository's own esbuild and point the client at the bundle instead, which is what verify:mcp and smoke:mcp already do:

npm.cmd run verify:mcp        # builds mcp-server/.build/server.mjs on the way
# then: command `node`, args [ "<repo>/mcp-server/.build/server.mjs" ]

Tools

| Tool | Input | What it returns | | --- | --- | --- | | list_sources | — | Every dataset the other tools draw from — licence, freshness, what it feeds | | score_location | lat, lng, radius_m?, vintage_year? | A one-sentence verdict — or its refusal — plus five amenity scores, walkability, footfall and noise, each a Measured<T>: value, source, licence, date, method, caveat | | compare_locations | a, b, radius_m?, vintage_year? | Both full score sets with their own verdicts, a per-axis numeric delta, and which axes are comparable at all. Two points, never a list, and no combined verdict — both refused by design (PERIMETRE.md §1 and §4) | | explain_score | lat, lng, metric, radius_m?, vintage_year? | Full detail on one axis, as a sentence and as structured data | | find_premises | lat, lng, radius_m?, limit? | BDCom premises near a point with their location_id, plus total_matched as the denominator. Candidates, never one match | | trace_premise | location_id | compass_address_timeline: BDCom surveys and BODACC notices in order, each with its record, its evidence and its confidence level |

find_premises and trace_premise are a pair — the timeline takes a location_id, and nothing else here hands one out. Two tools rather than one because up to 120 premises share a coordinate and 69 % share a street number: "the nearest premise" would pick one shopfront out of a stack and present it as the answer, so the candidates are returned and the caller chooses.

find_premises is pinned to vintage 2023 and takes no vintage_year. 2023 is the only ODbL vintage; for 2017 and 2020, 20260809000011 withholds not just the contents but the existence of a record, and a lookup that listed their premises would disclose exactly that. Those years still appear in trace_premise, as withheld rows — the licensed way to say something is there.

The verdict, and what it shares with the web page

score_location returns a verdict alongside its figures: one sentence of named axes, or a refusal saying which bearing finding is missing and why. It is composed by src/core/verdict.ts, the same function /contexte/<adresse> calls — not by anything in this package. That is what « the same answer for an agent » means here, and it is checked rather than claimed: the PARITE family of verify.ts recomposes the sentence from the figures this server publishes and fails if the two differ, and npm.cmd run test fails if either surface stops going through the core.

What is not shared is the corpus. This server reads premises from APUR's BDCom door-to-door survey; the browser reads them from OpenStreetMap's shop=vacant tagging. The figures can differ, and the server's are the better ones. The composition rule is shared; the data is not.

There is still no score out of 100, here or there.

Verify

Both run from the repository root, not from here — they typecheck this package and build it before touching the network, so there is nothing to install or remember first:

npm.cmd run verify:mcp

The gate. Five families — the six tools registered against the six documented above (INVENTAIRE), every figure attributed to the layer it was read from (PROVENANCE), the two freshness dates kept apart (FRAICHEUR), the anonymous licence path with 2017 and 2020 withheld and no label borrowed to fill them (LICENCE), and four failure modes including an unreachable database (PANNE). Exits non-zero on a broken rule. Source: src/verify.ts.

The number of checks is not fixed, by design — 41 when both upstreams answer, fewer when Overpass rate-limits (measured 24–25 August). PROVENANCE collapses from five assertions to two when the amenity layer never arrived: there is no point asserting the provenance of figures that were never computed, and pretending otherwise would be a green tick standing for nothing. Read the 0 en échec, not the total.

npm.cmd run smoke:mcp

The reading. Spawns the server as a real client would and prints every tool's raw answer. It asserts nothing and exits 0 as long as nothing throws — useful when a rule has broken and you want to see what an agent actually receives, useless as a control.

Overpass is a shared public mirror and does rate-limit under repeated testing (context_failures: [{ layer: "amenities", reason: "Overpass responded 429" }]) — that is the server reporting a real outage honestly, not a bug. verify:mcp records those calls as panne and suspends the assertions that depend on them, rather than failing; it still checks that the outage was reported and that no figure came back as a measured zero. Run either sparingly rather than in a loop.

What this does not cover yet

~~Every field's source currently reads "OpenStreetMap via Overpass" even where the premises layer comes from BDCom via Supabase.~~ Fixed on 24 August by w0-provenance (#10): scoreLocation takes a LayerOrigins — one Origin per layer — and each metric is attributed to the layer it actually reads. Measured through this server the same day at Montorgueil: the seven OpenStreetMap figures cite OSM with the query date, and footfall cites APUR BDCom 2023 + OpenStreetMap via Overpass with asOf: 2023-06, the survey's date and not the query's. Pinned by P4/P5 in verify.ts so it cannot silently regress.

~~A point outside the BDCom corpus but inside the accepted coordinate box is still scored as though the corpus covered it.~~ Fixed on 25 August by 20260825000003 (#55, DIAGNOSTIC.md §16). compass_scoring_context_within now tests membership of the 80 quartier polygons and returns an out_of_corpus marker row, so the layer is withdrawn and footfall comes back unknown with its reason — the same shape withheld already had.

Both halves are pinned, and the second is the one that matters: E12 checks that a genuinely empty radius inside Paris still reads as a measured zero. The Bois de Vincennes sits in the Picpus quartier and holds no premise within 400 m — treating every empty result as "outside the corpus" would have passed E11 and destroyed the one answer the data gives with certainty.

~~Freshness is reported for BDCom only; BODACC and SIRENE have no ingestion date.~~ Closed on 25 August by w0-cron (#6). list_sources now carries a freshness block per dataset, and it deliberately reports two dates rather than one: dataAsOf is how current the facts are, lastLoadedAt is when this copy was refreshed. Reloading does not make the facts newer — BDCom reloaded on 25 August still reads dataAsOf: "2023-06". upkeep says whether the refresh is actually automated, so a declared cadence cannot be mistaken for a kept one. Pinned by F1–F4 in verify.ts.

~~No tool here exposes compass_address_timeline.~~ Exposed on 17 August as trace_premise, with find_premises as the lookup it needs. The front still has the same gap on its side (PLAN.md §2.7, "la fiche locale"): this server is now the only consumer of the timeline outside the evaluation gate.

~~compass_premises_within still has the silent-absence defect.~~ Fixed the same day, in 20260817000001, and covered by I14/I15. Writing find_premises is what surfaced it: the function is SECURITY INVOKER, the RLS policy of 20260809000008 restricts premise_observation to redistributable vintages, and it answered a withheld vintage with zero rows — byte for byte what a genuinely empty radius returns.

Measured as a real anonymous caller through PostgREST at Châtelet over 800 m, before and after:

| | 2017 | 2020 | 2023 | 2023 @ 1 m | | --- | --- | --- | --- | --- | | before | 0 rows | 0 rows | 3 059 | 0 rows | | after | 1 row, withheld | 1 row, withheld | 3 059 | 0 rows |

The last column is the half that gets skipped: a genuinely empty radius still reads as empty, so the fix did not swap one defect for its mirror. All three functions carrying the licence rule are now covered — I9/I10, I12/I13, I14/I15.