sanalert-mcp
Related Servers
Alternatives to sanalert-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceProvides integrated access to location-based weather, reporting history, and infrastructure status data for safety reporting systems. It supports both SSE and stdio protocols for flexible integration with various AI agents and clients.-
- FlicenseBqualityBmaintenanceEnables an AI assistant to read and manage a local project-management database over stdio: listing and creating projects, tasks, expenses, chats and people, and pulling money, margin, deadline and overdue summaries. It runs on the same service layer and SQLite file as the bundled web UI, so figures shown to the assistant and to the human always agree.14-

recordist-gatewayofficial
AlicenseNot gradedqualityBmaintenanceLets an AI assistant search and read the meetings recorded by Recordist on your own computer: transcripts, action items and notes. Local stdio server that talks only to the app's loopback API or its SQLite file; nothing leaves the machine.507 npmMIT- AlicenseAqualityBmaintenanceEnables AI assistants to read and modify an Acumulus administration through natural language over the official API, including invoices, picklists, and direct endpoint calls. Runs locally over stdio and supports test mode to validate writes without persisting them.4AGPL 3.0
- AlicenseAqualityBmaintenanceEnables an AI agent to run local tools on the user's own machine via stdio, including command execution, workspace file read/write, and system status checks.52MIT
- AlicenseAqualityBmaintenanceEnables AI assistants to query French public open data through read-only tools: geocoding and reverse geocoding of addresses, company lookups by name, address, leader or SIREN, and commune listings by name, postcode or département. It wraps free, keyless government APIs (IGN Géoplateforme/BAN, Recherche d'entreprises/SIRENE, geo.api.gouv.fr) over stdio or Streamable HTTP with validated inputs and rate limiting.5MIT
TDQS
Scored across 1 tool
Only one tool exists, so there is no risk of selecting the wrong tool. Its description clearly defines a single purpose: retrieving SanAlert level and related alerts for a specified place in Poland.
The single tool name sanalert_level is descriptive, uses snake_case, and aligns with the server name. With only one tool, there is no inconsistent convention to compare.
A single tool is thin for an MCP server, even though the tool itself is comprehensive. The rubric treats 1-2 tools as borderline, and there is no ability to split concerns across multiple operations.
The tool covers current level, messages, and data trust for one place, but there is no way to discover valid town names or coordinates, nor to query multiple places or historical data. This is a notable gap for an agent that does not already know the exact input.