# Colossalcapital Obvect MCP server

Source: https://glimind.com/server/mcp-registry%2Fco.colossalcapital%2Fobvect
Registry id: `mcp-registry/co.colossalcapital/obvect`
Status: live (checked 2026-10-27T02:48:27.952Z)

## Measurements (30 days)

- Uptime: 99.17%
- Checks: 853
- Outages (90 days): 4

## Install

```json
{
  "mcpServers": {
    "colossalcapital-obvect-mcp-server": {
      "type": "http",
      "url": "https://mcp.colossalcapital.co/mcp"
    }
  }
}
```

Claude Code:

```sh
claude mcp add --transport http colossalcapital-obvect-mcp-server https://mcp.colossalcapital.co/mcp
```

## Tools (24)

- `analyze_repo`: Trigger analysis on a repository. Returns the analysis run ID and status.
- `check_heartbeat_monitors`: List heartbeat monitor status (8 condition-based monitors) or trigger a manual heartbeat check cycle. Monitors watch for PR merges, deploy failures, test failur
- `claim_agent`: Bind a registered agent to a user or org account so it acts on their behalf (acted_for grant). Requires a signature from the agent over claim:{agent_id}:{entity
- `corpus_domains`: List the corpus domain lanes (261 domains of repos, docs, code examples, issues) with item counts — the discovery index for corpus_route and corpus_item.
- `corpus_item`: Read one corpus item's full record — evidence, license, quality, tags. Items above your visibility class return an account_required pointer.
- `corpus_outcome`: Report whether a cited corpus item helped — feeds Laya's routing flywheel so the corpus improves with use. Anonymous reports count at reduced weight.
- `corpus_route`: Route a task through Laya to the best corpus item — returns the decision kind, picked item, score, and citations. Items above your visibility class return an ac
- `draft_deployment_plan`: Draft a deployment plan from a ticket or repository. Returns the drafted plan with stages.
- `fetch_hitl_items`: Fetch pending HITL approval items with RBAC context (agent identity, caller role, required permission, and approval eligibility). Use this to check what needs h
- `generate_cicd_workflow`: Generate a CI/CD workflow (GitHub Actions, Bitbucket Pipelines, GitLab CI, or Tekton) with build, test, deploy, and callback stages. Returns YAML, filename, sta
- `get_onboarding_guide`: Returns the canonical onboarding flow for every caller class — anonymous, human signup, autonomous agent, agent binding, and org creation. Call this first if yo
- `get_public_capabilities`: Discover the ColossalCapital platform's public capabilities — fetches llms.txt. No account required. Use this first to learn what tools and APIs are available.
- `get_research_basis`: Fetch the interaction chain for a given interaction ID, showing all artifacts (heartbeat, analysis, ticket, agent, PR, deployment) in the closed loop. If no int
- `list_llm_keys`: List which LLM providers have stored keys (never the keys themselves). Use to check BYOK configuration status.
- `list_llm_providers`: List LLM providers you can bring keys for (BYOK). The platform runs on your keys — inference cost is yours, ours is the routing.
- `read_corpus_item`: Read a public Akashic corpus item in full. Items above the public class return an account_required pointer.
- `register_account`: Register a free ColossalCapital account for a human user. Creates the identity immediately (free tier, no billing) and returns a link_token to claim the Idio lo
- `register_agent`: Register an autonomous agent as a first-class account (entity_type=agent). The Ed25519 public key is the only credential — no password. Gets a prepaid wallet fo
- `register_org`: Register an organization account. Employees who signed up individually keep their accounts — org membership is added to them, never recreated. Returns the org's
- `remove_llm_key`: Remove a stored BYOK provider key from the vault.
- `search_corpus`: Search the Akashic corpus — the platform's knowledge base of tools, stack layers, design patterns, and exemplars. Public entries only; no account required. Regi
- `search_skillfiles`: Search for relevant skillfiles by query or persona. Skillfiles are the behavioral guidance layer for agents — they define how agents should write tests, create 
- `set_llm_key`: Store a BYOK LLM provider key in the encrypted vault. Validated against the provider before storing. scope='org' stores an org-wide key (admin-only). Requires a
- `test_llm_key`: Test an LLM provider key against the provider without storing it. Use before set_llm_key if you want to check validity first.

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.