Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

ColossalCapital — Akashic Corpus & Agentic Platform

REMOTE · MCP.COLOSSALCAPITAL.CO

Akashic corpus + Laya routing. Anonymous read; free signup in-band.

+4 this week 69 Trust /100

Last scanned (23 hours ago)

Scores higher than 54% of remote servers

Reachable. Last reached 4 Nov 2026.

Category CI/CD and DevOps

Recent critical change

Authorization (24 Oct 2026). See the changelog before you install this server.

Trust breakdown (7 categories)

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 Security66
Transport & Reachability100
Schema Quality & AI Usability61
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 1577 tokens (~65/item across 24 items; 24 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management40
  • Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 25 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Changelog

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.

  • 4 Nov 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.

  • 2 Nov 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.

  • 31 Oct 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.

  • 29 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

  • 27 Oct 26 +3
    • HSTS header: fail → pass ▲ security
  • 25 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 24 Oct 26 +2
    • Authorization: unverified → fail ▼ critical
    • Tool “remove_llm_key” is now declared destructive security
    • Stability: unverified → 0.03 ▲ functional
    • Destructive annotations: All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation. functional
    • Server version: 1.0.0 → 1.0.1 functional
    • “register_account” added an optional parameter “captcha_token” cosmetic
    • Tool “analyze_repo” changed its title: Analyze Repository cosmetic
    • Tool “check_heartbeat_monitors” changed its title: Check Heartbeat Monitors cosmetic
    • Tool “claim_agent” changed its title: Claim Agent cosmetic
    • Tool “corpus_domains” changed its title: List Corpus Domains cosmetic
    • Tool “corpus_item” changed its title: Get Corpus Item cosmetic
    • Tool “corpus_outcome” changed its title: Report Corpus Outcome cosmetic
    • Tool “corpus_route” changed its title: Route Task via Laya cosmetic
    • Tool “draft_deployment_plan” changed its title: Draft Deployment Plan cosmetic
    • Tool “fetch_hitl_items” changed its title: Fetch HITL Items cosmetic
    • Tool “generate_cicd_workflow” changed its title: Generate CI/CD Workflow cosmetic
    • Tool “get_onboarding_guide” changed its title: Get Onboarding Guide cosmetic
    • Tool “get_public_capabilities” changed its title: Get Public Capabilities cosmetic
    • Tool “get_research_basis” changed its title: Get Research Basis cosmetic
    • Tool “list_llm_keys” changed its title: List LLM Keys cosmetic
    • Tool “list_llm_providers” changed its title: List LLM Providers cosmetic
    • Tool “read_corpus_item” changed its title: Read Corpus Item cosmetic
    • Tool “register_account” changed its title: Register Account cosmetic
    • Tool “register_agent” changed its title: Register Agent cosmetic
    • Tool “register_org” changed its title: Register Organization cosmetic
    • Tool “remove_llm_key” changed its title: Remove LLM Key cosmetic
    • Tool “search_corpus” changed its title: Search Corpus cosmetic
    • Tool “search_skillfiles” changed its title: Search Skillfiles cosmetic
    • Tool “set_llm_key” changed its title: Set LLM Key cosmetic
    • Tool “test_llm_key” changed its title: Test LLM Key cosmetic
  • 23 Oct 26 59

    First indexed and scored.

Diagnostics

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 4 Nov 2026 · Probed https://mcp.colossalcapital.co/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mcp.colossalcapital.co CN=YE1,O=Let's Encrypt,C=US 23 Oct 2026 21 Jan 2027 ECDSA 256 ECDSA-SHA384 55dcd7cca1bf3c2209fdbb150aceacfd094
SANs: mcp.colossalcapital.co
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 mcp.colossalcapital.co. — Secure

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
co. present 7786 8 Verified
colossalcapital.co. present 2371 13 Verified
mcp.colossalcapital.co. 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=31536000; includeSubDomains
x-content-type-options nosniff

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.colossalcapital.co/mcp Verified 200
http (plaintext) http://mcp.colossalcapital.co/mcp HTTPS enforced 301 https://mcp.colossalcapital.co/mcp
MCP tools · 24 exposed · ~1,525 tokens

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 →

Tool Tokens
analyze_repo ~46

Trigger analysis on a repository. Returns the analysis run ID and status.

NameTypeReqDescription
entity_idstring––
interaction_idstring––
repo_pathstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

check_heartbeat_monitors ~75

List heartbeat monitor status (8 condition-based monitors) or trigger a manual heartbeat check cycle. Monitors watch for PR merges, deploy failures, test failures, dependency drift, doc drift, security advisories, stale branches, and failing suites.

NameTypeReqDescription
entity_idstring––
trigger_checkboolean––
NameTypeReqDescription
resultstringyes–

No examples provided.

claim_agent ~102

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_id} — the agent consents, and the account consents. The agent keeps its own identity.

