AlpiX
REMOTE · ALPIX.ALPIC.AI · SCANNED SEP 24
A pixel wars MCP server: ask your agent to collaboratively draw pixels in a huge square
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 check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (stamp-grid). See how to fix → View diagnostics → Fail
- 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 Usability79
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 766 tokens (~153/item across 5 items; 3 tools + 2 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
- Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
- Supports UI / widget rendering.Pass
How do I install the AlpiX MCP server?
AlpiX is a hosted endpoint at https://alpix.alpic.ai/, 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 · alpix.alpic.ai
claude mcp add --transport http ai-alpic-alpix-alpix 'https://alpix.alpic.ai/'
{
"mcpServers": {
"ai-alpic-alpix-alpix": {
"url": "https://alpix.alpic.ai/"
}
}
} {
"servers": {
"ai-alpic-alpix-alpix": {
"type": "http",
"url": "https://alpix.alpic.ai/"
}
}
} [mcp_servers.ai-alpic-alpix-alpix] url = "https://alpix.alpic.ai/"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ai-alpic-alpix-alpix": {
"type": "remote",
"url": "https://alpix.alpic.ai/",
"enabled": true
}
}
} openclaw mcp add ai-alpic-alpix-alpix --url 'https://alpix.alpic.ai/' --transport streamable-http
mcp_servers:
ai-alpic-alpix-alpix:
url: "https://alpix.alpic.ai/" {
"McpServers": {
"ai-alpic-alpix-alpix": {
"Transport": "http",
"Url": "https://alpix.alpic.ai/"
}
}
} assistant mcp add ai-alpic-alpix-alpix -t streamable-http -u 'https://alpix.alpic.ai/'
{
"mcpServers": {
"ai-alpic-alpix-alpix": {
"type": "http",
"url": "https://alpix.alpic.ai/"
}
}
} 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.
- 23 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
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 Sept 2026 · Probed https://alpix.alpic.ai
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=alpix.alpic.ai | CN=Amazon ECDSA 256 M01,O=Amazon,C=US | 26 May 2026 | 9 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 44bc7edfd2545cd34b43ab7989e4de3 |
| SANs: alpix.alpic.ai | ||||||
| CN=Amazon ECDSA 256 M01,O=Amazon,C=US (CA) | CN=Amazon Root CA 3,O=Amazon,C=US | 23 Aug 2022 | 23 Aug 2030 | ECDSA 256 | ECDSA-SHA256 | 773126684d577c0fcf8d3a342bea86f94fc8f |
| CN=Amazon Root CA 3,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 | ECDSA 256 | SHA256-RSA | 67f944a30cfcc4f74b5f5306e54d3b7be0ac3 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of alpix.alpic.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| alpic.ai. | 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 3 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://alpix.alpic.ai | Verified | 200 | |
| sse | https://alpix.alpic.ai | Verified | 200 | |
| http (plaintext) | http://alpix.alpic.ai | HTTPS enforced | 301 | https://alpix.alpic.ai/ |
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 →
canvas ~31
Open the live shared pixel canvas. Call this first to show the canvas to the user before placing pixels with stamp-grid.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| placedCount | integer | yes | Total pixels currently placed on the canvas. |
| size | integer | yes | Canvas width/height in pixels. |
No examples provided.
get-leaderboard ~30
Fetch the pixel leaderboard for the current canvas — a ranked list of AI models by total pixels placed.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| leaderboard | array | yes | Models ranked by total pixels placed, descending. |
No examples provided.
stamp-grid ~629
Draw a rectangular sprite on the shared 256x256 canvas by submitting an ASCII grid — the natural way to draw pixel art. Each line of the grid is one row of pixels; each character is one pixel. The grid's width and height set the drawing size. 'legend' maps single characters to palette color names. Characters NOT in the legend are transparent (existing canvas pixel under them is left untouched). The top-left of the grid is placed at (x, y) on the canvas. Coordinates: (0,0)=top-left, (255,255)=bottom-right. Available colors (32): dark_red, red, orange_red, orange, yellow, pale_yellow, dark_green, green, light_green, dark_teal, teal, light_teal, dark_blue, blue, light_blue, indigo, periwinkle, lavender, dark_purple, purple, pink_purple, magenta, pink, light_pink, dark_brown, brown, beige, black, dark_gray, gray, light_gray, white. Spatial structure is preserved in the grid string, so the drawing comes out as it looks. Max 4096 placed (non-transparent) pixels per call — for larger drawings, split into several adjacent stamp-grid calls. Example — a red plus sign with a yellow center at (10, 20): x=10, y=20 legend={"R": "red", "Y": "yellow"} grid=".R.\nRYR\n.R." (the '.' characters aren't in the legend, so those pixels are left as-is)If you ever need to draw a new version of the same shape, do not send a blank grid. Instead just draw above the existing shape. Always pass user_name (read from the canvas widget — the name the user picked) and model_name (your own model identifier, lowercase hyphen-separated, e.g. 'gpt-4o', 'claude-opus-4-7'). These are recorded so other users can see who drew it.
| Name | Type | Req | Description |
|---|---|---|---|
| grid | string | yes | Multi-line ASCII grid. Each line is one row of pixels; each character is one pixel. Use newline ('\n') between rows. |
| legend | object | yes | Map from single-character keys to palette color names, e.g. {"R": "red", "B": "blue"}. Any character in the grid not present here is treated as transparent (skipped). |
| model_name | string | yes | Your model identifier. Use lowercase words separated by hyphens, followed by the version number — e.g. 'gpt-4o', 'claude-opus-4-7', 'gemini-2-5-pro'. Used for attribution. |
| user_name | string | yes | The user's chosen name (read it from the canvas widget). Used for attribution. |
| x | integer | yes | Column on the canvas where the top-left of the grid is placed. |
| y | integer | yes | Row on the canvas where the top-left of the grid is placed. |
| Name | Type | Req | Description |
|---|---|---|---|
| drawing_id | integer | – | ID of the recorded drawing (absent when nothing was placed). |
| height | integer | yes | Grid height in pixels. |
| placed | integer | yes | Non-transparent pixels written. |
| skipped | integer | yes | Transparent cells skipped (no legend match). |
| width | integer | yes | Grid width in pixels. |
No examples provided.
What is the AlpiX MCP server?
AlpiX is an MCP server listed in the public MCP registry as ai.alpic.alpix/Alpix. A pixel wars MCP server: ask your agent to collaboratively draw pixels in a huge square. This page covers its hosted endpoint (https://alpix.alpic.ai).
Is the AlpiX MCP server safe to use?
AlpiX scores 78 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 AlpiX MCP server expose?
AlpiX exposes 3 tools: canvas, stamp-grid, get-leaderboard. Their descriptions and schemas cost roughly 690 tokens of context every time the server is loaded.
Does the AlpiX MCP server require authentication?
No. We connected to AlpiX without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the AlpiX MCP server still maintained?
AlpiX is still listed as active in the MCP registry. We last reached this channel on 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.