Home / MCP registry index / io.github.gpartin/waveguard
WaveGuard
io.github.gpartin/waveguard in the official MCP registry.
Endpoint https://gpartin--waveguard-api-fastapi-app.modal.run/mcp. Source: github.com/gpartin/LFMAnomalyDetection.
The registry describes it as: Anomaly detection API powered by physics simulation. Scan any data for outliers.
We read its 19 tools on 2026-10-26. Nothing in them matched our tool-poisoning rules.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
waveguard_scan waveguard_scan_timeseries waveguard_health waveguard_fingerprint waveguard_compare waveguard_token_risk waveguard_wallet_profile waveguard_volume_check waveguard_price_manipulation waveguard_market_data waveguard_counterfactual waveguard_trajectory_scan waveguard_instability waveguard_phase_coherence waveguard_interaction_matrix waveguard_cascade_risk waveguard_mechanism_probe waveguard_action_surface waveguard_multi_horizon_outlook
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-github-gpartin-waveguard)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.