NameTypeReqDescription
agent_idstringyes–
claimant_entity_idstringyes–
scopesstring––
signaturestringyes–
workspace_scopestring––
NameTypeReqDescription
resultstringyes–

No examples provided.

corpus_domains ~47

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.

NameTypeReqDescription
productstring––
NameTypeReqDescription
resultstringyes–

No examples provided.

corpus_item ~42

Read one corpus item's full record — evidence, license, quality, tags. Items above your visibility class return an account_required pointer.

NameTypeReqDescription
item_idstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

corpus_outcome ~67

Report whether a cited corpus item helped — feeds Laya's routing flywheel so the corpus improves with use. Anonymous reports count at reduced weight.

NameTypeReqDescription
domainstringyes–
item_idstringyes–
notestring––
successbooleanyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

corpus_route ~58

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 account_required pointer.

NameTypeReqDescription
domainstring––
taskstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

draft_deployment_plan ~68

Draft a deployment plan from a ticket or repository. Returns the drafted plan with stages.

NameTypeReqDescription
cicd_providerstring––
derived_from_ticketstring––
environmentstring––
source_repostringyes–
workspace_idstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

fetch_hitl_items ~59

Fetch pending HITL approval items with RBAC context (agent identity, caller role, required permission, and approval eligibility). Use this to check what needs human approval before proceeding.

NameTypeReqDescription
categorystring––
statusstring––
NameTypeReqDescription
resultstringyes–

No examples provided.

generate_cicd_workflow ~113

Generate a CI/CD workflow (GitHub Actions, Bitbucket Pipelines, GitLab CI, or Tekton) with build, test, deploy, and callback stages. Returns YAML, filename, stages, and per-field research basis.

NameTypeReqDescription
build_commandstring––
deploy_enabledboolean––
deploy_environmentstring––
providerstringyes–
repo_pathstringyes–
test_commandstring––
tierstring––
NameTypeReqDescription
resultstringyes–

No examples provided.

get_onboarding_guide ~46

Returns the canonical onboarding flow for every caller class — anonymous, human signup, autonomous agent, agent binding, and org creation. Call this first if you're unsure how to proceed.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultstringyes–

No examples provided.

get_public_capabilities ~42

Discover the ColossalCapital platform's public capabilities — fetches llms.txt. No account required. Use this first to learn what tools and APIs are available.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultstringyes–

No examples provided.

get_research_basis ~62

Fetch the interaction chain for a given interaction ID, showing all artifacts (heartbeat, analysis, ticket, agent, PR, deployment) in the closed loop. If no interaction_id is provided, lists all known interaction IDs.

NameTypeReqDescription
interaction_idstring––
NameTypeReqDescription
resultstringyes–

No examples provided.

list_llm_keys ~32

List which LLM providers have stored keys (never the keys themselves). Use to check BYOK configuration status.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultstringyes–

No examples provided.

list_llm_providers ~41

List LLM providers you can bring keys for (BYOK). The platform runs on your keys — inference cost is yours, ours is the routing.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultstringyes–

No examples provided.

