Query Markup Documents - On-device hybrid search for markdown files with BM25, vector search, and LLM reranking
ColossalCapital — Akashic Corpus & Agentic Platform is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Akashic corpus + Laya routing. Anonymous read; free signup in-band.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http colossalcapital-akashic-corpus-agentic-platfo-mcp https://mcp.colossalcapital.co/mcp
# 2 — ask your agent for something these tools do
# analyze_repo, draft_deployment_plan, generate_cicd_workflow and 21 more
ColossalCapital — Akashic Corpus & Agentic Platform costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http colossalcapital-akashic-corpus-agentic-platfo-mcp https://mcp.colossalcapital.co/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
24 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Trigger analysis on a repository. Returns the analysis run ID and status.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| repo_path | string | yes | — |
| entity_id | string | no | — |
| interaction_id | string | no | — |
Draft a deployment plan from a ticket or repository. Returns the drafted plan with stages.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| workspace_id | string | yes | — |
| source_repo | string | yes | — |
| environment | string | no | — |
| derived_from_ticket | string | no | — |
| cicd_provider | string | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| repo_path | string | yes | — |
| provider | string | yes | — |
| tier | string | no | — |
| build_command | string | no | — |
| test_command | string | no | — |
| deploy_enabled | boolean | no | — |
| deploy_environment | string | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| entity_id | string | no | — |
| trigger_check | boolean | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| status | string | no | — |
| category | string | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | no | — |
| persona | string | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| interaction_id | string | no | — |
Discover the ColossalCapital platform's public capabilities — fetches llms.txt. No account required. Use this first to learn what tools and APIs are available.
No parameter schema on file.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| string | yes | — | |
| name | string | yes | — |
| intended_tier | string | no | — |
| use_case | string | no | — |
| captcha_token | string | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | — |
| contact_email | string | yes | — |
| contact_name | string | no | — |
| industry | string | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | — |
| ed25519_pubkey | string | yes | — |
| operator_contact | string | no | — |
| intended_use | string | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| agent_id | string | yes | — |
| claimant_entity_id | string | yes | — |
| signature | string | yes | — |
| scopes | string | no | — |
| workspace_scope | string | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | no | — |
| stack_layer | string | no | — |
| technology | string | no | — |
| limit | integer | no | — |
Read a public Akashic corpus item in full. Items above the public class return an account_required pointer.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| entry_id | string | yes | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| task | string | yes | — |
| domain | string | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| product | string | no | — |
Read one corpus item's full record — evidence, license, quality, tags. Items above your visibility class return an account_required pointer.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| item_id | string | yes | — |
Report whether a cited corpus item helped — feeds Laya's routing flywheel so the corpus improves with use. Anonymous reports count at reduced weight.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| item_id | string | yes | — |
| domain | string | yes | — |
| success | boolean | yes | — |
| note | string | no | — |
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.
No parameter schema on file.
List LLM providers you can bring keys for (BYOK). The platform runs on your keys — inference cost is yours, ours is the routing.
No parameter schema on file.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| provider | string | yes | — |
| api_key | string | yes | — |
| scope | string | no | — |
| validate | boolean | no | — |
List which LLM providers have stored keys (never the keys themselves). Use to check BYOK configuration status.
No parameter schema on file.
Remove a stored BYOK provider key from the vault.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| provider | string | yes | — |
| scope | string | no | — |
Test an LLM provider key against the provider without storing it. Use before set_llm_key if you want to check validity first.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| provider | string | yes | — |
| api_key | string | yes | — |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install ColossalCapital — Akashic Corpus & Agentic Platform or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | high | capability blast radius (high) — client exposure if the model is manipulated | −6 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. high is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| analyze_repo | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| draft_deployment_plan | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| generate_cicd_workflow | code-execexternal-sink | code-exec: parameter "command"; external-sink: declares readOnlyHint: false, openWorldHint: true |
| check_heartbeat_monitors | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| fetch_hitl_items | untrusted-input | untrusted-input: keyword "fetch" |
| search_skillfiles | no tags | |
| get_research_basis | untrusted-input | untrusted-input: keyword "fetch" |
| get_public_capabilities | no tags | |
| register_account | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| register_org | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| register_agent | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| claim_agent | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| search_corpus | no tags | |
| read_corpus_item | no tags | |
| corpus_route | no tags | |
| corpus_domains | no tags | |
| corpus_item | no tags | |
| corpus_outcome | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| get_onboarding_guide | no tags | |
| list_llm_providers | no tags | |
| set_llm_key | state-write | state-write: declares readOnlyHint: false |
| list_llm_keys | no tags | |
| remove_llm_key | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| test_llm_key | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.1.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish ColossalCapital — Akashic Corpus & Agentic Platform can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.