Skip to main content
Glama
Sirenic MCP server

Sirenic MCP server

Official

French regulator alerts (AMF)

check_french_regulator_alerts
Read-only

Screen a name against official AMF blacklists and look up PSAN or SGP registrations by name or SIREN before trusting a French investment site, crypto provider, or asset manager.

Instructions

French financial regulator (AMF) alerts and registers (scam check): screen a name against the official AMF blacklists (unauthorized investment websites, scams, AMF impersonation) and look up PSAN crypto-provider registrations and licensed asset-management companies (SGP) by name or SIREN. Use before trusting an investment site, a crypto provider or an asset manager operating in France. Official AMF open data, refreshed daily. Paid via x402 ($0.01 in USDC or EURC). When you report a result, cite its citation verbatim.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "check_french_regulator_alerts"
  }
}

Input Schema

NameRequiredDescriptionDefault
nomNoName to screen (site, brand, company), required unless siren is given
sirenNo9-digit SIREN for PSAN/SGP register lookup, required unless nom is given

Output Schema

NameRequiredDescriptionDefault
hintNoHow to settle the quote, present when payment_required is true.
quoteNoThe signable x402 payment requirements when payment_required is true: {x402Version, accepts[]} where each entry carries scheme, network, amount, asset and payTo (USDC and EURC options at the same numeric amount). Sign one entry and call again with `x_payment`.
resultatNoThe endpoint's JSON response when payment_required is false. Paid responses carry `source`, `disclaimer` and an Ed25519 signature, and every paid JSON response carries a `provenance` array (all tools since 2026-09-06): one entry per block served, with the official register, licence, version, `empreinte_sha256` (full snapshots), `as_of` date and `precision_as_of` (what that date means), plus the common per-block envelope: `etat` in a closed list (servi, absence_mesuree, absence_non_conclusive, partiel, perime, indisponible, sans_objet), `motif` when unavailable, `age_jours` (only for publication or ingestion dates), `couverture` (complete / partielle / non_mesurable with its measure) and `confiance` in bands (faible / moyenne / forte, only where a measure grounds it, never averaged across blocks). Read the states before the numbers: an absence_non_conclusive, indisponible or partiel block is never « nothing to report »; only absence_mesuree asserts an absence. Register codes: GET /v1/provenance/registres ; states, closed lists and reading rules: GET /v1/lecture (both free). The PDF tools carry no JSON envelope (the PDF report prints it).
free_tierNoFree API key offer for this tool, present with a quote.
payment_requiredYesTrue when this response is an x402 payment quote instead of data: settle one of the quote's `accepts` options and call the tool again with `x_payment`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds genuinely useful context beyond that: official AMF open data, daily refresh, x402 payment of $0.01 in USDC or EURC, and the instruction to cite the `citation` field verbatim. These are real behavioral traits, though return shape and failure modes are left to the output schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core action, then usage, then provenance, cost and citation duty. Dense but every clause carries information. The single long opening sentence is slightly heavy but not padded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be described. The description covers what an agent needs to call it correctly: the two lookup modes, the freshness of the data, the payment requirement, and the citation obligation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description adds meaning by explaining that `nom` screens a site, brand or company while `siren` targets the PSAN/SGP register, and that either may be supplied. That clarifies the either/or semantics beyond the raw schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: screen a name against AMF blacklists and look up PSAN/SGP registrations by name or SIREN. The parenthetical '(scam check)' and the enumeration of blacklist types make the purpose unmistakable and clearly distinct from the sibling company-data tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit trigger: 'Use before trusting an investment site, a crypto provider or an asset manager operating in France.' That is a clear when-to-use condition. It stops short of naming an alternative tool or stating when not to use it, so it falls just short of a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools