All servers · Other
CURRENT SEA - Ambiguity Scan
io.github.Bowieboii/current-sea · v0.0.3
Measured by MCP Station
| Last check | Reachable |
|---|---|
| Checked at | — |
| Check success 7 / 30 days | — |
| First-try success 30 days | — |
| Median response | — |
| Lookups 30 days | — |
| Authentication | No auth |
| MCP version | 2025-06-18 |
| Rank score | — |
| Declared risk | Not declared (tools carry no read/destructive hints) |
| Capabilities declared | experimental, prompts, resources, tools |
| Tool definitions | 1 tools · with description 100% · input schema is an object 100% · read/destructive hints 0% |
Description written by the publisher, not verified
Explainable ambiguity signals for text. Submitted text is processed but never retained.
Connect
streamable-http · https://current-sea.fastapicloud.dev/mcp
claude mcp add --transport http current-sea https://current-sea.fastapicloud.dev/mcp{
"mcpServers": {
"current-sea": {
"url": "https://current-sea.fastapicloud.dev/mcp"
}
}
}Tools as reported by the server
scan_ambiguityFind wording that may need clarification. Use this when an agent needs an inexpensive, deterministic, explainable check for vague timing, quantities, references, commitments, or standards. The service retains invocation metadata but never the submitted text. Signals are possible issues, not proof of
JSON · Text for agents · Registry updated 2026-08-27