ArcadeOps Public Discovery
REMOTE · ARCADEOPS.LEADALPES.FR · SCANNED SEP 20
Read-only ArcadeOps discovery for developer docs, OAuth, OpenAPI and synthetic sandbox.
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 Security83
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability87
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 235 tokens (~47/item across 5 items; 3 tools + 2 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management83
- Stability observed for 25 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
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 5 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 ArcadeOps Public Discovery MCP server?
ArcadeOps Public Discovery is a hosted endpoint at https://arcadeops.leadalpes.fr/mcp/public, 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 · arcadeops.leadalpes.fr
claude mcp add --transport http damso74-arcadeops-public-discovery 'https://arcadeops.leadalpes.fr/mcp/public'
{
"mcpServers": {
"damso74-arcadeops-public-discovery": {
"url": "https://arcadeops.leadalpes.fr/mcp/public"
}
}
} {
"servers": {
"damso74-arcadeops-public-discovery": {
"type": "http",
"url": "https://arcadeops.leadalpes.fr/mcp/public"
}
}
} [mcp_servers.damso74-arcadeops-public-discovery] url = "https://arcadeops.leadalpes.fr/mcp/public"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"damso74-arcadeops-public-discovery": {
"type": "remote",
"url": "https://arcadeops.leadalpes.fr/mcp/public",
"enabled": true
}
}
} openclaw mcp add damso74-arcadeops-public-discovery --url 'https://arcadeops.leadalpes.fr/mcp/public' --transport streamable-http
mcp_servers:
damso74-arcadeops-public-discovery:
url: "https://arcadeops.leadalpes.fr/mcp/public" {
"McpServers": {
"damso74-arcadeops-public-discovery": {
"Transport": "http",
"Url": "https://arcadeops.leadalpes.fr/mcp/public"
}
}
} assistant mcp add damso74-arcadeops-public-discovery -t streamable-http -u 'https://arcadeops.leadalpes.fr/mcp/public'
{
"mcpServers": {
"damso74-arcadeops-public-discovery": {
"type": "http",
"url": "https://arcadeops.leadalpes.fr/mcp/public"
}
}
} 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.
- 18 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.
- 16 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.
- 14 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.
- 12 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 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 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 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 6 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 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 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 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 20 Sept 2026 · Probed https://arcadeops.leadalpes.fr/mcp/public
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=arcadeops.leadalpes.fr | CN=YE1,O=Let's Encrypt,C=US | 3 Aug 2026 | 1 Nov 2026 | ECDSA 256 | ECDSA-SHA384 | 51bdd841b795050d859f459e3df38e5e966 |
| SANs: arcadeops.leadalpes.fr | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of arcadeops.leadalpes.fr. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| fr. | present | 65381 | 13 | Verified |
| leadalpes.fr. | present | 20366 | 13 | Verified |
| arcadeops.leadalpes.fr. | Verified address RRset verified with the apex keys |
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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' 'wasm-unsafe-eval'; style-src 'self' 'unsafe-inline'; img-src 'self' data: blob: https://api.dicebear.com https://www.gravatar.com https://bnunkedencbjnrjapybz.supabase.co; font-src 'self' data:; connect-src 'self' https://bnunkedencbjnrjapybz.supabase.co wss://bnunkedencbjnrjapybz.supabase.co https://api.openai.com https://api.stripe.com https://*.sentry.io https://*.ingest.de.sentry.io; frame-ancestors 'none'; base-uri 'self'; form-action 'self' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://arcadeops.leadalpes.fr/mcp/public | Verified | 200 | |
| http (plaintext) | http://arcadeops.leadalpes.fr/mcp/public | HTTPS enforced | 308 | https://arcadeops.leadalpes.fr/mcp/public |
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 →
arcadeops_discover Découvrir ArcadeOps ~39
Retourne les ressources publiques ArcadeOps, le guide OAuth et l'adresse du MCP métier protégé. Aucune donnée privée n'est lue.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
arcadeops_get_document Résoudre un document ArcadeOps ~43
Retourne le lien canonique et le type MIME d’un document public ArcadeOps identifié.
| Name | Type | Req | Description |
|---|---|---|---|
| document | string | yes | Identifiant stable du document public à ouvrir. |
No output schema declared.
No examples provided.
arcadeops_search_docs Rechercher la documentation ArcadeOps ~52
Recherche par nom et description dans le catalogue public ArcadeOps. Aucun contenu privé ni appel réseau secondaire.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Termes recherchés, par exemple OAuth, OpenAPI, CLI ou sandbox. |
No output schema declared.
No examples provided.
What is the ArcadeOps Public Discovery MCP server?
ArcadeOps Public Discovery is an MCP server listed in the public MCP registry as io.github.Damso74/arcadeops-public-discovery. Read-only ArcadeOps discovery for developer docs, OAuth, OpenAPI and synthetic sandbox. This page covers its hosted endpoint (https://arcadeops.leadalpes.fr/mcp/public).
Is the ArcadeOps Public Discovery MCP server safe to use?
ArcadeOps Public Discovery scores 88 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 ArcadeOps Public Discovery MCP server expose?
ArcadeOps Public Discovery exposes 3 tools: arcadeops_discover, arcadeops_search_docs, arcadeops_get_document. Their descriptions and schemas cost roughly 134 tokens of context every time the server is loaded.
Does the ArcadeOps Public Discovery MCP server require authentication?
No. We connected to ArcadeOps Public Discovery without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the ArcadeOps Public Discovery MCP server still maintained?
ArcadeOps Public Discovery is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.