list_access_point_churn_participants — PeppolStatus MCP Tool Read-only
list_access_point_churn_participants
(list access point churn participants) is one of 62 tools on the
PeppolStatus
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call list_access_point_churn_participants from your client
- Claude Code PeppolStatus list_access_point_churn_participants run in your project directory
- Claude Desktop PeppolStatus list_access_point_churn_participants ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor PeppolStatus list_access_point_churn_participants ~/.cursor/mcp.json
- VS Code PeppolStatus list_access_point_churn_participants .vscode/mcp.json
- Zed PeppolStatus list_access_point_churn_participants ~/.config/zed/settings.json
- Windsurf PeppolStatus list_access_point_churn_participants ~/.codeium/windsurf/mcp_config.json
- Cline PeppolStatus list_access_point_churn_participants ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI PeppolStatus list_access_point_churn_participants ~/.gemini/settings.json
- Grok PeppolStatus list_access_point_churn_participants .mcp.json (in your project root)
- ChatGPT PeppolStatus list_access_point_churn_participants Settings → Connectors → Advanced → Developer mode
- Claude.ai PeppolStatus list_access_point_churn_participants Settings → Connectors → Add custom connector
- LangChain PeppolStatus list_access_point_churn_participants pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http api https://mcp.peppolstatus.comOther tools on this server
- list_hosts
- get_host
- list_host_incidents
- get_host_uptime
- list_host_software
- get_host_software
- list_host_software_history
- list_incidents
- get_participant
- list_participant_events
- get_participant_history
- get_participant_availability
- get_network_summary
- get_network_history
- get_summary
- get_adoption
- list_providers
- get_provider
- list_public_providers
- get_public_provider
- get_provider_sla
- get_provider_sla_by_key
- list_provider_certs
- list_access_points
- get_access_point
- get_access_point_roster_mix
- get_access_point_churn
- list_smps
- get_seat
- get_seat_sla
- get_seat_compliance
- list_events
- list_participants
- get_participants_mix
- get_participant_stats
- get_participant_stats_history
- get_participant_joiners
- list_software
- get_software
- get_software_stats
- get_software_stats_history
- get_doctype_stats
- get_doctype_stats_history
- get_doctype_family
- get_doctype_family_countries
- get_doctype_family_providers
- get_compliance_stats
- get_compliance_stats_history
- get_country_churn
- get_country_providers
- list_cohort_moves
- list_cohort_move_participants
- list_anomalies
- list_software_anomalies
- get_anomaly
- get_sml_status
- get_id_quality
- list_id_quality_malformed
- get_id_quality_hosting
- list_compliance_rules
- list_compliance_findings
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.