Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Magic 8 Ball QA Demo

REMOTE · TEST5-CA2CC17F.ALPIC.LIVE

Skybridge demo for QA and playground validation

0 this week 23 Trust /100

Last scanned (17 hours ago)

Scores higher than 6% of remote servers

Reachable. Last reached 24 Oct 2026.

Category Entertainment and Games

Trust breakdown (7 categories)

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
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
  • Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
  • Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified

Unverified: 5 categories

Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

Changelog

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.

  • 9 Oct 26 −61
    • Endpoint reachability: reachable → not serving MCP ▼ security
    • Stability: pass → unverified ▼ security
    • Authorization: partial → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Transport: pass → fail ▼ security
    • Schema quality: 100 → unverified ▼ functional
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
  • 7 Oct 26 0
    • Resource “magic-8-ball” now points somewhere else: ui://widgets/apps-sdk/magic-8-ball.html → ui://widgets/ext-apps/magic-8-ball.html security
  • 5 Oct 26 0
    • Resource “magic-8-ball” now points somewhere else: ui://widgets/apps-sdk/magic-8-ball.html → ui://widgets/ext-apps/magic-8-ball.html security
  • 4 Oct 26 0
    • Resource “magic-8-ball” now points somewhere else: ui://widgets/apps-sdk/magic-8-ball.html → ui://widgets/ext-apps/magic-8-ball.html security
  • 3 Oct 26 0
    • Resource “magic-8-ball” now points somewhere else: ui://widgets/apps-sdk/magic-8-ball.html → ui://widgets/ext-apps/magic-8-ball.html security
  • 2 Oct 26 0
    • Resource “magic-8-ball” now points somewhere else: ui://widgets/apps-sdk/magic-8-ball.html → ui://widgets/ext-apps/magic-8-ball.html security
  • 1 Oct 26 +61
    • Authorization: unverified → partial ▲ security
    • Injection markers: unverified → pass ▲ security
    • Stability: unverified → pass ▲ security
    • Transport: fail → pass ▲ security
    • Resource “magic-8-ball” now points somewhere else: ui://widgets/apps-sdk/magic-8-ball.html → ui://widgets/ext-apps/magic-8-ball.html security
    • Endpoint reachability: not serving MCP → reachable ▲ functional
    • Tool coverage: unverified → 100 ▲ functional
    • Schema quality: unverified → 100 ▲ functional
    • MCP protocol: unverified → pass ▲ functional
  • 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
Diagnostics

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 24 Oct 2026 · Probed https://test5-ca2cc17f.alpic.live

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.alpic.live CN=Amazon RSA 2048 M04,O=Amazon,C=US 23 Sept 2026 8 Apr 2027 RSA 2048 SHA256-RSA 41ca0c3068063f7c713f936a81919aa
SANs: *.alpic.live
CN=Amazon RSA 2048 M04,O=Amazon,C=US (CA) CN=Amazon Root CA 1,O=Amazon,C=US 23 Aug 2022 23 Aug 2030 RSA 2048 SHA256-RSA 773124f2a952e3ed18a58bdb85d1bc0ce5f27
CN=Amazon Root CA 1,O=Amazon,C=US (CA) CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US 25 May 2015 31 Dec 2037 RSA 2048 SHA256-RSA 67f944a2a27cdf3fac2ae2b01f908eeb9c4c6

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of test5-ca2cc17f.alpic.live. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
live. present 36322 8 Verified
alpic.live. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Inconclusive

We could not reach the endpoint well enough to judge its authorisation posture.

Result Inconclusive
HTTP status 404

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 3 probes
Transport URL Outcome Status Location
streamable-http https://test5-ca2cc17f.alpic.live HTTP error 404
sse https://test5-ca2cc17f.alpic.live HTTP error 404
http (plaintext) http://test5-ca2cc17f.alpic.live HTTPS enforced 301 https://test5-ca2cc17f.alpic.live/
MCP tools · 1 exposed · ~28 tokens

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 →

Tool Tokens
magic-8-ball ~28

For fortune-telling or seeking advice.

NameTypeReqDescription
questionstringyesThe user question.

No output schema declared.

No examples provided.

Install

How do I install the Magic 8 Ball QA Demo MCP server?

Magic 8 Ball QA Demo is a hosted endpoint at https://test5-ca2cc17f.alpic.live/, 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 · test5-ca2cc17f.alpic.live

# add to Claude Code
claude mcp add --transport http live-alpic-test5-ca2cc17f-test5 'https://test5-ca2cc17f.alpic.live/'
Common questions

What is the Magic 8 Ball QA Demo MCP server?

Magic 8 Ball QA Demo is an MCP server listed in the public MCP registry as live.alpic.test5-ca2cc17f/test5. Skybridge demo for QA and playground validation. This page covers its hosted endpoint (https://test5-ca2cc17f.alpic.live).

Is the Magic 8 Ball QA Demo MCP server safe to use?

Magic 8 Ball QA Demo scores 23 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 Magic 8 Ball QA Demo MCP server expose?

Magic 8 Ball QA Demo exposes 1 tool: magic-8-ball. Their descriptions and schemas cost roughly 28 tokens of context every time the server is loaded.

Does the Magic 8 Ball QA Demo MCP server require authentication?

Its publisher declares no required credentials for Magic 8 Ball QA Demo. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

Is the Magic 8 Ball QA Demo MCP server still maintained?

Magic 8 Ball QA Demo is still listed as active in the MCP registry. We last reached this channel on 24 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.