io.github.Speeron-Polska/speeron-next
REMOTE · SPEERONNEXT-DEV-CHAT-APP.AZUREWEBSITES.NET · SCANNED SEP 30
Speeron NEXT Digital Guest Journey MCP server (remote HTTP endpoint).
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability34
- AI-judged instruction clarity (poor).Fail
- Tool/resource definitions use about 250 tokens (~62/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage0
- 0% of tools have a non-trivial description (not blank, and not just the tool's name).Fail
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the io.github.Speeron-Polska/speeron-next MCP server?
io.github.Speeron-Polska/speeron-next is a hosted endpoint at https://speeronnext-dev-chat-app.azurewebsites.net/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · speeronnext-dev-chat-app.azurewebsites.net
claude mcp add --transport http speeron-polska-speeron-next 'https://speeronnext-dev-chat-app.azurewebsites.net/mcp'
{
"mcpServers": {
"speeron-polska-speeron-next": {
"url": "https://speeronnext-dev-chat-app.azurewebsites.net/mcp"
}
}
} {
"servers": {
"speeron-polska-speeron-next": {
"type": "http",
"url": "https://speeronnext-dev-chat-app.azurewebsites.net/mcp"
}
}
} [mcp_servers.speeron-polska-speeron-next] url = "https://speeronnext-dev-chat-app.azurewebsites.net/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"speeron-polska-speeron-next": {
"type": "remote",
"url": "https://speeronnext-dev-chat-app.azurewebsites.net/mcp",
"enabled": true
}
}
} openclaw mcp add speeron-polska-speeron-next --url 'https://speeronnext-dev-chat-app.azurewebsites.net/mcp' --transport streamable-http
mcp_servers:
speeron-polska-speeron-next:
url: "https://speeronnext-dev-chat-app.azurewebsites.net/mcp" {
"McpServers": {
"speeron-polska-speeron-next": {
"Transport": "http",
"Url": "https://speeronnext-dev-chat-app.azurewebsites.net/mcp"
}
}
} assistant mcp add speeron-polska-speeron-next -t streamable-http -u 'https://speeronnext-dev-chat-app.azurewebsites.net/mcp'
{
"mcpServers": {
"speeron-polska-speeron-next": {
"type": "http",
"url": "https://speeronnext-dev-chat-app.azurewebsites.net/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 11 Sept 26 0
- Stability: 0.97 → pass security
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 5 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 30 Sept 2026 · Probed https://speeronnext-dev-chat-app.azurewebsites.net/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.azurewebsites.net,O=Microsoft Corporation,L=Redmond,ST=WA,C=US | CN=Microsoft TLS G2 RSA CA OCSP 16,O=Microsoft Corporation,C=US | 26 Aug 2026 | 22 Feb 2027 | RSA 2048 | SHA384-RSA | 5500b7ca2955391647f9d2f82b000000b7ca29 |
| SANs: *.azurewebsites.net, *.scm.azurewebsites.net, *.sso.azurewebsites.net, *.northeurope-01.azurewebsites.net, *.scm.northeurope-01.azurewebsites.net, *.sso.northeurope-01.azurewebsites.net, *.northeurope.c.azurewebsites.net, *.scm.northeurope.c.azurewebsites.net, *.sso.northeurope.c.azurewebsites.net, *.02.northeurope.c.azurewebsites.net, *.scm.02.northeurope.c.azurewebsites.net, *.sso.02.northeurope.c.azurewebsites.net and 18 more | ||||||
| CN=Microsoft TLS G2 RSA CA OCSP 16,O=Microsoft Corporation,C=US (CA) | CN=Microsoft TLS RSA Root G2,O=Microsoft Corporation,C=US | 1 Aug 2025 | 3 Jun 2029 | RSA 4096 | SHA384-RSA | 330000000e42938f25dc51a99b00000000000e |
| CN=Microsoft TLS RSA Root G2,O=Microsoft Corporation,C=US (CA) | CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US | 21 May 2025 | 19 Jun 2029 | RSA 4096 | SHA384-RSA | b0c6b2c466917b04773c647d4afc0c8 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of speeronnext-dev-chat-app.azurewebsites.net. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| net. | present | 37331 | 13 | Verified |
| azurewebsites.net. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://speeronnext-dev-chat-app.azurewebsites.net/mcp | Verified | 200 | |
| http (plaintext) | http://speeronnext-dev-chat-app.azurewebsites.net/mcp | HTTPS enforced | 301 | https://speeronnext-dev-chat-app.azurewebsites.net/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_in_user ~53
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| bookingId | string | yes | – |
| city | string | – | – |
| country | string | – | – |
| guestLastName | string | yes | – |
| hotelName | string | – | – |
| tenantId | string | – | – |
No output schema declared.
No examples provided.
confirm_booking ~66
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| checkInDate | string | yes | – |
| guestName | string | yes | – |
| hotelName | string | – | – |
| numberOfAdults | integer | yes | – |
| numberOfChildren | integer | – | – |
| numberOfNights | integer | yes | – |
| optionId | string | yes | – |
No output schema declared.
No examples provided.
search_room_options ~73
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| checkInDate | string | yes | – |
| city | string | yes | – |
| country | string | – | – |
| hotelName | string | yes | – |
| numberOfAdults | integer | yes | – |
| numberOfChildren | integer | – | – |
| numberOfNights | integer | yes | – |
| tenantId | string | – | – |
No output schema declared.
No examples provided.
search_rooms_by_area ~58
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| checkInDate | string | yes | – |
| city | string | yes | – |
| country | string | – | – |
| numberOfAdults | integer | yes | – |
| numberOfChildren | integer | – | – |
| numberOfNights | integer | yes | – |
No output schema declared.
No examples provided.
What is the io.github.Speeron-Polska/speeron-next MCP server?
io.github.Speeron-Polska/speeron-next is an MCP server listed in the public MCP registry as io.github.Speeron-Polska/speeron-next. Speeron NEXT Digital Guest Journey MCP server (remote HTTP endpoint). This page covers its hosted endpoint (https://speeronnext-dev-chat-app.azurewebsites.net/mcp).
Is the io.github.Speeron-Polska/speeron-next MCP server safe to use?
io.github.Speeron-Polska/speeron-next scores 61 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.Speeron-Polska/speeron-next MCP server expose?
io.github.Speeron-Polska/speeron-next exposes 4 tools: confirm_booking, search_rooms_by_area, search_room_options, check_in_user. Their descriptions and schemas cost roughly 250 tokens of context every time the server is loaded.
Does the io.github.Speeron-Polska/speeron-next MCP server require authentication?
No. We connected to io.github.Speeron-Polska/speeron-next without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.Speeron-Polska/speeron-next MCP server still maintained?
io.github.Speeron-Polska/speeron-next is still listed as active in the MCP registry. We last reached this channel on 30 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.