read_corpus_item ~40

Read a public Akashic corpus item in full. Items above the public class return an account_required pointer.

NameTypeReqDescription
entry_idstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

register_account ~101

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 login later. Call this when a tool returns account_required, or when a user asks to sign up.

NameTypeReqDescription
captcha_tokenstring––
emailstringyes–
intended_tierstring––
namestringyes–
use_casestring––
NameTypeReqDescription
resultstringyes–

No examples provided.

register_agent ~95

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 for metered tools. Can later be bound to a user via claim_agent without losing its identity.

NameTypeReqDescription
ed25519_pubkeystringyes–
intended_usestring––
namestringyes–
operator_contactstring––
NameTypeReqDescription
resultstringyes–

No examples provided.

register_org ~69

Register an organization account. Employees who signed up individually keep their accounts — org membership is added to them, never recreated. Returns the org's API key.

NameTypeReqDescription
contact_emailstringyes–
contact_namestring––
industrystring––
namestringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

remove_llm_key ~35

Remove a stored BYOK provider key from the vault.

NameTypeReqDescription
providerstringyes–
scopestring––
NameTypeReqDescription
resultstringyes–

No examples provided.

search_corpus ~83

Search the Akashic corpus — the platform's knowledge base of tools, stack layers, design patterns, and exemplars. Public entries only; no account required. Register via register_account or register_agent for the full corpus.

NameTypeReqDescription
limitinteger––
querystring––
stack_layerstring––
technologystring––
NameTypeReqDescription
resultstringyes–

No examples provided.

search_skillfiles ~66

Search for relevant skillfiles by query or persona. Skillfiles are the behavioral guidance layer for agents — they define how agents should write tests, create PRs, lint code, review, and generate CI/CD workflows.

NameTypeReqDescription
personastring––
querystring––
NameTypeReqDescription
resultstringyes–

No examples provided.

set_llm_key ~84

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 an account — call register_account or authenticate first.

NameTypeReqDescription
api_keystringyes–
providerstringyes–
scopestring––
validateboolean––
NameTypeReqDescription
resultstringyes–

No examples provided.

test_llm_key ~52

Test an LLM provider key against the provider without storing it. Use before set_llm_key if you want to check validity first.

NameTypeReqDescription
api_keystringyes–
providerstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

Install

How do I install the ColossalCapital — Akashic Corpus & Agentic Platform MCP server?

ColossalCapital — Akashic Corpus & Agentic Platform is a hosted endpoint at https://mcp.colossalcapital.co/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 · mcp.colossalcapital.co

# add to Claude Code
claude mcp add --transport http co-colossalcapital-obvect 'https://mcp.colossalcapital.co/mcp'
Common questions

What is the ColossalCapital — Akashic Corpus & Agentic Platform MCP server?

ColossalCapital — Akashic Corpus & Agentic Platform is an MCP server listed in the public MCP registry as co.colossalcapital/obvect. Akashic corpus + Laya routing. Anonymous read; free signup in-band. This page covers its hosted endpoint (https://mcp.colossalcapital.co/mcp).

Is the ColossalCapital — Akashic Corpus & Agentic Platform MCP server safe to use?

ColossalCapital — Akashic Corpus & Agentic Platform scores 69 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 ColossalCapital — Akashic Corpus & Agentic Platform MCP server expose?

ColossalCapital — Akashic Corpus & Agentic Platform exposes 24 tools: analyze_repo, draft_deployment_plan, generate_cicd_workflow, check_heartbeat_monitors, fetch_hitl_items, and 19 more. Their descriptions and schemas cost roughly 1,525 tokens of context every time the server is loaded.

Does the ColossalCapital — Akashic Corpus & Agentic Platform MCP server require authentication?

No. We connected to ColossalCapital — Akashic Corpus & Agentic Platform without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the ColossalCapital — Akashic Corpus & Agentic Platform MCP server still maintained?

ColossalCapital — Akashic Corpus & Agentic Platform is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.