Speeron NEXT Digital Guest Journey MCP server (remote HTTP endpoint).
Dev & Codev1.0.0streamable-httpspeeronnext-dev-chat-app.azurewebsites.net
| Criterion | Points | Observed |
|---|---|---|
| reachability | 25 / 25 | HTTP 200, initialize accepted in 671ms |
| protocol | 15 / 15 | valid JSON-RPC initialize result, protocolVersion 2025-06-18, serverInfo SpeeronNext.ChatBot.ChatBot.WebApp@1.0.26194.2 |
| tooling | 20 / 35 | tools/list OK: 4 tools e.g. "confirm_booking"; 0/4 described, 4/4 fully-typed schemas, median description 0 chars |
| latency | 7 / 10 | initialize round-trip 671ms |
| provenance | 5 / 15 | description present; no repository URL; version 1.0.0; namespace io.github.Speeron-Polska does NOT match remote host (expected *.speeron-polska.github.io) |
Score 72/100 · latency 671ms · 4 tools · auth: open
Claude Code:
claude mcp add --transport http speeron-next https://speeronnext-dev-chat-app.azurewebsites.net/mcp
Generic MCP client config:
{ "mcpServers": { "speeron-next": { "type": "http", "url": "https://speeronnext-dev-chat-app.azurewebsites.net/mcp" } } }
MCP Queen is a graded index, not a middleman — your agent connects directly to the server above. Check the grade and evidence first; that's the point.
Share this server: permalink https://mcpqueen.com/s/io.github.Speeron-Polska/speeron-next · referral link https://mcpqueen.com/go/io.github.Speeron-Polska/speeron-next (counts as “routed via the queen”).
Live badge, re-probed continuously — put it in your README:
[](https://mcpqueen.com/s/io.github.Speeron-Polska/speeron-next)
Think the grade is wrong? Fix the finding the evidence shows, then the next probe cycle picks it up automatically (full cycle ≈ 3 days) — or open a dispute via the MCP endpoint.
Email alerts when the grade changes or the endpoint stops answering. Double-opt-in, one-click unwatch, free while in beta.
| When (UTC) | Grade | Score | Latency |
|---|---|---|---|
| 2026-07-13 19:17 | C | 72 | 671ms |