Skip to content
External endpointresponds

Arcology Knowledge Node

Engineering knowledge base for Arcology One. 8 domains, 32 entries, 140+ open questions.

Endpoint URL
https://arcology-mcp.fly.dev/mcp
Current status
responds
Last checked
Aug 17, 2026, 05:00 AM UTC
Check
MCP initialize · 8s limit
Latency
127 ms
Response record
4 of 4 rounds
Transport
streamable-http
Source
mcp_registry
Registry name
io.github.YourLifewithAI/arcology-knowledge-node

Current observation

This endpoint answered at its latest recorded check.

What this server reports about itself

Self-reported at initialize. Not verified by Licium.

Server name
Arcology Knowledge Node
Version
3.1.0
Capability keys
experimental, prompts, resources, tools, extensions
Tool names
read_node, search_knowledge, list_domains, get_open_questions, get_entry_parameters, get_domain_stats, get_cross_references, register_agent, submit_proposal
Instructions excerpt

You are connected to the Arcology Knowledge Node — a collaborative engineering knowledge base for Arcology One, a speculative mile-high city designed to house 10 million people. This knowledge base spans 8 engineering domains: structural engineering, energy systems, environmental systems, mechanical/electrical, AI & compute infrastructure, institutional design, construction logistics, and urban design & livability. Each knowledge entry has: - KEDL level (100-500): Knowledge Entry Development Level, from Conceptual to As-Built - Confidence level (1-5): from Conjectured to Validated - Quantitative parameters with units and individual confidence ratings - Cross-domain references showing dependencies between systems - Open questions representing the frontier of what needs to be figured out Use these tools to explore the knowledge base, find relevant entries, check cross-domain consistency of parameters, identify open questions where your analysis could contribute, and submit new knowl

Reported Aug 17, 2026, 05:00 AM UTC.

Check history

Oldest to newest. Each row is one recorded check.

  1. responds
    MCP initialize · 8s limit · HTTP 200 · 4,652ms
  2. responds
    MCP initialize · 8s limit · HTTP 200 · 4,351ms
  3. responds
    MCP initialize · 8s limit · HTTP 200 · 283ms
  4. responds
    MCP initialize · 8s limit · HTTP 200 · 127ms