Anki MCP Server vs PeppolStatus — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Anki MCP Server vs PeppolStatus
In-depth architectural comparison of the Anki MCP Server and PeppolStatus MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Anki MCP Server
Monitoring · Local stdio
Quality: 64/100 (Good) | Auth: No auth required
PeppolStatus
Monitoring · Remote HTTP/SSE
Quality: 55/100 (Good) | Auth: No auth required
Verdict Summary: Choose Anki MCP Server if you need specialized Monitoring tools running via a local process. Choose PeppolStatus if your workspace requires Monitoring integration with remote web transport. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Anki MCP Server when:
You need dedicated capabilities in the Monitoring domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Sync with AnkiWeb to pull latest data and push changes
get_due_cards
Get cards that are due for review, optionally filtered by deck (answers omitted unless `include_answer: true`, default `false`)
get_cards
Get cards with flexible filtering by state (due, new, learning, suspended, buried) and deck (answers omitted unless `include_answer: true`, default `false`)
present_card
Show a card for review with its question/front side
rate_card
Rate card performance (Again, Hard, Good, Easy) and schedule the next review
forgetCards
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Anki MCP Server is categorized under Monitoring and uses a local stdio subprocess. In contrast, PeppolStatus belongs to Monitoring using remote streaming HTTP/SSE transport. Select Anki MCP Server when you need capabilities focused on monitoring and PeppolStatus when you require tools for monitoring.
Reset cards to new, discarding their scheduling without recording a review
setDueDate
Reschedule cards to become due in N days (`"0"`, `"3-7"`, `"1!"`), without recording a review
areSuspended
Check suspension state for one or more cards without changing anything
suspend
Suspend cards so they are skipped during review until unsuspended
unsuspend
Unsuspend cards so they return to normal review
listDecks
List all decks, optionally with per-deck study-queue statistics
deckStats
Get comprehensive statistics for a single deck (study queue, true card-state counts, ease/interval distributions)
+41 more tools listed on main page
PeppolStatus Tools (51)
list_hosts
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.
get_host
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.
list_host_incidents
List a host's incidents
Incidents for one host, newest-first, cursor-paginated.
get_host_uptime
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.
list_host_software
List all hosts' software (Market)
Every host with open software fingerprint rows, one row per (hostname, role) with the vendor / version / hosting axes folded in (value, tier, first-seen; plus vendor `variant` and version `kind`). The evidence blob is omitted to keep the list lean — it stays on the per-host resource. Cursor-paginated on the stable (hostname, role) order; optional `vendor=` filter. Market tier.
get_host_software
Get a host's software fingerprint
The detected software of a host across ALL its roles: vendor, version and hosting per role, each with its confidence tier, first-seen timestamp and the structured evidence that fired. `?at=` returns point-in-time state. Market tier.
list_host_software_history
List a host's software-fingerprint history
The closed (superseded) software rows for one host, newest-first, cursor-paginated. Each row is one axis transition with its evidence. Market tier.
list_incidents
List incidents
The global incident feed, newest-first, cursor-paginated.
get_participant
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.
list_participant_events
List a participant's change events
The participant's typed change events, newest-first, cursor-paginated.
get_participant_history
List a participant's temporal history
The participant's temporal rows across the directory/card/registration/SMP fact families, newest-first, cursor-paginated.
get_participant_availability
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`).