Skip to content

PeppolStatus MCP server

com.peppolstatus/apipeppolstatus.comstreamable-httpv1.0.0Scanned

Peppol market intelligence and network monitoring: migrations, provider churn, leads, and uptime.

65 tools: 2 change things and 63 only read.

Tools: 0 delete, 0 irreversible, 2 write, 63 read.
  • Reads private data · 2
  • Reads text others write · 0
  • Can send data out · 1
  • 5 findings

Tools listed without sign-in. Remote posture

Anlyon alternative

2 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

Its sign-in does not let Anlyon set up an OAuth client on its own, so there is no link to it here.

What the PeppolStatus MCP server can do

The PeppolStatus MCP server is published by peppolstatus.com, a domain the MCP Registry verified. It has 65 tools. It can create or change data (2 tools: get_country_churn and get_country_providers), but cannot delete data. 63 tools only read.

2 tools read private data (get_doctype_stats and get_doctype_stats_history); 1 tool can send data out of your system (get_country_churn).

The fixed checks matched 5 findings (long-description and annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 14, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

65 tools

Changes things 2Claude Code: ask
  • get_country_churnPer-country participant churn New (joiner) vs departed (leaver) participants for one country, as a daily series and an all-time monthly rollup, from the hourly churn rollup.Can send data out1 finding

    Why it is in this group

    • The name "get_country_churn" says "get": a word for reading.
    • The input takes a statement or command to run (input.code), which can change anything it can reach.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • outboundThe input takes a destination (input.to): what the tool writes goes there.

    Findings

    • Warn

      The server marks "get_country_churn" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true}; The name "get_country_churn" says "get": a word for reading.

      What this check looks for
    Description, as the server wrote it
    Per-country participant churn New (joiner) vs departed (leaver) participants for one country, as a daily series and an all-time monthly rollup, from the hourly churn rollup. A valid but unknown country returns empty arrays. Keyless-cacheable.

    Annotations the server declares

    • readOnlyHint: true
  • get_country_providersProviders serving a country The Access Points serving one country, ranked two ways from the hourly rollup: `providers` by participant (Peppol-ID) count, and `providers_by_company` …1 finding

    Why it is in this group

    • The name "get_country_providers" says "get": a word for reading.
    • The input takes a statement or command to run (input.code), which can change anything it can reach.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "get_country_providers" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true}; The name "get_country_providers" says "get": a word for reading.

      What this check looks for
    Description, as the server wrote it
    Providers serving a country The Access Points serving one country, ranked two ways from the hourly rollup: `providers` by participant (Peppol-ID) count, and `providers_by_company` by the number of DISTINCT organizations (real businesses) each serves (issue #467). Each row's `key` is the `/v1/aps/{key}` handle and `share` is that provider's fraction of the country's AP-served total for its metric. `company_coverage` (0..1) is how much ID→organization dedup the market shows — ~0 (and `providers_by_company` empty) for markets without register enrichment, meaningfully positive for BE/FR. A valid but unknown country returns empty lists. Keyless-cacheable.

    Annotations the server declares

    • readOnlyHint: true
Only reads 63Show 63 read-only tools
  • get_access_pointGet an access point One Provider's detail: display name, verified flag, member seats (each with its embedded provider or unverified cert-CN), roster size, and the country + documen…No findings

    Why it is in this group

    • The name "get_access_point" says "get": a word for reading.
    Description, as the server wrote it
    Get an access point One Provider's detail: display name, verified flag, member seats (each with its embedded provider or unverified cert-CN), roster size, and the country + document-scheme composition of its roster. A request for a STALE key (a seat since curated, so its old unverified key left the directory) resolves to the current Provider; the returned `key` is always the canonical current one. `software` groups the Provider's sighted hosts by registrable domain with the crawled identity of each, and `hostname_count` / `smp_hostname_count` give the true totals behind the capped `hostnames` / `smp_hostnames` samples. `smp_tenants` lists the Access Points (seats) that serve the participants on this Provider's SMP hosts — on a multi-tenant SMP most of the hosted footprint belongs to other APs — with `smp_tenant_count` / `smp_tenant_other` / `smp_tenant_no_ap` so the rows add up to `hosted_participant_count` (both come from the same rollup run); `smp_hosted_by` is the reverse: other providers' SMPs that carry this AP's participants. Each `sub_providers` bucket names its Vendor (`name`) and links to the Vendor's row (`vendor_key`). A Vendor key (`v-<slug>`) returns the Vendor detail instead and needs a Market-tier key: the Providers it connects through (`via`), its participants and Companies, the signals that back the row, and the composition of its roster. A Vendor has no Seats, no certificate and no hosts of its own.

    Annotations the server declares

    • readOnlyHint: true
  • get_access_point_churnGet an access point's churn An Access Point's joiner / mover / leaver activity over a period: a daily category series with derived net growth, period totals, and the 'won from / lo…1 finding

    Why it is in this group

    • The name "get_access_point_churn" says "get": a word for reading.

    Findings

    • Info

      The description is 2,313 characters long, over the 2,000 this check looks for.

      Matched text

      description ends: "...ll movers. A Vendor key is not changed: its counterparts have no platform fields."

      What this check looks for
    Description, as the server wrote it
    Get an access point's churn An Access Point's joiner / mover / leaver activity over a period: a daily category series with derived net growth, period totals, and the 'won from / lost to' counterpart breakdown. Joiners are first-ever serving seats (from 2026-08-02 onward, first-full-deep-sweep completion); movers change Provider (both sides resolved to the current identity); leavers deregister while served. Defaults to the trailing 30 days. A Vendor key (`v-<slug>`) returns the same shape for the Vendor, from a daily comparison of its membership. Movement is counted from `churn_since`; there is no history before it. A counterpart is a Provider or another Vendor (`kind`). `match_totals` and the `newly_matched` / `no_longer_matched` series count membership changes with no real event behind them (a signal appeared or disappeared): they are a data-quality figure, not movement, and are never in `net_growth`. For a Provider key, `counterpart_flow` gives each mover side (out, in) its top counterpart with its share and the effective number of counterparts, over the requested period. The share is null under 25 movers on that side and the effective number under 100. A Vendor key has no `counterpart_flow`. PLATFORM MOVES. A mover is a platform move when the platform that serves the participant stayed and only the certificate Seat changed: it is not a customer decision. The verdict is per DIRECTED provider pair (from → to), over all its movers since 2026-08-02, with one of two reasons (`same_host`, `sub_provider`): at least 90% of the movers whose endpoint host can be compared (5 or more, and at least 50% of all movers of the pair) kept their endpoint host, or at least 90% of 25 or more movers still carry, at the new provider, the sub-provider brand of the provider they left. It is a CURRENT judgment, computed again on every rollup cycle. For a Provider key, the movers of a platform-move pair are in `platform_won` / `platform_lost` of the counterpart and not in its `won` / `lost`; the flag is per direction (counterpart → Provider, Provider → counterpart). `totals.platform_in` / `totals.platform_out` are their sums. `totals.movers_in`, `totals.movers_out`, `net_growth` and the daily series still count all movers. A Vendor key is not changed: its counterparts have no platform fields.

    Annotations the server declares

    • readOnlyHint: true
  • get_access_point_roster_mixGet a filtered access point roster breakdown The five roster breakdowns of `GET /v1/aps/{key}` (country, entity type, NACE Rev.No findings

    Why it is in this group

    • The name "get_access_point_roster_mix" says "get": a word for reading.
    Description, as the server wrote it
    Get a filtered access point roster breakdown The five roster breakdowns of `GET /v1/aps/{key}` (country, entity type, NACE Rev. 2.1 division, size class, region) recomputed over a FILTERED slice of the roster, so a breakdown stays true while the roster is cut down. The filters are the same names and shapes as `GET /v1/participants`, scoped to this provider's seats. BOUNDED BY DESIGN. The breakdowns are computed only when the filtered slice is narrow (under an internal cap of 10,000 participants). A request that narrows on nothing, that carries a filter this endpoint cannot express (`doctype`, `transport_profile`, `q`, `host`, `sub_provider`, `postcode`, `provenance`, `vat_liable`), or whose slice is too wide answers `degraded: true` with every mix null — never a wrong number and never an error. Callers fall back to the stored whole-roster mixes on `GET /v1/aps/{key}`. Counts are sparse the same way the stored mixes are: company enrichment covers a handful of registers, so every mix except `country_mix` sums BELOW `participant_count` and the un-enriched remainder is derived from the total rather than served as a bucket. A Vendor key (`v-<slug>`) answers the same question over the Vendor's roster and needs a Market-tier key. `seat` then selects one Seat the Vendor connects through.

    Annotations the server declares

    • readOnlyHint: true
  • get_adoptionGet a country's adoption aggregates Peppol adoption for one country as one bare object: headline totals (universe, on_peppol, penetration), the single-dimension cuts (sector with a…No findings

    Why it is in this group

    • The name "get_adoption" says "get": a word for reading.
    Description, as the server wrote it
    Get a country's adoption aggregates Peppol adoption for one country as one bare object: headline totals (universe, on_peppol, penetration), the single-dimension cuts (sector with a NACE Rev. 2.1 section rollup (A–V), region, FR-only département, size class (FR and NO), BE-only province + postcode + mandate scope, legal-form family, and company age), the same categorical cuts cross-tabbed by company-age band (`cuts_by_age`), and the trend (monthly new adopters plus per-run penetration history). Region cells carry ISO 3166-2 (BE, NO, SK) / INSEE région (FR) codes and sector cells the NACE Rev. 2.1 division code, so the choropleth joins geometry with no string matching. Numerator cells below 10 matched companies are suppressed (`on_peppol`/`penetration` null, `suppressed` true); denominators are never suppressed. Cached for a day (data moves monthly).

    Annotations the server declares

    • readOnlyHint: true
  • get_anomalyGet an anomaly One anomaly by its stable content-derived key.No findings

    Why it is in this group

    • The name "get_anomaly" says "get": a word for reading.
    Description, as the server wrote it
    Get an anomaly One anomaly by its stable content-derived key.

    Annotations the server declares

    • readOnlyHint: true
  • get_compliance_statsNetwork compliance landscape The free compliance landscape (issue #692): per-country error rates — the share of a country's registered participants that break at least one publishe…No findings

    Why it is in this group

    • The name "get_compliance_stats" says "get": a word for reading.
    Description, as the server wrote it
    Network compliance landscape The free compliance landscape (issue #692): per-country error rates — the share of a country's registered participants that break at least one published Peppol rule — and the per-rule breakdown of every open finding. Counts ONLY: no participant, seat or hostname appears here; the participant-level records are `GET /v1/compliance/findings` (Network tier). Read from the pre-computed compliance rollup tables and edge-cached. Keyless-cacheable. Pass `country` to scope the whole body to one country (issue #716): the same shape, with `countries` holding that one cell, `rules` its own breakdown, each rule's `share` a share of THAT country's open findings, and the code echoed back in `country`. A country scope is how a structural national pattern is told apart from a real problem — AU and NZ, for example, break `not_in_peppol_directory` almost everywhere because A-NZ PINT participants are absent from the European Peppol Directory by design.

    Annotations the server declares

    • readOnlyHint: true
  • get_compliance_stats_historyNetwork compliance trend The network compliance picture over time: one point per UTC day the rollup ran, carrying that day's participant denominator, affected participants, error r…No findings

    Why it is in this group

    • The name "get_compliance_stats_history" says "get": a word for reading.
    Description, as the server wrote it
    Network compliance trend The network compliance picture over time: one point per UTC day the rollup ran, carrying that day's participant denominator, affected participants, error rate and open findings by grade. The series starts the day the rollup first ran. Keyless-cacheable. Pass `country` for one country's trend (issue #716) — the same series shape, restricted to that country and echoed back in `country`. The per-country series starts the day the country rollup first ran, which is later than the network one.

    Annotations the server declares

    • readOnlyHint: true
  • get_deregistered_company_statsGet the company breakdown of the De-registered IDs Who left: the De-registered IDs of `/v1/stats/deregistered` (same population, same daily rollup, same `deregistered` total) by co…No findings

    Why it is in this group

    • The name "get_deregistered_company_stats" says "get": a word for reading.
    Description, as the server wrote it
    Get the company breakdown of the De-registered IDs Who left: the De-registered IDs of `/v1/stats/deregistered` (same population, same daily rollup, same `deregistered` total) by company profile, register status, lifetime, re-activation and leftovers. `entity_type`, `sector`, `size` and `region` come from the company register (BE, FR, NO, SE, FI and SI only) and cover the `enriched` IDs: the cells of each of the four add up to `enriched`, with the key `unknown` for an enriched ID that has no value in that breakdown. Each cell carries `base`, the registered IDs in the same cell, so the two mixes can be compared. `company_status` is the status of the company in its register now: `active` (still in business, gone from Peppol), `ceased`, or `unmatched` (no register match). `lifetime` is the time from the join date to the de-registration; `unknown` holds the IDs with no usable join date or a leave before 2026-08-02. `leftovers` counts the De-registered IDs that still have a Peppol Directory entry (`directory_card`). `reactivation` is the share of the IDs de-registered since 2026-08-02 that are registered again. A count below 10 is withheld (`count: null`, `suppressed: true`), and so is a cell with a registered base from 1 to 9 (`base: null` too). When one cell alone of a breakdown is withheld, the next-smallest cell is withheld with it, so that it cannot be had back by subtraction (not for `leftovers`, which is part of no total). Counts only: no company and no natural person is named.

    Annotations the server declares

    • readOnlyHint: true
  • get_deregistered_statsGet the De-registered overview The participants that left the network.No findings

    Why it is in this group

    • The name "get_deregistered_stats" says "get": a word for reading.
    Description, as the server wrote it
    Get the De-registered overview The participants that left the network. A De-registered ID is a participant that is not registered now AND has at least one closed registration row. An ID that was never observed registered (not scanned yet, or never in the SML) is not de-registered: it is counted apart in `never_registered` and is in no other number here. `leavers` is the sub-count of the De-registered IDs that left while a Provider served them. `deregistered`, `share_pct` and `countries` are the stock of the daily rollup (`as_of`). `flow` and `weekly` are the leave flow from the network growth series of `/v1/network/stats`, to the last complete UTC day: `flow.d7` and `flow.d30` are the same counts as `leavers.last_7d` and `leavers.last_30d` there. A day with no completed change scan is a gap: its de-registrations are counted on the next scanned day, so a period sums all its days and `gap_days` only marks it. A period or a week of gap days only has `leavers: null` — a gap is never 0. Joiners do not depend on the change scan, so a gap day keeps them. `annualized_leave_rate_pct` is the Leaver rate (annualized), the same figure as `leavers.annualized_pct` of `/v1/network/stats`: the 30-day leavers as a percentage of the registered participants at the start of the period, × 365 / the days of the period. Leave dates are reliable from 2026-08-02 (`reliable_from`); a period that would open earlier is clamped to it, and the weekly trend starts there. The event date of a de-registration is about 3 days after the true leave (3 consecutive scans without the ID). Free. The company breakdown of the same population is `/v1/stats/deregistered/companies` (Market).

    Annotations the server declares

    • readOnlyHint: true
  • get_doctype_familyDoctypes within a family The concrete document types within one family (issue #647): each doctype's local name, version, participant count, and share of the family.No findings

    Why it is in this group

    • The name "get_doctype_family" says "get": a word for reading.
    Description, as the server wrote it
    Doctypes within a family The concrete document types within one family (issue #647): each doctype's local name, version, participant count, and share of the family. An unknown family returns an empty `doctypes` array. Keyless-cacheable.

    Annotations the server declares

    • readOnlyHint: true
  • get_doctype_family_countriesA family's receivers by country One document family's receiving participants sliced by ISO-3166 alpha-2 country (issue #652), each with its share of the family total.No findings

    Why it is in this group

    • The name "get_doctype_family_countries" says "get": a word for reading.
    Description, as the server wrote it
    A family's receivers by country One document family's receiving participants sliced by ISO-3166 alpha-2 country (issue #652), each with its share of the family total. The country is derived from the participant identifier's ICD; unresolved identifiers bucket as `ZZ`. An unknown family returns an empty `countries` array. Keyless-cacheable.

    Annotations the server declares

    • readOnlyHint: true
  • get_doctype_family_providersA family's receivers by provider One document family's receiving participants sliced by hosting provider (issue #652), attributed via the SMP-hosted footprint (the participant's cu…No findings

    Why it is in this group

    • The name "get_doctype_family_providers" says "get": a word for reading.
    Description, as the server wrote it
    A family's receivers by provider One document family's receiving participants sliced by hosting provider (issue #652), attributed via the SMP-hosted footprint (the participant's current SMP host mapped to a provider), each with its share of the family total. Participants whose SMP host maps to no known provider are omitted. An unknown family returns an empty `providers` array. Keyless-cacheable.

    Annotations the server declares

    • readOnlyHint: true
  • get_doctype_statsDocument-type landscape The free document-type landscape (issue #647): per-family participant share (Invoice, Order, Credit Note, …), the wildcard-doctype bucket, and the participa…Reads private dataNo findings

    Why it is in this group

    • The name "get_doctype_stats" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "document": it reads documents.
    Description, as the server wrote it
    Document-type landscape The free document-type landscape (issue #647): per-family participant share (Invoice, Order, Credit Note, …), the wildcard-doctype bucket, and the participant denominator. Read from the pre-computed doctype rollup tables and edge-cached. Keyless-cacheable.

    Annotations the server declares

    • readOnlyHint: true
  • get_doctype_stats_historyDocument-type landscape history The document-type landscape over time: per UTC day, the participant count for each family, from the doctype history rollup.Reads private dataNo findings

    Why it is in this group

    • The name "get_doctype_stats_history" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "document": it reads documents.
    Description, as the server wrote it
    Document-type landscape history The document-type landscape over time: per UTC day, the participant count for each family, from the doctype history rollup. Keyless-cacheable.

    Annotations the server declares

    • readOnlyHint: true
  • get_hostGet a host's current state Current role, verdict, network attribution (IPs/PTR), TLS certificate and operating provider for a host.No findings

    Why it is in this group

    • The name "get_host" says "get": a word for reading.
    Description, as the server wrote it
    Get a host's current state Current role, verdict, network attribution (IPs/PTR), TLS certificate and operating provider for a host. `?at=` returns point-in-time state. `profile` carries the crawled software identity of the host's registrable domain when one is publishable (curated, or extraction confidence 0.8+ — then unverified).

    Annotations the server declares

    • readOnlyHint: true
  • get_host_uptimeGet a host's uptime aggregates The aggregate ladder for a host at a chosen resolution, per-location plus the `__all__` rollup, optionally windowed by `[from, to)`, cursor-paginated…No findings

    Why it is in this group

    • The name "get_host_uptime" says "get": a word for reading.
    Description, as the server wrote it
    Get a host's uptime aggregates The aggregate ladder for a host at a chosen resolution, per-location plus the `__all__` rollup, optionally windowed by `[from, to)`, cursor-paginated.

    Annotations the server declares

    • readOnlyHint: true
  • get_id_qualityPeppol ID quality summary Per-scheme (ICD) summary of the structural identifier checks: how many participants were checked, how many failed their scheme's rule, and the resulting v…No findings

    Why it is in this group

    • The name "get_id_quality" says "get": a word for reading.
    Description, as the server wrote it
    Peppol ID quality summary Per-scheme (ICD) summary of the structural identifier checks: how many participants were checked, how many failed their scheme's rule, and the resulting violation rate. Ordered by violation count, busiest first.

    Annotations the server declares

    • readOnlyHint: true
  • get_id_quality_hostingHosting rollup for malformed identifiers Which Access Points and SMPs serve the malformed identifiers, honouring the same `scheme`/`reason`/`q` filters as the malformed list.No findings

    Why it is in this group

    • The name "get_id_quality_hosting" says "get": a word for reading.
    Description, as the server wrote it
    Hosting rollup for malformed identifiers Which Access Points and SMPs serve the malformed identifiers, honouring the same `scheme`/`reason`/`q` filters as the malformed list. Access points and SMPs are ranked by malformed-id count; `totals` covers the filtered set.

    Annotations the server declares

    • readOnlyHint: true
  • get_network_historyGet the network verdict history The host verdict mix over time, derived from the temporal verdict table in one windowed pass: per UTC day, the rows open at 00:00 that day, counted …No findings

    Why it is in this group

    • The name "get_network_history" says "get": a word for reading.
    Description, as the server wrote it
    Get the network verdict history The host verdict mix over time, derived from the temporal verdict table in one windowed pass: per UTC day, the rows open at 00:00 that day, counted by verdict. Two caveats. Counts are (hostname, role) pairs — a host serving two roles counts twice, the same grain as `/v1/network`. And before 2026-08-15 an unresolvable host was recorded as `down`, so `unresolvable` reads 0 over the earlier stretch. The series starts 2026-07-21, the first day the table covers; an earlier `from` is clamped to it. Keyless-cacheable.

    Annotations the server declares

    • readOnlyHint: true
  • get_network_statsGet the network-level statistics How the whole network moves: Movers (AP) and Movers (SMP), Cross-border moves, Bulk moves, Joiners, Leavers and Net growth, the Leaver rate (annual…No findings

    Why it is in this group

    • The name "get_network_stats" says "get": a word for reading.
    Description, as the server wrote it
    Get the network-level statistics How the whole network moves: Movers (AP) and Movers (SMP), Cross-border moves, Bulk moves, Joiners, Leavers and Net growth, the Leaver rate (annualized), Concentration (AP) and Concentration (SMP) (HHI, top 5, top 10), Concentration per country, Foreign-served participants and penetration. Each flow statistic gives its count over the last 7 and 30 days, the 7-day mean and the change against the period before. Every rate is of the registered-participant count at the START of its period (`base`, the end of `base_day`) and is returned beside its absolute count. A day with no completed change scan is a gap: `gap_days` counts them, and moves found after a gap are counted on the next scan day. A 7-day mean is the mean over the scanned days of its window; a gap day is in neither the sum nor the divisor, and a window of gap days only has no mean (null). The series starts 2026-08-02; a window that would open earlier is clamped to it. `as_of` is the last complete UTC day and every flow period ends there. Concentration, Foreign-served participants and penetration are snapshots: each is the latest stored value and carries its own `day`, which can be one day after `as_of`. `concentration_by_country` gives, per country, how the Peppol IDs of that country are shared over the providers that serve it: the HHI, the effective number of providers (10000 / HHI), the largest provider with its share, the top-4 and top-10 shares and the number of providers above 1%. The basis is the provider rosters (certificate seats); Vendors are not counted. Only a country with 8 or more providers is returned. The headline numbers are free. The organic/bulk split, the cross-border split, the bulk share, penetration and the 30-day trends are returned for a Market key only (see `x-required-tier` on the fields); the body is private to the caller.

    Annotations the server declares

    • readOnlyHint: true
  • get_network_stats_historyGet one network-level statistic as a daily series One point for every UTC day of the window.No findings

    Why it is in this group

    • The name "get_network_stats_history" says "get": a word for reading.
    Description, as the server wrote it
    Get one network-level statistic as a daily series One point for every UTC day of the window. `stat` is required. A flow statistic (`ap_switching` = Movers (AP), `cross_border` = Cross-border moves, `smp_switching` = Movers (SMP), `growth` = Net growth with Joiners and Leavers) carries per day its counts (`values`), the registered-participant count at the start of the day (`base`), the first key as a percentage of that base (`pct`) and its 7-day mean (`mean_7d`). For `cross_border`, `base` is all AP moves of the day and `pct` is the cross-border share of them. A day with no completed change scan has `gap: true` and `values: null` — a gap is never 0. The 7-day mean is the mean over the scanned days of `day − 6 .. day`: a gap day is in neither the sum nor the divisor, and the mean is null when all are gaps. It is the same figure as `trend_30d` of `/v1/network/stats`. For `growth`, a gap day keeps `joiners` and nulls `leavers` and `net`. A stock statistic (`concentration_ap` = Concentration (AP), `concentration_ap_country` = Concentration per country, `concentration_smp` = Concentration (SMP), `foreign_served` = Foreign-served participants, `penetration`) carries `values`, null on a day with no snapshot; `foreign_served` also carries `base`, the registered participants of that day. `concentration_ap`, `concentration_ap_country`, `foreign_served` and `penetration` have no history before their first snapshot. A day with no snapshot is absent, not 0. The series starts 2026-08-02.

    Annotations the server declares

    • readOnlyHint: true
  • get_network_summaryGet the network summary Current host verdict counts, open incidents and anomalies in the last 24h, plus how fresh the Peppol Directory export behind every other endpoint is.No findings

    Why it is in this group

    • The name "get_network_summary" says "get": a word for reading.
    Description, as the server wrote it
    Get the network summary Current host verdict counts, open incidents and anomalies in the last 24h, plus how fresh the Peppol Directory export behind every other endpoint is.

    Annotations the server declares

    • readOnlyHint: true
  • get_participantGet a participant's current state Directory presence, SML registration + current SMP, business card, the company-register enrichment block, endpoints and serving seats for a Peppol…No findings

    Why it is in this group

    • The name "get_participant" says "get": a word for reading.
    Description, as the server wrote it
    Get a participant's current state Directory presence, SML registration + current SMP, business card, the company-register enrichment block, endpoints and serving seats for a Peppol participant. Discovered participants carry no card; unmatched participants carry company: null.

    Annotations the server declares

    • readOnlyHint: true
  • get_participant_availabilityGet a participant's measured availability The real, probe-measured reachability of one Peppol ID over time.No findings

    Why it is in this group

    • The name "get_participant_availability" says "get": a word for reading.
    Description, as the server wrote it
    Get a participant's measured availability The real, probe-measured reachability of one Peppol ID over time. Two lanes — the participant's SMP host (discovery) and its Access Point host(s) (delivery) — are read from the uptime ladder and merged per bucket into one verdict (available | degraded | unreachable | no_data): an AP with any down check is unreachable; an AP up/degraded with the SMP down is degraded (discovery impaired, still deliverable); both lanes up is available. Returns per-lane `UptimeBucket` ladders, the worst-of combined lane, 30/90-day + full headline uptime (degraded counts as available), a monthly 99.5% Peppol AP service-level TARGET (never a contractual claim), host-change markers and window-overlapping incidents. `daily` spans the full history; `hourly` covers the last 90 days. Buckets before the 2026-08-02 AP epoch carry partial AP attribution (`pre_epoch`).

    Annotations the server declares

    • readOnlyHint: true
  • get_participant_historyList a participant's temporal history The participant's temporal rows across the directory/card/registration/SMP fact families, newest-first, cursor-paginated.No findings

    Why it is in this group

    • The name "get_participant_history" says "get": a word for reading.
    Description, as the server wrote it
    List a participant's temporal history The participant's temporal rows across the directory/card/registration/SMP fact families, newest-first, cursor-paginated.

    Annotations the server declares

    • readOnlyHint: true
  • get_participant_joinersNetwork joiners curve The real onboarding curve (issue #222): joiner counts bucketed by derived network join date (business-card RegistrationDate, else genuine first-seen), with a …No findings

    Why it is in this group

    • The name "get_participant_joiners" says "get": a word for reading.
    Description, as the server wrote it
    Network joiners curve The real onboarding curve (issue #222): joiner counts bucketed by derived network join date (business-card RegistrationDate, else genuine first-seen), with a whole-network coverage split (registration_date / first_seen / unknown). The unknown/seed tail is reported in `coverage` only, never folded into a bucket. Keyless-cacheable.

    Annotations the server declares

    • readOnlyHint: true
  • get_participant_statsParticipant facet stats Global participant facet counts (per country/scheme/smp/ap/doctype/transport_profile, registered share, provenance split) plus an estimated total, from the …No findings

    Why it is in this group

    • The name "get_participant_stats" says "get": a word for reading.
    Description, as the server wrote it
    Participant facet stats Global participant facet counts (per country/scheme/smp/ap/doctype/transport_profile, registered share, provenance split) plus an estimated total, from the hourly rollup. `total_count` counts every ID ever registered; `registered_count` and the `country_registered` facet scope the same data to the LIVE (registered) IDs (issue #818). Keyless-cacheable — safe for the marketing site to hit directly.

    Annotations the server declares

    • readOnlyHint: true
  • get_participant_stats_historyParticipant facet history A daily time series over one participant facet dimension (adoption curves / QoQ trends), from daily snapshots of the rollup.No findings

    Why it is in this group

    • The name "get_participant_stats_history" says "get": a word for reading.
    Description, as the server wrote it
    Participant facet history A daily time series over one participant facet dimension (adoption curves / QoQ trends), from daily snapshots of the rollup. History accrues from the day the feature shipped. Keyless-cacheable.

    Annotations the server declares

    • readOnlyHint: true
  • get_participants_mixGet a filtered participant breakdown The participant set broken down by country, entity type, NACE Rev.No findings

    Why it is in this group

    • The name "get_participants_mix" says "get": a word for reading.
    Description, as the server wrote it
    Get a filtered participant breakdown The participant set broken down by country, entity type, NACE Rev. 2.1 division, size class, region and serving Access Point, over a FILTERED slice — so a breakdown stays true while the list is cut down. The filters are the same names and shapes as `GET /v1/participants`. TWO SOURCES, one shape, named by `source`. A request that narrows on NOTHING is answered from the hourly rollup (`source: "rollup"`, with `refreshed_at`) — the whole-network breakdown, no scan. A request that narrows is computed live (`source: "slice"`). BOUNDED BY DESIGN. A live slice is computed only while it is narrow (under an internal cap of 10,000 participants). A slice wider than the cap, or a request carrying a filter this endpoint cannot express (`doctype`, `transport_profile`, `q`, `host`, `sub_provider`), answers `degraded: true` with every mix null — never a wrong number and never an error. Callers fall back to the whole-network breakdown on `GET /v1/stats/participants`. Counts are sparse the same way the rollup facets are: company enrichment covers a handful of registers, so every mix except `country_mix` sums BELOW `participant_count` and the un-enriched remainder is derived from the total rather than served as a bucket. `ap_mix` names the busiest Access Point Seats and folds the rest into one `__other__` bucket.

    Annotations the server declares

    • readOnlyHint: true
  • get_providerGet a curated provider A curated provider navigable to its seats and each seat's observed hosts.No findings

    Why it is in this group

    • The name "get_provider" says "get": a word for reading.
    Description, as the server wrote it
    Get a curated provider A curated provider navigable to its seats and each seat's observed hosts.

    Annotations the server declares

    • readOnlyHint: true
  • get_provider_movesGet moves between providers The from→to matrix of participants that changed Access Point provider in a trailing window: who lost participants to whom, for the whole network or for …1 finding

    Why it is in this group

    • The name "get_provider_moves" says "get": a word for reading.

    Findings

    • Info

      The description is 2,713 characters long, over the 2,000 this check looks for.

      Matched text

      description ends: "...movers of the window that have a country. This share includes the platform moves."

      What this check looks for
    Description, as the server wrote it
    Get moves between providers The from→to matrix of participants that changed Access Point provider in a trailing window: who lost participants to whom, for the whole network or for one country (`country`), in one call. The `top` largest providers on each side keep their identity (`from` = sources, `to` = destinations; a provider can be on both). Every other provider folds into one "Other" node per side, and `other` gives the number of folded providers and their participants. `pairs` is the COMPLETE folded matrix, largest first: a `null` `from` or `to` is the "Other" node of that side, zero cells are omitted, and the values sum to `total` exactly. A node's `value` is all its moves in the window, also the moves to or from a folded provider. A move inside one provider (between two of its own Access Points) is not counted. Every day is the PROBE-OBSERVATION day — when the change scan saw the SMP record change — not the day a migration was executed. A window with no moves returns `total: 0` and empty lists. PLATFORM MOVES. A mover is a platform move when the platform that serves the participant stayed and only the certificate Seat changed: it is not a customer decision. The verdict is per DIRECTED provider pair (from → to), over all its movers since 2026-08-02, with one of two reasons (`same_host`, `sub_provider`): at least 90% of the movers whose endpoint host can be compared (5 or more, and at least 50% of all movers of the pair) kept their endpoint host, or at least 90% of 25 or more movers still carry, at the new provider, the sub-provider brand of the provider they left. It is a CURRENT judgment, computed again on every rollup cycle. The movers of a platform-move pair are in no node, in no cell and not in `total`: `platform` gives their number and the number of directed provider pairs they come from. The matrix has Providers only; a Vendor is not in it. With `country`, the matrix holds the moves of the participants of that country: card country first, the country of the ICD prefix as fallback. The window is then one day longer (`from` = today − `days`), the same days as the `country_*_{7,30,90}d` fields of `GET /v1/aps?country=`. `platform_by_provider` gives the platform moves of EVERY provider of that country (not limited by `top`): what a net-growth chart takes out of a provider's movers to show its organic net. A move with no attributable country is dropped, so the countries do not add up to the network. A platform move is judged per provider pair across the whole network, not per country. `country_share` gives the movers of one country (the `country` param, else FR) among all movers of the window that have a country. This share includes the platform moves.

    Annotations the server declares

    • readOnlyHint: true
  • get_provider_roster_spreadGet the provider roster-size spread per country How Access Point provider roster sizes are spread in each country, in one call.No findings

    Why it is in this group

    • The name "get_provider_roster_spread" says "get": a word for reading.
    Description, as the server wrote it
    Get the provider roster-size spread per country How Access Point provider roster sizes are spread in each country, in one call. A roster size is the number of participant IDs one provider serves in the country (`country_roster` of `GET /v1/aps?country=`). Each country row is the five-number summary over the providers with at least one participant there: `n` providers, `min`, `q1`, `median`, `q3`, `max`, and `total` (the sum). Quantiles use linear interpolation between the two closest ranks (type 7), rounded to 2 decimals. `points` is every roster size in ascending order when the country has fewer than `points_max` providers, and null at or above it. The response carries sizes only, no provider key or name. Countries are ordered by median, largest first. A summary of a country with few providers says little: the console does not draw a country with fewer than 8.

    Annotations the server declares

    • readOnlyHint: true
  • get_provider_slaList provider SLA scorecards Per-provider SLA scorecards for one trailing period: checks-weighted uptime across each provider's mapped hosts, incident count, total downtime minutes…No findings

    Why it is in this group

    • The name "get_provider_sla" says "get": a word for reading.
    Description, as the server wrote it
    List provider SLA scorecards Per-provider SLA scorecards for one trailing period: checks-weighted uptime across each provider's mapped hosts, incident count, total downtime minutes and the single worst host. Ordered worst uptime first (providers with no checks in the window last). Materialized hourly by the batch runner. Not paginated (the envelope's `next_cursor` is always null).

    Annotations the server declares

    • readOnlyHint: true
  • get_provider_sla_by_keyGet a provider's SLA scorecards One provider's SLA scorecards, one per trailing period (30d and 90d).No findings

    Why it is in this group

    • The name "get_provider_sla_by_key" says "get": a word for reading.
    Description, as the server wrote it
    Get a provider's SLA scorecards One provider's SLA scorecards, one per trailing period (30d and 90d). `key` is the provider's natural key (as reported by `GET /v1/providers`). Empty `items` when the provider has no SLA data yet.

    Annotations the server declares

    • readOnlyHint: true
  • get_public_providerGet a public provider profile The FREE, crawlable public subset for one curated provider (same shape as a `GET /v1/providers/public` item).No findings

    Why it is in this group

    • The name "get_public_provider" says "get": a word for reading.
    Description, as the server wrote it
    Get a public provider profile The FREE, crawlable public subset for one curated provider (same shape as a `GET /v1/providers/public` item). Reachable with no API key.

    Annotations the server declares

    • readOnlyHint: true
  • get_seatGet a seat A Peppol certificate seat: its embedded provider (verified mapping or unverified cert-CN fallback) and the hosts it was observed operating.No findings

    Why it is in this group

    • The name "get_seat" says "get": a word for reading.
    Description, as the server wrote it
    Get a seat A Peppol certificate seat: its embedded provider (verified mapping or unverified cert-CN fallback) and the hosts it was observed operating.

    Annotations the server declares

    • readOnlyHint: true
  • get_seat_complianceGet a seat's compliance scorecard One seat's compliance posture: the registrations under it, its OPEN findings broken down by rule, the daily trend, and where the seat sits against…No findings

    Why it is in this group

    • The name "get_seat_compliance" says "get": a word for reading.
    Description, as the server wrote it
    Get a seat's compliance scorecard One seat's compliance posture: the registrations under it, its OPEN findings broken down by rule, the daily trend, and where the seat sits against the network. This is what a Peppol Authority's periodic scan reports, from the same published rules (`GET /v1/compliance/rules`), before the letter arrives. Rates are open findings per 1,000 registrations, and `null` when the seat hosts no registrations. The network median and 90th percentile are taken over every seat that hosts registrations — a seat with no finding of a rule counts as 0 — so they describe the whole network, not only the seats that break the rule. Read from a daily rollup: `snapshot_date` is the day it describes, and is `null` (with zero counts and empty lists) for a seat no scan has covered yet.

    Annotations the server declares

    • readOnlyHint: true
  • get_seat_slaGet a seat's SLA scorecards One seat's SLA scorecards, one per trailing period (30d and 90d).No findings

    Why it is in this group

    • The name "get_seat_sla" says "get": a word for reading.
    Description, as the server wrote it
    Get a seat's SLA scorecards One seat's SLA scorecards, one per trailing period (30d and 90d). `seatId` is the seat identifier (as reported by `GET /v1/aps/{key}` on `seats[].seat_id`). Empty `items` when the seat has no SLA data yet.

    Annotations the server declares

    • readOnlyHint: true
  • get_sml_statusGet SML/SMK zone status One entry per monitored zone: quorum verdict, per-location canary breakdown, DNAME cutover state, management-host TLS snapshot and zone incidents.No findings

    Why it is in this group

    • The name "get_sml_status" says "get": a word for reading.
    Description, as the server wrote it
    Get SML/SMK zone status One entry per monitored zone: quorum verdict, per-location canary breakdown, DNAME cutover state, management-host TLS snapshot and zone incidents.

    Annotations the server declares

    • readOnlyHint: true
  • get_softwareGet one software product (Market) One engine of the software library: the same row the list returns (product metadata, host count per observed role, first/last seen, the compliance…No findings

    Why it is in this group

    • The name "get_software" says "get": a word for reading.
    Description, as the server wrote it
    Get one software product (Market) One engine of the software library: the same row the list returns (product metadata, host count per observed role, first/last seen, the compliance signal and the host-count trend) plus the catalogue version and generation stamp. `engine` is a catalogue engine slug as published in `engine` on the list; an unknown slug is a 404. Beyond the list row it also returns `advisory_list[]` (issue #798): every live advisory of the engine's lanes with its id, normalized severity, CVSS score, summary, url and publication stamp, newest first. Null when no lane of the engine has an advisory feed; `[]` when it has one and upstream has published nothing. Market tier.

    Annotations the server declares

    • readOnlyHint: true
  • get_software_statsSoftware landscape The free host-software landscape (issue #490): k-anonymised vendor share (k=5, the sub-k tail folded into `other`), version distribution within each named vendor…No findings

    Why it is in this group

    • The name "get_software_stats" says "get": a word for reading.
    Description, as the server wrote it
    Software landscape The free host-software landscape (issue #490): k-anonymised vendor share (k=5, the sub-k tail folded into `other`), version distribution within each named vendor (k=10), ASN hosting share, and a two-denominator coverage block (host-weighted ~90% and participant-weighted ~50%, each named, no bare coverage scalar). Computed live from the temporal software table and edge-cached. Names no operator. Keyless-cacheable.

    Annotations the server declares

    • readOnlyHint: true
  • get_software_stats_historySoftware landscape history The software landscape over time, derived from the temporal software table in one windowed pass: per UTC day, the host-weighted identified/total targets …No findings

    Why it is in this group

    • The name "get_software_stats_history" says "get": a word for reading.
    Description, as the server wrote it
    Software landscape history The software landscape over time, derived from the temporal software table in one windowed pass: per UTC day, the host-weighted identified/total targets and the k-anonymised vendor shares. Keyless-cacheable.

    Annotations the server declares

    • readOnlyHint: true
  • get_summaryGet the public dashboard summary The free marketing-dashboard rollup: the network-wide host rollup (fleet count + mean uptime/latency), the hourly fleet-average p50 latency trend o…No findings

    Why it is in this group

    • The name "get_summary" says "get": a word for reading.
    Description, as the server wrote it
    Get the public dashboard summary The free marketing-dashboard rollup: the network-wide host rollup (fleet count + mean uptime/latency), the hourly fleet-average p50 latency trend over the last 24h, and the top-10 providers by market share (0..1 fraction). No host list, full registry or arbitrary per-host uptime is exposed.

    Annotations the server declares

    • readOnlyHint: true
  • list_access_point_churn_participantsList participants behind a churn category The drill-down: the participant IDs behind one churn category count for this Provider over the period, newest observation day first.No findings

    Why it is in this group

    • The name "list_access_point_churn_participants" says "list": a word for reading.
    Description, as the server wrote it
    List participants behind a churn category The drill-down: the participant IDs behind one churn category count for this Provider over the period, newest observation day first. `counterpart` narrows a mover category to the participants won from or lost to one Provider. Cursor-paginated in pages of at most 500: follow `next_cursor` until it is null. A Vendor key (`v-<slug>`) lists the Vendor's events, also accepts `newly_matched` and `no_longer_matched`, and adds `counterpart_kind` to each item. `category` takes a comma list, or `net` for the four net-growth categories: the items come in the order joiner, mover_in, mover_out, leaver (then newly_matched, no_longer_matched), each category newest day first, and every item names its `category`. `day` is the short form of `from` = `to` = that day. The counts are of participant IDs, not companies: group on `company_key` to count companies.

    Annotations the server declares

    • readOnlyHint: true
  • list_access_pointsList access points The Access Point directory: every Provider in its serving role, with its member seats and roster size (current participant count), busiest first.No findings

    Why it is in this group

    • The name "list_access_points" says "list": a word for reading.
    Description, as the server wrote it
    List access points The Access Point directory: every Provider in its serving role, with its member seats and roster size (current participant count), busiest first. A Provider is resolved from each seat with the precedence curated mapping (verified) → exact signing-cert `O=` string (unverified) → bare SeatID. Not paginated (the envelope's `next_cursor` is always null). Pass `?country=CC` to compare providers within one market instead of network-wide. Every item carries the windowed net growth; a MARKET-tier key additionally gets the four churn components behind each net (`joiners`, `movers_in`, `movers_out`, `leavers` × 7d/30d/90d), which a lower-tier key simply does not receive. `kind` selects the row kinds. The default is `provider`, and the list is then Provider rows only. A Vendor is a curated software or service brand that connects its customers through the Seats of one or more Providers; `kind=vendor` returns the Vendor rows and `kind=all` returns both, each item marked by `kind`. A Vendor's participants are always also in the count of the Provider that serves them: never add Provider rows and Vendor rows into one total, share or rank.

    Annotations the server declares

    • readOnlyHint: true
  • list_anomaliesList anomalies The anomaly feed, newest-first, cursor-paginated.No findings

    Why it is in this group

    • The name "list_anomalies" says "list": a word for reading.
    Description, as the server wrote it
    List anomalies The anomaly feed, newest-first, cursor-paginated.

    Annotations the server declares

    • readOnlyHint: true
  • list_cohort_move_participantsList participants in a bulk AP migration The drill-down: the participant IDs behind one cohort, oldest observation day first.No findings

    Why it is in this group

    • The name "list_cohort_move_participants" says "list": a word for reading.
    Description, as the server wrote it
    List participants in a bulk AP migration The drill-down: the participant IDs behind one cohort, oldest observation day first. A cohort's membership is DEFINED as the mover events its provider pair and day range select, so this list is always in step with the cohort's counts. Cursor-paginated on (day, value). `id` is the request-lifetime handle from `GET /v1/stats/cohort-moves`. The detector re-clusters the trailing window on every run, so a handle whose cohort boundaries have since shifted answers 404 rather than a stale list — re-read the feed instead of persisting ids.

    Annotations the server declares

    • readOnlyHint: true
  • list_cohort_movesList bulk AP migrations Detected bulk migrations between Access Points, largest first.1 finding

    Why it is in this group

    • The name "list_cohort_moves" says "list": a word for reading.

    Findings

    • Info

      The description is 2,321 characters long, over the 2,000 this check looks for.

      Matched text

      description ends: "...is a request-lifetime handle for the participant drill-down — never persist one."

      What this check looks for
    Description, as the server wrote it
    List bulk AP migrations Detected bulk migrations between Access Points, largest first. A cohort is a gap-≤3-day island of (from_provider, to_provider) mover days that clears three thresholds: at least 25 participants, at least 40 % of them on the busiest day (which rejects a steady drip), and at most 20 active days for the pair over the trailing 40 days (which rejects a recurring partnership). Every day is the PROBE-OBSERVATION day — the day the change scan saw the SMP record change, not the day the migration was executed — so a cohort is always a `[first_day, last_day]` range and `peak_day` is the busiest observation day. Render the range, never a single date. `top_country` is derived from the ICD prefix of the participant identifiers, not from business-card country fields. `merge_suspect` marks a cohort large enough (or whose source provider no longer resolves in the directory) to be a provider merge or a renamed provider rather than that many independent customer decisions — the canonical case is Sovos → Sage, 10,574 participants. Such rows are data events, not customer decisions; verify one before quoting it. The flag is a CURRENT judgment, re-evaluated on every recompute, not frozen at detection. PLATFORM MOVES. A mover is a platform move when the platform that serves the participant stayed and only the certificate Seat changed: it is not a customer decision. The verdict is per DIRECTED provider pair (from → to), over all its movers since 2026-08-02, with one of two reasons (`same_host`, `sub_provider`): at least 90% of the movers whose endpoint host can be compared (5 or more, and at least 50% of all movers of the pair) kept their endpoint host, or at least 90% of 25 or more movers still carry, at the new provider, the sub-provider brand of the provider they left. It is a CURRENT judgment, computed again on every rollup cycle. A cohort of such a pair has `platform_move: true`. It stays in the list. A Vendor's cohorts (`provider=v-<slug>`) are not changed and have no `platform_move`. `from`/`to` are OVERLAP bounds (a cohort counts when its range intersects the window), defaulting to the trailing 90 days the detector re-clusters. Mover history begins 2026-07-24, so no cohort predates it. `id` is a request-lifetime handle for the participant drill-down — never persist one.

    Annotations the server declares

    • readOnlyHint: true
  • list_compliance_findingsList compliance findings Deterministic verdicts against the published rules, newest first and keyset-paginated on (`first_detected_at`, `finding_id`).No findings

    Why it is in this group

    • The name "list_compliance_findings" says "list": a word for reading.
    Description, as the server wrote it
    List compliance findings Deterministic verdicts against the published rules, newest first and keyset-paginated on (`first_detected_at`, `finding_id`). A finding stays `open` until the registration is corrected, at which point the next scan stamps `resolved_at`; `first_detected_at` survives every re-scan. Distinct from `/v1/anomalies`, which reports observed behaviour rather than rule breaches. The first page's `meta.facets` gives rule and grade counts over the filtered set.

    Annotations the server declares

    • readOnlyHint: true
  • list_compliance_rulesList the compliance rule catalogue The published rules registrations are judged against: what each rule requires, what it applies to, how severe a breach is, and how many findings …No findings

    Why it is in this group

    • The name "list_compliance_rules" says "list": a word for reading.
    Description, as the server wrote it
    List the compliance rule catalogue The published rules registrations are judged against: what each rule requires, what it applies to, how severe a breach is, and how many findings requires, what it applies to, and how severe a breach is. Free — the rules themselves are public; the findings against them are on `GET /v1/compliance/findings`.

    Annotations the server declares

    • readOnlyHint: true
  • list_deregistered_idsList the latest De-registered IDs The De-registered IDs of `/v1/stats/deregistered` (same population, same daily rollup) with the newest leave date: at most 1000, newest first, cur…No findings

    Why it is in this group

    • The name "list_deregistered_ids" says "list": a word for reading.
    Description, as the server wrote it
    List the latest De-registered IDs The De-registered IDs of `/v1/stats/deregistered` (same population, same daily rollup) with the newest leave date: at most 1000, newest first, cursor-paginated. Each item is a `/v1/participants` list item plus `left_at`, the close of its latest registration. `left_at` is recorded about 3 days after the true leave, and a date before 2026-08-02 is not reliable. An ID that is registered again since the rollup run is left out, so a page can be shorter than `total` says. `/v1/participants?registered=false` is a wider list: it also holds the never-registered IDs, which are not de-registered.

    Annotations the server declares

    • readOnlyHint: true
  • list_eventsList global change events Every typed change event, newest-first, cursor-paginated.No findings

    Why it is in this group

    • The name "list_events" says "list": a word for reading.
    Description, as the server wrote it
    List global change events Every typed change event, newest-first, cursor-paginated. Any anomaly an event triggered is embedded on it. `cursor` walks older events; `prev_cursor` walks the newer edge (for live polling). The first page carries a `meta` block with exact type facets + filter count and an auto-bucketed timeline chart.

    Annotations the server declares

    • readOnlyHint: true
  • list_host_incidentsList a host's incidents Incidents for one host, newest-first, cursor-paginated.No findings

    Why it is in this group

    • The name "list_host_incidents" says "list": a word for reading.
    Description, as the server wrote it
    List a host's incidents Incidents for one host, newest-first, cursor-paginated.

    Annotations the server declares

    • readOnlyHint: true
  • list_hostsList monitored hosts Every monitored host with its current verdict, latest hourly all-locations latency and 24h uptime, worst-first, plus a network-wide rollup.No findings

    Why it is in this group

    • The name "list_hosts" says "list": a word for reading.
    Description, as the server wrote it
    List monitored hosts Every monitored host with its current verdict, latest hourly all-locations latency and 24h uptime, worst-first, plus a network-wide rollup.

    Annotations the server declares

    • readOnlyHint: true
  • list_id_quality_malformedList malformed participant identifiers The individual identifiers that failed their scheme's structural rule, keyset-paginated on (scheme, value).No findings

    Why it is in this group

    • The name "list_id_quality_malformed" says "list": a word for reading.
    Description, as the server wrote it
    List malformed participant identifiers The individual identifiers that failed their scheme's structural rule, keyset-paginated on (scheme, value). The first page's `meta.facets` gives scheme and reason counts over the filtered set.

    Annotations the server declares

    • readOnlyHint: true
  • list_incidentsList incidents The global incident feed, newest-first, cursor-paginated.No findings

    Why it is in this group

    • The name "list_incidents" says "list": a word for reading.
    Description, as the server wrote it
    List incidents The global incident feed, newest-first, cursor-paginated.

    Annotations the server declares

    • readOnlyHint: true
  • list_participant_eventsList a participant's change events The participant's typed change events, newest-first, cursor-paginated.No findings

    Why it is in this group

    • The name "list_participant_events" says "list": a word for reading.
    Description, as the server wrote it
    List a participant's change events The participant's typed change events, newest-first, cursor-paginated.

    Annotations the server declares

    • readOnlyHint: true
  • list_participantsList participants The participant set, keyset-paginated.No findings

    Why it is in this group

    • The name "list_participants" says "list": a word for reading.
    Description, as the server wrote it
    List participants The participant set, keyset-paginated. Default sort is first-seen newest-first. Comma-array filters (`country`, `scheme`, `smp`, `ap`, `doctype`, `transport_profile`, `host`, `provenance`, and the company-register cuts `entity_type`, `sector`, `size`, `region`, `postcode`), the single-valued `sub_provider` cut, `registered` + `vat_liable` booleans, and a smart `q` (a full Peppol ID or a bare identifier number matches the ID; other text is a name search on the business-card name or the company-register name — see `q`). First-page `meta` carries estimated totals and rollup facets; `meta.filter_count` is a bounded exact count that degrades to null (never an error) if it exceeds the query timeout. A name search that exceeds the query timeout returns an empty first page with `meta.search_degraded`, and a 503 on a later page. Discovered participants carry no name/card fields (privacy).

    Annotations the server declares

    • readOnlyHint: true
  • list_provider_certsGet a provider's certificate posture A curated provider's whole-fleet certificate posture in one call: per-Seat cert counts, soonest expiry, expired / expiring-within-30-days count…No findings

    Why it is in this group

    • The name "list_provider_certs" says "list": a word for reading.
    Description, as the server wrote it
    Get a provider's certificate posture A curated provider's whole-fleet certificate posture in one call: per-Seat cert counts, soonest expiry, expired / expiring-within-30-days counts, observed cert organisations and last identity shift, plus the rolled-up fleet summary.

    Annotations the server declares

    • readOnlyHint: true
  • list_providersList providers The OpenPeppol member registry with role flags, country, mapped hostnames and per-provider participant counts (market share), busiest first.No findings

    Why it is in this group

    • The name "list_providers" says "list": a word for reading.
    Description, as the server wrote it
    List providers The OpenPeppol member registry with role flags, country, mapped hostnames and per-provider participant counts (market share), busiest first. Not paginated (the envelope's `next_cursor` is always null).

    Annotations the server declares

    • readOnlyHint: true
  • list_public_providersList public provider profiles The FREE, crawlable public subset for each curated provider, busiest first: identity + role flags, the seat-directory columns (legal entity, commercia…No findings

    Why it is in this group

    • The name "list_public_providers" says "list": a word for reading.
    Description, as the server wrote it
    List public provider profiles The FREE, crawlable public subset for each curated provider, busiest first: identity + role flags, the seat-directory columns (legal entity, commercial name, website, infra provider, hosting), mapped hostnames, participant count, roster country mix, the 30d/90d uptime headline, a cert-health summary and an `as_of` freshness stamp. Reachable with no API key. `limit` clamps to [1, 500] (default 100). Not paginated (the envelope's `next_cursor` is always null).

    Annotations the server declares

    • readOnlyHint: true
  • list_smpsList SMPs The SMP directory: every current SMP hostname with the seat(s) and provider that sign its metadata, busiest first.No findings

    Why it is in this group

    • The name "list_smps" says "list": a word for reading.
    Description, as the server wrote it
    List SMPs The SMP directory: every current SMP hostname with the seat(s) and provider that sign its metadata, busiest first. A hostname is listed if it currently homes participants (from the participant rollup's `smp` facet) or carries an open `smp-signing` certificate. `participant_count` comes from that bounded top-N facet, so a hostname with a signing cert but outside the top-N carries a null count (unknown), not zero. The provider is resolved from the most-recent open signing cert with the precedence curated mapping (verified) → unverified cert-CN — the same as `/v1/aps`. `provider` is who OPERATES the host; `owner` names the party the curated registry says OWNS it, and is set only when that is a different party (a shared registry SMP served under another party's cert), else null. Not paginated (the envelope's `next_cursor` is always null).

    Annotations the server declares

    • readOnlyHint: true
  • list_softwareList the software library (Market) The software catalogue's PRODUCT taxonomy joined to what the network shows: for every engine, its display name, vendor, category and homepage, th…No findings

    Why it is in this group

    • The name "list_software" says "list": a word for reading.
    Description, as the server wrote it
    List the software library (Market) The software catalogue's PRODUCT taxonomy joined to what the network shows: for every engine, its display name, vendor, category and homepage, the current host count broken down by observed role, when it was first and last seen, a compliance signal for the seats running it, and a host-count trend of up to 90 UTC days. Every catalogue engine appears, including one the network does not currently show (`hosts: 0`, a flat trend) — the library is the catalogue, not only today's sightings. `category` is the vendor's own framing; `roles` is the OBSERVED fact and is the one to trust where the two disagree. `compliance.seats_linked` is deliberately not called "owned": an engine → seat link is MANY-TO-MANY, so a seat whose hosts run two engines is counted under both and its findings appear under both. Summing `open_findings` across engines therefore OVER-COUNTS the network total; the figure answers "how much compliance debt sits behind this engine", never "who is to blame". `compliance` is null when no seat is linked to the engine, and `snapshot_date` always travels with the numbers because the daily rollup can be a day stale. `lanes[]` (issue #798) reports each tracked upstream LANE of the engine — a lane is not an engine: `oxalis` covers three independent release ladders — with its `latest_release` and the `hosts_current` / `hosts_behind` / `hosts_unknown` split of the hosts running it (all three null when any is below 10). `advisories` summarises the live advisories published for the product by CVSS severity. Both are NULL — never `[]` or zero counts — for the engines the catalogue tracks no upstream feed for. Market tier.

    Annotations the server declares

    • readOnlyHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged untrusted-input.

Reads private data2
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out1
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:44 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
2
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://mcp.peppolstatus.com/.well-known/oauth-protected-resource
Authorization servers
https://api.peppolstatus.com
Legacy HTTP+SSE transport
no
Dynamic client registration
no
Client ID metadata documents
no
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://mcp.peppolstatus.com: tools/list returned 65 tools to an anonymous client, including get_country_churn (write), get_country_providers (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

2 warn3 info
  • The server marks "get_country_churn" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true}; The name "get_country_churn" says "get": a word for reading.

    What this check looks for
  • The server marks "get_country_providers" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true}; The name "get_country_providers" says "get": a word for reading.

    What this check looks for
  • The description is 2,313 characters long, over the 2,000 this check looks for.

    Matched text

    description ends: "...ll movers. A Vendor key is not changed: its counterparts have no platform fields."

    What this check looks for
  • The description is 2,321 characters long, over the 2,000 this check looks for.

    Matched text

    description ends: "...is a request-lifetime handle for the participant drill-down — never persist one."

    What this check looks for
  • The description is 2,713 characters long, over the 2,000 this check looks for.

    Matched text

    description ends: "...movers of the window that have a country. This share includes the platform moves."

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools2 changed.~2 changedView diff

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http api https://mcp.peppolstatus.com
claude mcp add --transport http api https://mcp.peppolstatus.com

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__api__list_hosts",
      "mcp__api__get_host",
      "mcp__api__list_host_incidents",
      "mcp__api__get_host_uptime",
      "mcp__api__list_incidents",
      "mcp__api__get_participant",
      "mcp__api__list_participant_events",
      "mcp__api__get_participant_history",
      "mcp__api__get_participant_availability",
      "mcp__api__get_network_summary",
      "mcp__api__get_network_history",
      "mcp__api__get_network_stats",
      "mcp__api__get_network_stats_history",
      "mcp__api__get_summary",
      "mcp__api__get_adoption",
      "mcp__api__list_providers",
      "mcp__api__get_provider",
      "mcp__api__list_public_providers",
      "mcp__api__get_public_provider",
      "mcp__api__get_provider_sla",
      "mcp__api__get_provider_sla_by_key",
      "mcp__api__list_provider_certs",
      "mcp__api__list_access_points",
      "mcp__api__get_access_point",
      "mcp__api__get_access_point_roster_mix",
      "mcp__api__get_access_point_churn",
      "mcp__api__list_access_point_churn_participants",
      "mcp__api__list_smps",
      "mcp__api__get_seat",
      "mcp__api__get_seat_sla",
      "mcp__api__get_seat_compliance",
      "mcp__api__list_events",
      "mcp__api__list_participants",
      "mcp__api__get_participants_mix",
      "mcp__api__get_participant_stats",
      "mcp__api__get_participant_stats_history",
      "mcp__api__get_participant_joiners",
      "mcp__api__list_software",
      "mcp__api__get_software",
      "mcp__api__get_software_stats",
      "mcp__api__get_software_stats_history",
      "mcp__api__get_doctype_stats",
      "mcp__api__get_doctype_stats_history",
      "mcp__api__get_doctype_family",
      "mcp__api__get_doctype_family_countries",
      "mcp__api__get_doctype_family_providers",
      "mcp__api__get_compliance_stats",
      "mcp__api__get_compliance_stats_history",
      "mcp__api__get_deregistered_stats",
      "mcp__api__get_deregistered_company_stats",
      "mcp__api__list_deregistered_ids",
      "mcp__api__list_cohort_moves",
      "mcp__api__get_provider_moves",
      "mcp__api__get_provider_roster_spread",
      "mcp__api__list_cohort_move_participants",
      "mcp__api__list_anomalies",
      "mcp__api__get_anomaly",
      "mcp__api__get_sml_status",
      "mcp__api__get_id_quality",
      "mcp__api__list_id_quality_malformed",
      "mcp__api__get_id_quality_hosting",
      "mcp__api__list_compliance_rules",
      "mcp__api__list_compliance_findings"
    ],
    "ask": [
      "mcp__api__get_country_churn",
      "mcp__api__get_country_providers"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as api. Review it before you use it.

Capability tags behind 3 rules
  • mcp__api__get_doctype_stats private-data
  • mcp__api__get_doctype_stats_history private-data
  • mcp__api__get_country_churn outbound

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.peppolstatus/api/verify?hash=dcb63e3bd4e7cb8c62bcb07a67e185586b4e763714f12114eba56666322130b2" | jq -e '.changed == false'

Pinned hash dcb63e3bd4e7, from Nov 14, 2026, 00:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.peppolstatus/api/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.peppolstatus/api
[![Anlyon Radar](https://radar.anlyon.com/badge/com.peppolstatus/api.svg)](https://radar.anlyon.com/servers/com.peppolstatus/api)

Source: MCP Registry. Synced Oct 21, 2026, 18:00 UTC.

PeppolStatus MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the PeppolStatus MCP server safe?

No scan can promise that. What its definitions show: 65 tools, 2 of which can change, send or delete something, and 5 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the PeppolStatus MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the PeppolStatus MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the PeppolStatus MCP server have?

65 tools: 2 write, 63 read. get_country_churn, get_country_providers, list_hosts, get_host, list_host_incidents, get_host_uptime, list_incidents, get_participant and 57 more.

Does the PeppolStatus MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the PeppolStatus MCP server send data to outside services?

1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): get_country_churn.

Has the PeppolStatus MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 1, 2026. Every change is on this page and in its Atom feed.