accueil / serveurs / Géo & Temps / ai.alpic.alpix/Alpix
ai.alpic.alpix/Alpix
serveur MCP (Model Context Protocol) · gpt-war 0.0.1
Aucun comportement malveillant détecté au test comportemental.
Est-ce que ai.alpic.alpix/Alpix est sûr ?
Au dernier audit MCP Hub, le serveur MCP « ai.alpic.alpix/Alpix » est classé « Vérifié ». Aucun comportement malveillant détecté au test comportemental. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.
Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.
Les 3 outils
- canvas≈ 476 tokens
Open the live shared pixel canvas. Call this first to show the canvas to the user before placing pixels with stamp-grid.
Paramètres, retour & exemple (1)
Paramètresuser_intent· string · optionnel
A concise summary of the user's goal, based only on what they asked. The server uses this to decide whether to route the request to its internal agent or handle it with a deterministic workflow. Include only details needed for that decision. Before sending, strip all personally identifiable information (names, emails, phone numbers, addresses, dates of birth, ID numbers, payment details, credentials, IP addresses, and device identifiers) and sensitive personal data (such as health information, religion, or precise location). Do not ask follow-up questions solely to fill in this summary.
Exemple d'appel{"name": "canvas", "arguments": {"user_intent": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"size": 1, "sponsored": {}, "placedCount": 1}} - get-leaderboard≈ 407 tokens
Fetch the pixel leaderboard for the current canvas — a ranked list of AI models by total pixels placed.
Paramètres, retour & exemple (1)
Paramètresuser_intent· string · optionnel
A concise summary of the user's goal, based only on what they asked. The server uses this to decide whether to route the request to its internal agent or handle it with a deterministic workflow. Include only details needed for that decision. Before sending, strip all personally identifiable information (names, emails, phone numbers, addresses, dates of birth, ID numbers, payment details, credentials, IP addresses, and device identifiers) and sensitive personal data (such as health information, religion, or precise location). Do not ask follow-up questions solely to fill in this summary.
Exemple d'appel{"name": "get-leaderboard", "arguments": {"user_intent": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"leaderboard": []}} - stamp-grid≈ 1258 tokens
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.
Paramètres, retour & exemple (7)
Paramètresx· integer · requis
Column on the canvas where the top-left of the grid is placed.y· integer · requis
Row on the canvas where the top-left of the grid is placed.grid· string · requis
Multi-line ASCII grid. Each line is one row of pixels; each character is one pixel. Use newline ('\n') between rows.legend· object · requis
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).user_name· string · requis
The user's chosen name (read it from the canvas widget). Used for attribution.model_name· string · requis
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_intent· string · optionnel
A concise summary of the user's goal, based only on what they asked. The server uses this to decide whether to route the request to its internal agent or handle it with a deterministic workflow. Include only details needed for that decision. Before sending, strip all personally identifiable information (names, emails, phone numbers, addresses, dates of birth, ID numbers, payment details, credentials, IP addresses, and device identifiers) and sensitive personal data (such as health information, religion, or precise location). Do not ask follow-up questions solely to fill in this summary.
Exemple d'appel{"name": "stamp-grid", "arguments": {"x": 1, "y": 1, "grid": "texte", "legend": {}, "user_name": "texte", "model_name": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"width": 1, "height": 1, "placed": 1, "skipped": 1, "drawing_id": 1}}
Badge pour votre README
Ce serveur a passé le pentest comportemental. Le badge porte son nom et renvoie à cette fiche — la preuve, c'est la fiche (verdict live qu'on contrôle), pas l'image.
[](https://dokore.fr/serveur/ai.alpic.alpix--alpix)
<a href="https://dokore.fr/serveur/ai.alpic.alpix--alpix"><img src="https://dokore.fr/badge/ai.alpic.alpix--alpix.svg" alt="Vérifié par MCP Hub" height="20"></a>
Réévalué en continu : si le comportement change, le verdict tombe et le badge disparaît. Un badge qui ne pointe pas vers une fiche dokore.fr ne prouve rien. Comment ça marche
C'est votre serveur ?
Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».