runx
REMOTE · API.RUNX.AI · SCANNED SEP 24
The governed runtime for agent skills. Search the catalog and inspect a skill before running it.
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 Security69
- 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 enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 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
- Context-footprint check failed: tool/resource definitions use about 313 tokens (~156/item across 2 items; 2 tools + 0 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 Management57
- Stability observed for 17 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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 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
How do I install the runx MCP server?
runx is a hosted endpoint at https://api.runx.ai/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 · api.runx.ai
claude mcp add --transport http ai-runx-runx 'https://api.runx.ai/mcp'
{
"mcpServers": {
"ai-runx-runx": {
"url": "https://api.runx.ai/mcp"
}
}
} {
"servers": {
"ai-runx-runx": {
"type": "http",
"url": "https://api.runx.ai/mcp"
}
}
} [mcp_servers.ai-runx-runx] url = "https://api.runx.ai/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ai-runx-runx": {
"type": "remote",
"url": "https://api.runx.ai/mcp",
"enabled": true
}
}
} openclaw mcp add ai-runx-runx --url 'https://api.runx.ai/mcp' --transport streamable-http
mcp_servers:
ai-runx-runx:
url: "https://api.runx.ai/mcp" {
"McpServers": {
"ai-runx-runx": {
"Transport": "http",
"Url": "https://api.runx.ai/mcp"
}
}
} assistant mcp add ai-runx-runx -t streamable-http -u 'https://api.runx.ai/mcp'
{
"mcpServers": {
"ai-runx-runx": {
"type": "http",
"url": "https://api.runx.ai/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.
- 23 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 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 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.
- 19 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.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 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 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.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 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 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Sept 26 +1
- Stability: unverified → 0.03 ▲ 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 24 Sept 2026 · Probed https://api.runx.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=runx.ai | CN=WE1,O=Google Trust Services,C=US | 5 Aug 2026 | 3 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 9316d4f49a86131c138e66fe62b3dbb2 |
| SANs: runx.ai, *.runx.ai | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.runx.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| runx.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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| content-security-policy | default-src 'self' https: data: blob: 'unsafe-inline' |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | no-referrer-when-downgrade |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.runx.ai/mcp | Verified | 200 | |
| http (plaintext) | http://api.runx.ai/mcp | Inconclusive | 406 |
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 →
get_skill ~104
Read one runx skill in full before running it: its manifest, the authority it asks for, its publisher and trust signals, and the exact command to install and run it through the runx CLI. Everything needed to decide whether to trust a skill arrives in this one call.
| Name | Type | Req | Description |
|---|---|---|---|
| skill_id | string | yes | Skill id in owner/name form, for example `ausca/browser-session`. |
| version | string | – | Exact version to read. Defaults to the latest published version. |
No output schema declared.
No examples provided.
search_skills ~87
Find runx skills by what they do. Returns each match with its skill id, owner, description, latest version, and trust tier, so a caller can pick one and then read it in full with get_skill.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum matches to return. |
| query | string | yes | What the skill should do, in plain words. An empty string browses everything. |
No output schema declared.
No examples provided.
What is the runx MCP server?
runx is an MCP server listed in the public MCP registry as ai.runx/runx. The governed runtime for agent skills. Search the catalog and inspect a skill before running it. This page covers its hosted endpoint (https://api.runx.ai/mcp).
Is the runx MCP server safe to use?
runx scores 79 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 runx MCP server expose?
runx exposes 2 tools: search_skills, get_skill. Their descriptions and schemas cost roughly 191 tokens of context every time the server is loaded.
Does the runx MCP server require authentication?
No. We connected to runx without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the runx MCP server still maintained?
runx 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.