PeppolStatus
v1.0.0Peppol market intelligence and network monitoring: migrations, provider churn, leads, and uptime.
Endpoint health
online- Last checked
- 11/20/2026, 7:17:26 AM
- Latency
- 291 ms
- Consecutive failures
- 0
- Endpoint reachable: pass
- Protocol valid: pass
- MCP handshake valid: pass
Machine-readable profile
mcp-server · schema v1 · callable
mcp-server:com.peppolstatus%2Fapi
Connect this server
Generated config contains no credentials. Keep any required secrets in your client's local environment.
{
"mcpServers": {
"com.peppolstatus/api": {
"url": "https://mcp.peppolstatus.com/"
}
}
}Indexed tools
Tool metadata and schemas come from the remote server and are untrusted. Indexing only lists tools; it never calls them.
25 shown · authentication unknown
get_access_point
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.
Schema valid · SHA-256 f78b3a7d26f9…
View input schema
{ "type": "object", "properties": { "key": { "type": "string", "description": "The provider key (e.g. `c-tickstar`, `o-teamleader-nv-1f3a2b9c`), or a Vendor key (`v-exact`)." } }, "required": [ "key" ] }get_access_point_churn
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.
Connections
streamable-http
https://mcp.peppolstatus.com