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.

l0g.fr Risk Intelligence

REMOTE · L0G.FR · 2 COMPONENTS

Read-only macro risk analysis, evidence, signals, and source-backed research from l0g.fr.

0 this week 90 Trust /100

Last scanned (12 hours ago)

Scores higher than 98% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Finance and Payments

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security83
Transport & Reachability100
Schema Quality & AI Usability84
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 977 tokens (~61/item across 16 items; 6 tools + 10 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 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
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.

  • 3 Nov 26 0
    • Stability: 0.97 → pass security
  • 2 Nov 26 0
    • Stability: pass → 0.97 functional
  • 26 Oct 26 0
    • Server version: 1.24.7 → 1.24.8 functional
  • 23 Oct 26 0
    • Server version: 1.24.6 → 1.24.7 functional
  • 10 Oct 26 0
    • Server version: 1.24.5 → 1.24.6 functional
  • 4 Oct 26 90
    • Stability: unverified → pass ▲ security
    • HSTS header: unverified → pass ▲ security
    • Authorization: unverified → partial ▲ security
    • Injection markers: unverified → pass ▲ security
    • TLS certificate: unverified → pass ▲ security
    • Transport: fail → pass ▲ security
    • Endpoint reachability: unreachable → reachable ▲ functional
    • MCP protocol: unverified → pass ▲ functional
    • Schema quality: unverified → 100 ▲ functional
    • Tool coverage: unverified → 100 ▲ functional
  • 3 Oct 26 0
    • Endpoint reachability: reachable → unreachable ▼ security
    • HSTS header: pass → unverified ▼ security
    • TLS certificate: pass → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Authorization: partial → unverified ▼ security
    • Stability: pass → unverified ▼ security
    • Transport: pass → fail ▼ security
    • Tool coverage: 100 → unverified ▼ functional
    • Capabilities: pass → unverified ▼ functional
    • Schema quality: 100 → unverified ▼ functional
  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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 5 Nov 2026 · Probed https://l0g.fr/api/mcp/compact

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=l0g.fr CN=YE1,O=Let's Encrypt,C=US 23 Sept 2026 22 Dec 2026 ECDSA 256 ECDSA-SHA384 6325ea3e1ce4e69d0db20549db47d24a715
SANs: l0g.fr, watch.l0g.fr, www.l0g.fr
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC secure

Validation of l0g.fr. — Secure

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
fr. present 65381 13 Verified
l0g.fr. present 14561 8 Verified
l0g.fr. Verified address RRset verified with the apex keys
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=63072000; includeSubDomains; preload
content-security-policy default-src 'self'; script-src 'self' 'wasm-unsafe-eval'; script-src-attr 'none'; style-src 'self' 'unsafe-inline'; img-src 'self' data:; font-src 'self'; connect-src 'self'; frame-src 'none'; worker-src 'self' blob:; manifest-src 'self'; media-src 'self'; object-src 'none'; base-uri 'self'; form-action 'self'; frame-ancestors 'self'; trusted-types 'none'; require-trusted-types-for 'script'; upgrade-insecure-requests
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy strict-origin-when-cross-origin
permissions-policy geolocation=(), microphone=(), camera=(), interest-cohort=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://l0g.fr/api/mcp/compact Verified 200
http (plaintext) http://l0g.fr/api/mcp/compact HTTPS enforced 301 https://l0g.fr/api/mcp/compact
MCP tools · 6 exposed · ~755 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
build_research_pack ~133

Compose en un appel un paquet de recherche déterministe : documents classés, claims canoniques, sources primaires, liens claim -> preuve, fraîcheur, Risk Diff, éléments adverses, limites et URLs citables. Ne produit aucune opinion d’investissement.

NameTypeReqDescription
asOfstring–Date point-in-time optionnelle au format YYYY-MM-DD.
languagestringyesLangue des documents recherchés : fr ou en.
limitinteger–Nombre maximum de documents.
querystringyesQuestion ou thème de recherche.
riskWindowstring–Fenêtre Risk Diff.
NameTypeReqDescription
adversarialFindingsarray––
asOf–––
citationUrlsarray––
claimEvidencearray––
claimsarray––
documentsarray––
errorstring––
freshness–––
knownLimitationsarray––
languagestring––
parametersobject––
primarySourcesarray––
querystring––
riskDiff–––
versionstring––

No examples provided.

discover_l0g ~50

Point d’entrée compact : capacités, versions, fraîcheur, contrats, règles de preuve et chemins MCP complet/compact.

NameTypeReqDescription
latestLimitinteger–Nombre de contenus récents à inclure.
NameTypeReqDescription
errorstring––

No examples provided.

get_document ~164

Lit un article ou guide l0g par slug, avec pagination opaque, troncature explicite, références et URL canonique.

NameTypeReqDescription
cursorstring–Curseur opaque nextCursor renvoyé par un appel précédent.
languagestring–Langue optionnelle : fr ou en. Une URL /en/... permet aussi de l’inférer.
lengthinteger–Longueur maximale du segment renvoyé.
limitinteger–Alias de length, recommandé pour les clients agents.
offsetinteger–Position de départ en caractères pour paginer le texte.
sectionstring–Section pratique : body avec offset, head, tail ou sources.
slugstringyesSlug de l'article ou du guide.
NameTypeReqDescription
canonicalIdstring––
errorstring––
hasMoreboolean––
language–––
lengthnumber––
limitnumber––
nextCursorstring|null––
nextOffsetnumber|null––
offsetnumber––
referencesarray––
sectionstring––
sectionFoundboolean––
slugstring––
textstring––
textCharsnumber––
titlestring––
totalCharsnumber––
totalWordsnumber––
translationStatusstring––
truncatedboolean––
typestring––
urlstring––
wordsnumber––

No examples provided.

get_evidence ~164

Interroge les claims et leurs sources, un sous-graphe de preuve ou le registre de sources avec une seule primitive compacte.

NameTypeReqDescription
articleSlugstring–Slug d’article à auditer.
claimIdstring–Identifiant exact de claim.
includeEvidenceboolean–Inclut le voisinage de preuve pour une claim unique.
kindstring–Type de claim.
languagestring–Langue du slug : fr ou en.
limitinteger–Nombre maximum d’objets.
modestring–Vue de preuve : claims, graph ou sources.
querystring–Filtre textuel sur les claims.
sourceIdstring–Source primaire ou hôte cité.
NameTypeReqDescription
errorstring––

No examples provided.

get_risk_state ~136

Produit agentique principal de l0g. Renvoie un contrat stable et sourcé pour l’état courant, le diff 1/7/30 jours, l’historique d’un instrument ou un replay Black Box point-in-time. Commencer ici pour toute question sur le risque.

NameTypeReqDescription
datestring–Date YYYY-MM-DD requise lorsque mode=replay.
instrumentstring–Instrument requis lorsque mode=history.
limitinteger–Nombre maximum d’observations ou frames.
modestring–Vue de risque demandée.
windowstring–Fenêtre de diff.
NameTypeReqDescription
asOfstring|nullyes–
errorstring––
interpretationarrayyes–
methodologystringyes–
modestringyes–
primarybooleanyes–
requestobjectyes–
sourcestringyes–

No examples provided.

search_l0g ~108

Recherche filtrée bilingue dans articles, guides, glossaire, méthodologies et sources. Renvoie des URL canoniques et des extraits bornés.

NameTypeReqDescription
languagestring–Langue optionnelle : fr ou en. Sans filtre, recherche bilingue.
limitinteger–Nombre maximum de résultats.
modestring–fulltext pour le corps des pages, catalog pour le scoring catalogue historique.
querystringyesTermes de recherche.
NameTypeReqDescription
backendstring––
countnumber––
coveragearray––
errorstring––
language–––
modestring––
querystring––
resultsarray––

No examples provided.

Install

How do I install the l0g.fr Risk Intelligence MCP server?

l0g.fr Risk Intelligence is a hosted endpoint at https://l0g.fr/api/mcp/compact, 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.

remote · l0g.fr

# add to Claude Code
claude mcp add --transport http bluetouff-l0g 'https://l0g.fr/api/mcp/compact'
Common questions

What is the l0g.fr Risk Intelligence MCP server?

l0g.fr Risk Intelligence is an MCP server listed in the public MCP registry as io.github.bluetouff/l0g. Read-only macro risk analysis, evidence, signals, and source-backed research from l0g.fr. This page covers its hosted endpoint (https://l0g.fr/api/mcp/compact).

Is the l0g.fr Risk Intelligence MCP server safe to use?

l0g.fr Risk Intelligence scores 90 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 l0g.fr Risk Intelligence MCP server expose?

l0g.fr Risk Intelligence exposes 6 tools: discover_l0g, search_l0g, get_document, get_evidence, build_research_pack, get_risk_state. Their descriptions and schemas cost roughly 755 tokens of context every time the server is loaded.

Does the l0g.fr Risk Intelligence MCP server require authentication?

No. We connected to l0g.fr Risk Intelligence without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the l0g.fr Risk Intelligence MCP server still maintained?

l0g.fr Risk Intelligence 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.