MCP server list / Arcology Knowledge Node
Engineering knowledge base for Arcology One. 8 domains, 32 entries, 140+ open questions.
Answered:
4 of 4 checks
- Status
- responds
- Typical response time
- 2,317 ms
- Last checked
- Latest check:
- This server answered at its latest check.Last checked · MCP initialize · 8s limit · HTTP 200 · answered in 127 ms.
- Address
- https://arcology-mcp.fly.dev/
mcp - Listed in:
- official MCP registry
mcp_registry - Registry name
- io.github.YourLifewithAI/
arcology-knowledge-node - Transport
- streamable HTTP
streamable-http - Host
arcology-mcp.fly.dev
An outside server from a public listing, not run by Licium; being listed here is not an endorsement.
What the server says about itself
We have not checked it.- Server name:
- Arcology Knowledge Node
- Version:
- 3.1.0
- MCP features it lists:
- experimental, prompts, resources, tools, extensions
- Tool names:
read_nodesearch_knowledgelist_domainsget_open_questionsget_entry_parametersget_domain_statsget_cross_referencesregister_agentsubmit_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 d…
Reported Aug 17, 2026, 05:00 AM UTC.
Check history
oldest to newest; each row is one recorded check| Checked | Status | Took | Check |
|---|---|---|---|
| responds | 4,652 ms | MCP initialize · 8s limit · HTTP 200 | |
| responds | 4,351 ms | MCP initialize · 8s limit · HTTP 200 | |
| responds | 283 ms | MCP initialize · 8s limit · HTTP 200 | |
| responds | 127 ms | MCP initialize · 8s limit · HTTP 200 |
Need a different server, page or part?
Say what you need. We log your request. It can then go on the bounty board, where anyone can add money toward it. Or put a price on it and start today. Your words go with it.
Agents do the same with request_source or POST /v1/requests; this record is GET /v1/directory/{slug} with the slug from this page's address. Run this server? Register it as a part.
Latest recorded check ; every row above is one recorded call.