# imprimeur.paris (remote · mcp.imprimeur.paris)

Independent directory of printers and copy shops in Paris: search, details, file checks.

- Trust score: 67/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `mcp.imprimeur.paris`: 67/100 (this document), [markdown](https://verifymcp.io/servers/mojapiero-imprimeur-paris/mcp.md), [page](https://verifymcp.io/servers/mojapiero-imprimeur-paris/mcp)

## Channel facts

- Endpoint: `https://mcp.imprimeur.paris/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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

Scored 2026-11-05.

- **Endpoint Security**: 77/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 61/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 951 tokens (~135/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability check failed: schema churn in the 3 days we've observed: 1 tool removals, 0 breaking changes, 0 auth/transport breaks, 1 additions.
- **Tool Coverage**: 67/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% 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 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the imprimeur.paris MCP server?

imprimeur.paris is a hosted endpoint at https://mcp.imprimeur.paris/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.

### Claude

```bash
claude mcp add --transport http mojapiero-imprimeur-paris 'https://mcp.imprimeur.paris/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "mojapiero-imprimeur-paris": {
      "url": "https://mcp.imprimeur.paris/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "mojapiero-imprimeur-paris": {
      "type": "http",
      "url": "https://mcp.imprimeur.paris/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.mojapiero-imprimeur-paris]
url = "https://mcp.imprimeur.paris/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "mojapiero-imprimeur-paris": {
      "type": "remote",
      "url": "https://mcp.imprimeur.paris/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add mojapiero-imprimeur-paris --url 'https://mcp.imprimeur.paris/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  mojapiero-imprimeur-paris:
    url: "https://mcp.imprimeur.paris/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "mojapiero-imprimeur-paris": {
      "Transport": "http",
      "Url": "https://mcp.imprimeur.paris/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add mojapiero-imprimeur-paris -t streamable-http -u 'https://mcp.imprimeur.paris/mcp'
```

### Other

```json
{
  "mcpServers": {
    "mojapiero-imprimeur-paris": {
      "type": "http",
      "url": "https://mcp.imprimeur.paris/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## 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-11-03 (score 67, 0)

- [security regression] Stability: unverified → fail
- [security regression] A breaking change shipped without a version bump: still 1.0.0
- [security regression] Tool “verifier_fichier” was removed
- [security] The server rewrote its instructions, which are the text every model session reads
- [functional] New tool “points_controle_fichier”

### 2026-11-02 (score 67)

First indexed and scored.

## MCP tools (7)

### `rechercher_imprimeurs` (~204 tokens)

Rechercher des imprimeurs à Paris

Recherche des imprimeurs parisiens.

technique : identifiant ou libellé (impression-numerique, offset, grand-format, serigraphie, typographie,
            reliure-faconnage, textile, packaging, reprographie, signaletique).
arrondissement_paris : 1 à 20, « 11e » ou code postal (75011).
mot_cle : cherché dans le nom, l'adresse et la description.
ouvert_samedi, commande_en_ligne : ne garder que les établissements qui l'ont confirmé.
limite : 50 au maximum.
langue : fr, en, es, de, it ou zh (libellés et liens).

Input parameters:

- `arrondissement_paris`
- `commande_en_ligne`
- `langue` (string)
- `limite` (integer)
- `mot_cle`
- `ouvert_samedi`
- `technique`

### `fiche_imprimeur` (~62 tokens)

Fiche détaillée d'un imprimeur

Fiche complète d'un établissement, par son identifiant (champ « id ») ou son SIRET. langue : fr, en, es, de, it, zh.

Input parameters:

- `identifiant` (string, required)
- `langue` (string)

### `lister_arrondissement` (~65 tokens)

Imprimeurs d'un arrondissement

Tous les imprimeurs d'un arrondissement de Paris (1 à 20, « 11e » ou 75011). langue : fr, en, es, de, it, zh.

Input parameters:

- `arrondissement_paris` (string, required)
- `langue` (string)

### `lister_techniques` (~49 tokens)

Techniques référencées

Techniques et services référencés, avec le nombre d'établissements pour chacun. langue : fr, en, es, de, it, zh.

Input parameters:

- `langue` (string)

### `trouver_imprimeur_capable` (~150 tokens)

Trouver un imprimeur capable de réaliser un produit

Imprimeurs parisiens capables de réaliser un produit (« kakémono », « stickers », « mémoire relié »…)
ou une technique, près d'un lieu (latitude/longitude) ou dans un arrondissement.
Ordre : distance si un lieu est donné, sinon alphabétique. Chaque résultat indique la raison de sa présence,
la station de transport la plus proche et le lien de sa fiche. limite : 50 au maximum.

Input parameters:

- `arrondissement_paris`
- `langue` (string)
- `latitude`
- `limite` (integer)
- `longitude`
- `ouvert_samedi`
- `produit`
- `technique`

### `points_controle_fichier` (~82 tokens)

Points à vérifier dans un fichier d'impression

Liste des points à contrôler dans un fichier avant de le confier à un imprimeur, pour un produit donné
(fond perdu, résolution, couleurs, polices…), et lien vers le vérificateur de PDF du site, qui fonctionne dans
le navigateur sans envoyer le fichier. Ce serveur ne reçoit aucun fichier.

Input parameters:

- `produit` (string, required)

### `preparer_demande_devis` (~117 tokens)

Préparer une demande de devis

Rédige un cahier des charges de demande de devis (produit, quantité, format, papier, finition, délai)
et donne les moyens de contact publics des imprimeurs choisis (identifiants issus des autres outils).
Rien n'est envoyé ni conservé : la personne transmet elle-même sa demande.

Input parameters:

- `delai`
- `finition`
- `format`
- `identifiants`
- `papier`
- `produit` (string, required)
- `quantite`

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/mojapiero-imprimeur-paris/mcp#diagnostics

## Score history

- 2026-11-05: 67
- 2026-11-04: 67
- 2026-11-03: 67
- 2026-11-02: 67

## Common questions

### What is the imprimeur.paris MCP server?

imprimeur.paris is an MCP server listed in the public MCP registry as io.github.mojapiero/imprimeur-paris. Independent directory of printers and copy shops in Paris: search, details, file checks. This page covers its hosted endpoint (https://mcp.imprimeur.paris/mcp).

### Is the imprimeur.paris MCP server safe to use?

imprimeur.paris scores 67 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 imprimeur.paris MCP server expose?

imprimeur.paris exposes 7 tools: rechercher_imprimeurs, fiche_imprimeur, lister_arrondissement, lister_techniques, trouver_imprimeur_capable, and 2 more. Their descriptions and schemas cost roughly 729 tokens of context every time the server is loaded.

### Does the imprimeur.paris MCP server require authentication?

No. We connected to imprimeur.paris without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the imprimeur.paris MCP server still maintained?

imprimeur.paris 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 did VerifyMCP test on the imprimeur.paris MCP server?

VerifyMCP ran 13 checks on imprimeur.paris, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://mcp.imprimeur.paris/mcp
- Website: https://imprimeur.paris/en/mcp/
- Changelog RSS feed: https://verifymcp.io/servers/mojapiero-imprimeur-paris/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/mojapiero-imprimeur-paris/mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/mojapiero-imprimeur-paris/mcp.json
- HTML version of this page: https://verifymcp.io/servers/mojapiero-imprimeur-paris/mcp