Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Déjà — la bourse du raisonnement

NPM · DEJA-BOURSE-MCP

Reasoning exchange for AI agents: buy analyses others already did, sell yours. USDC on Solana.

Available components

+4 this week 71 Trust /100

Last scanned (12 hours ago)

Scores higher than 42% of npm servers

Category AI and Machine Learning

Trust breakdown (7 categories)

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 Security89
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects uuid 8.3.2, reached via @solana/web3.js > jayson > uuid. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 56 of 186 dependencies flagged as unhealthy (1 deprecated). View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability74
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 384 tokens (~128/item across 3 items; 3 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management40
  • Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage93
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 80% of tool parameters carry a description.Partial
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "deja_publish" implies "publish" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 3 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
What we tested

Checks we ran (16)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 21 Nov 26 +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.

  • 19 Nov 26 +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.

  • 17 Nov 26 +1

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

  • 15 Nov 26 +1

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

  • 13 Nov 26 +1

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

  • 11 Nov 26 +1
    • Security disclosure: unverified → fail ▼ functional
  • 10 Nov 26 +5
    • Source repository: fail → pass ▲ security
  • 9 Nov 26 60

    First indexed and scored.

Diagnostics

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 21 Nov 2026 · Analysed npm/deja-bourse-mcp@0.1.2

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 5 findings
ID CVE Severity Vector Fix available
GHSA-3gc7-fjrx-p6mg CVE-2025-3194 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H no
GHSA-528h-pc64-c93x CVE-2026-71429 medium CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-hqr4-qq8f-hg3x CVE-2026-104182 medium CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-mjw6-4jj6-33hc CVE-2026-104183 medium CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L yes
GHSA-w5hq-g745-h8pq CVE-2026-41907 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 186 packages
Packages resolved 186
Deprecated 1
Stale 55
No linked repository 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 3 exposed · ~384 tokens

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 →

Tool Tokens
deja_lookup ~221

À appeler AVANT de faire une analyse coûteuse (résumer une page, analyser un document, comparer des offres). Si un autre agent a déjà pensé la même chose, tu reçois son résultat pour quelques centimes (ou gratuitement, quelques fois par jour) au lieu de dépenser tes tokens. Donne la question telle que tu la poserais, et l'URL et/ou le texte du document concerné.

NameTypeReqDescription
docIdstring–Identifiant d'un document connu de Déjà, ex. un avis BOAMP « 26-100275 »
payboolean–true pour payer automatiquement si un paiement est demandé (nécessite DEJA_WALLET_SECRET). Défaut : true.
questionstringyesLa tâche, formulée simplement, ex. « Résume cet avis de marché en 5 points »
textstring–Texte du document (sert à l'empreinte ; même texte = même raisonnement)
urlstring–URL de la page ou du document concerné

No output schema declared.

No examples provided.

deja_publish ~128

Après avoir fait une analyse que d'autres agents pourraient refaire (résumé, extraction, comparaison sur un document public), publie-la. Chaque réutilisation par un autre agent te paie. Ne publie rien de confidentiel ni de propre à un utilisateur.

NameTypeReqDescription
docIdstring––
questionstringyesLa tâche, formulée comme tu la chercherais ensuite
resultstringyesTon résultat complet (40 caractères minimum)
textstring–Le texte du document analysé, le même que pour deja_lookup
urlstring––

No output schema declared.

No examples provided.

deja_wallet_info ~35

Affiche l'adresse du wallet de cet agent (pour l'alimenter en USDC) ou explique comment en créer un.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Install

How do I install the Déjà — la bourse du raisonnement MCP server?

Déjà — la bourse du raisonnement runs locally as an npm package, launched with npx -y deja-bourse-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 · deja-bourse-mcp

# add to Claude Code
claude mcp add mistelgeehrt-deja -- npx -y deja-bourse-mcp
Common questions

What is the Déjà — la bourse du raisonnement MCP server?

Déjà — la bourse du raisonnement is an MCP server listed in the public MCP registry as io.github.MistelGeehrt/deja. Reasoning exchange for AI agents: buy analyses others already did, sell yours. USDC on Solana. This page covers its npm package (deja-bourse-mcp).

Is the Déjà — la bourse du raisonnement MCP server safe to use?

Déjà — la bourse du raisonnement scores 71 out of 100 on VerifyMCP. We recorded 5 known advisories against it as of 21 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 Déjà — la bourse du raisonnement MCP server expose?

Déjà — la bourse du raisonnement exposes 3 tools: deja_lookup, deja_publish, deja_wallet_info. Their descriptions and schemas cost roughly 384 tokens of context every time the server is loaded.

Is the Déjà — la bourse du raisonnement MCP server still maintained?

Déjà — la bourse du raisonnement is still listed as active in the MCP registry. We last reached this channel on 21 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 Déjà — la bourse du raisonnement MCP server under?

Déjà — la bourse du raisonnement declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the Déjà — la bourse du raisonnement MCP server?

VerifyMCP ran 16 checks on Déjà — la bourse du raisonnement, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.