Developer Tools
runx.ai
Find and inspect runx skills, including their manifests, authority, trust signals, and install commands.
ENDPOINT 1
https://api.runx.ai/mcp
MCP server metadata
- Name
- runx
- Version
- 1.0.0
Use this server to find a runx skill and read it before running anything. search_skills finds candidates by what they do. get_skill returns one skill in full: its manifest, the authority it asks for, its trust signals, and the exact command to install it through the runx CLI. Show a caller the requested authority and trust tier before you suggest running a skill. This surface is read-only, so nothing here executes a skill, moves money, or changes state; execution happens through the runx CLI or the authenticated hosted API, both of which apply policy and seal a receipt.
Known tools 2
get_skillRead 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.
Potential side effectsCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.runx]
url = "https://api.runx.ai/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"runx": {
"type": "http",
"url": "https://api.runx.ai/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: runx
Remote MCP URL: https://api.runx.ai/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"runx": {
"url": "https://api.runx.ai/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"runx": {
"type": "http",
"url": "https://api.runx.ai/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "runx",
"transport": "streamable-http",
"url": "https://api.runx.ai/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.