Home / MCP registry index / co.colossalcapital/obvect
ColossalCapital — Akashic Corpus & Agentic Platform
co.colossalcapital/obvect in the official MCP registry.
Endpoint https://mcp.colossalcapital.co/mcp.
The registry describes it as: Akashic corpus + Laya routing. Anonymous read; free signup in-band.
We read its 24 tools on 2026-10-27. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
analyze_repo draft_deployment_plan generate_cicd_workflow check_heartbeat_monitors fetch_hitl_items search_skillfiles get_research_basis get_public_capabilities register_account register_org register_agent claim_agent search_corpus read_corpus_item corpus_route corpus_domains corpus_item corpus_outcome get_onboarding_guide list_llm_providers set_llm_key list_llm_keys remove_llm_key test_llm_key
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/co-colossalcapital-obvect)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.