Koskamo

runchr MCP

A curated registry of agent artifacts that allows agents to search for stacks, retrieve stack cards and manifests, and obtain installation plans for MCP servers and other tools without requiring authentication.

Endpoint and access

No sign-in to connect and list tools. Individual tools may still need a vendor account, credentials, or permissions; check the documented prerequisites.

runchr MCP logo, by runchrCommunity listingStreamable HTTPNo sign-inEndpoint checked 2026-11-06Published by runchr
MCP endpoint (Streamable HTTP)
https://api.runchr.com/mcp
Vendor documentation

What its tools do

4 tools, grouped by the hints the server advertises. Hints are self-declared, not verified behavior.

Read-only (3)

Can change data (1)

4 of 4 have a description · 4 of 4 declare behavior hints · 4 of 4 with parameters document them all

Checks and signals

Each line is separate evidence, not a trust score.

  • Passed Endpoint answered the live check ·
  • Availability 1 of 1 checks passed in 30 days

What you can do with it

  • Find agent stacks by problem domain or text
  • Retrieve a specific stack's card and tools
  • Get the machine-readable manifest for a stack
  • Obtain an installation plan with shell commands

Source and maintenance

Community listingRegistry 0.1.2
mcp-registry: io.github.rmngl/runchr@0.1.2Project website

Protocol and capabilities

Server
runchr 0.1.0
MCP protocol negotiated in check
2025-06-18
Tools
4 advertised
Resources
Not advertised
Resource templates
Not advertised
Prompts
Not advertised
Server-advertised capabilities
{
  "tools": {}
}

Tools

4 advertised

search_stacks
Advertised by the server during the last successful anonymous check.
Advertised read-only

Find agent stacks by problem domain or text. A query is split into words and any of them may match, against the name, the copy, and the prompt. When nothing matches, the reply is labelled and filled with the most established stacks.

search_stacks input schema
{
  "type": "object",
  "properties": {
    "limit": {
      "type": "integer",
      "description": "How many stacks to return (default 10)."
    },
    "query": {
      "type": "string",
      "description": "What the agent needs to do, in your own words. Split into words; any may match."
    },
    "topic": {
      "type": "string",
      "description": "A problem domain id, e.g. software-devops."
    }
  }
}
search_stacks annotations
{
  "readOnlyHint": true,
  "openWorldHint": false,
  "idempotentHint": true
}
get_stack
Advertised by the server during the last successful anonymous check.
Advertised read-only

One stack's card: its copy, its tools, its tier, and its revision.

get_stack input schema
{
  "type": "object",
  "required": [
    "owner",
    "slug"
  ],
  "properties": {
    "slug": {
      "type": "string",
      "description": "The stack's slug."
    },
    "owner": {
      "type": "string",
      "description": "The stack's namespace owner (a login, or runchr)."
    }
  }
}
get_stack annotations
{
  "readOnlyHint": true,
  "openWorldHint": false,
  "idempotentHint": true
}
get_manifest
Advertised by the server during the last successful anonymous check.

The manifest a loader runs: the tools, the model, the harness, and the prompt. This is the thing to install.

get_manifest input schema
{
  "type": "object",
  "required": [
    "owner",
    "slug"
  ],
  "properties": {
    "slug": {
      "type": "string",
      "description": "The stack's slug."
    },
    "owner": {
      "type": "string",
      "description": "The stack's namespace owner (a login, or runchr)."
    }
  }
}
get_manifest annotations
{
  "readOnlyHint": false,
  "openWorldHint": false,
  "idempotentHint": false,
  "destructiveHint": false
}
get_install_plan
Advertised by the server during the last successful anonymous check.
Advertised read-only

How to install a stack: the MCP servers to configure, the shell commands to run, and the notes (a path, a harness command) for the rest. Deciding and configuring are open; the agent's host runs the commands.

get_install_plan input schema
{
  "type": "object",
  "required": [
    "owner",
    "slug"
  ],
  "properties": {
    "slug": {
      "type": "string",
      "description": "The stack's slug."
    },
    "owner": {
      "type": "string",
      "description": "The stack's namespace owner (a login, or runchr)."
    }
  }
}
get_install_plan annotations
{
  "readOnlyHint": true,
  "openWorldHint": false,
  "idempotentHint": true
}

Prompts

Not advertised

No prompt definitions available.

Resources

Not advertised

No resource definitions available.

90-day uptime

A lightweight connection check about every six hours, sampled on hosts with many listings. It shows the server answered, not that its tools work.

Too few checks for a percentage yet (1 of 1 answered).

  1. 2026-11-07: 1 of 1 checks answered

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks
1 of 1 (100%)
Average latency
218 ms
95th percentile latency
218 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

  • · probe · passed · 218 ms · metadata changed · 4 tool(s)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http runchr-mcp https://api.runchr.com/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add runchr-mcp --url https://api.runchr.com/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable runchr-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "runchr-mcp": {
      "url": "https://api.runchr.com/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).
Cline configuration
{
  "mcpServers": {
    "runchr-mcp": {
      "type": "streamableHttp",
      "url": "https://api.runchr.com/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start runchr-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "runchr-mcp": {
      "type": "http",
      "url": "https://api.runchr.com/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http runchr-mcp https://api.runchr.com/mcp

Claude Desktop

Open Claude Settings > Connectors > Add custom connector, enter this server URL and enable it for the conversation. This is a manual remote-connector handoff, not a desktop JSON configuration.
Claude Desktop configuration
https://api.runchr.com/mcp

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "runchr-mcp": {
      "serverUrl": "https://api.runchr.com/mcp"
    }
  }
}

Let your agent find its tools

Find servers like runchr MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.

Connect Koskamo Explore workflows
See all 8,317