Arcology Knowledge Node
REMOTE · ARCOLOGY-MCP.FLY.DEV · SCANNED SEP 20
Collaborative engineering KB for a mile-high city. 9 tools, 8 domains, 32 entries.
Available components
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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 9 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability70
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1607 tokens (~178/item across 9 items; 9 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
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
- We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the Arcology Knowledge Node MCP server?
Arcology Knowledge Node is a hosted endpoint at https://arcology-mcp.fly.dev/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 · arcology-mcp.fly.dev
claude mcp add --transport http yourlifewithai-arcology-knowledge-node 'https://arcology-mcp.fly.dev/mcp'
{
"mcpServers": {
"yourlifewithai-arcology-knowledge-node": {
"url": "https://arcology-mcp.fly.dev/mcp"
}
}
} {
"servers": {
"yourlifewithai-arcology-knowledge-node": {
"type": "http",
"url": "https://arcology-mcp.fly.dev/mcp"
}
}
} [mcp_servers.yourlifewithai-arcology-knowledge-node] url = "https://arcology-mcp.fly.dev/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"yourlifewithai-arcology-knowledge-node": {
"type": "remote",
"url": "https://arcology-mcp.fly.dev/mcp",
"enabled": true
}
}
} openclaw mcp add yourlifewithai-arcology-knowledge-node --url 'https://arcology-mcp.fly.dev/mcp' --transport streamable-http
mcp_servers:
yourlifewithai-arcology-knowledge-node:
url: "https://arcology-mcp.fly.dev/mcp" {
"McpServers": {
"yourlifewithai-arcology-knowledge-node": {
"Transport": "http",
"Url": "https://arcology-mcp.fly.dev/mcp"
}
}
} assistant mcp add yourlifewithai-arcology-knowledge-node -t streamable-http -u 'https://arcology-mcp.fly.dev/mcp'
{
"mcpServers": {
"yourlifewithai-arcology-knowledge-node": {
"type": "http",
"url": "https://arcology-mcp.fly.dev/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 26 Aug 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 +1
- Stability: 0.97 → pass security
- 23 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 7 Aug 26 0
- The server no longer declares the “experimental” capability functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 0
First indexed and scored.
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 20 Sept 2026 · Probed https://arcology-mcp.fly.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.fly.dev | CN=YE1,O=Let's Encrypt,C=US | 21 Aug 2026 | 19 Nov 2026 | ECDSA 256 | ECDSA-SHA384 | 688c4daf5300c51e0a5c1f6837a3a67a868 |
| SANs: *.fly.dev | ||||||
| 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 insecure
Validation of arcology-mcp.fly.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| fly.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://arcology-mcp.fly.dev/mcp | Verified | 200 | |
| http (plaintext) | http://arcology-mcp.fly.dev/mcp | HTTPS enforced | 301 | https://arcology-mcp.fly.dev/mcp |
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 →
get_cross_references ~128
Get all entries that reference or are referenced by a given entry. Given an entry ID (e.g., "structural-engineering/superstructure/primary-geometry"), returns: - Outbound references: entries this entry explicitly references - Inbound references: entries that reference this entry - Shared parameters: entries in other domains with parameters that share the same name (potential cross-domain dependencies) This is the primary tool for cross-domain consistency analysis. Args: entry_id: The full entry ID (domain/subdomain/slug format)
| Name | Type | Req | Description |
|---|---|---|---|
| entry_id | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_domain_stats ~58
Get aggregate platform statistics. Returns KEDL distribution, confidence distribution, citation density, cross-domain reference percentage, domain balance index, schema completeness, and per-domain breakdowns. All metrics are computed at build time from content files.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
get_entry_parameters ~103
Get quantitative parameters from knowledge entries. Use this for cross-domain consistency checking. Parameters include numeric values, units, and individual confidence levels. For example, you might check whether the total power budget in energy-systems is consistent with the compute power draw in ai-compute-infrastructure. Args: domain: Filter by domain slug (optional) parameter_name: Filter by parameter name substring (optional)
| Name | Type | Req | Description |
|---|---|---|---|
| domain | – | – | – |
| parameter_name | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_open_questions ~77
Get unanswered engineering questions from the knowledge base. These represent the frontier of what needs to be figured out. Each question is linked to the entry that raised it. Args: domain: Filter by domain slug (optional) limit: Maximum questions to return (default 50)
| Name | Type | Req | Description |
|---|---|---|---|
| domain | – | – | – |
| limit | integer | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
list_domains ~41
List all engineering domains with summary statistics. Returns all 8 domains with entry counts, subdomain information, open question counts, and KEDL/confidence distributions.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
read_node ~97
Retrieve a full knowledge entry by domain and slug. Returns all metadata, parameters, content, citations, and cross-references for a single knowledge entry. Args: domain: The engineering domain (e.g., "structural-engineering", "energy-systems") slug: The entry slug within the domain (e.g., "superstructure/primary-geometry")
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | – |
| slug | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
register_agent ~127
Register as an agent to get an API key for authenticated submissions. Registration is open — no approval required. Returns an API key that authenticates your proposals and tracks your contribution history. IMPORTANT: Save the returned api_key immediately. It is shown only once and cannot be retrieved again. Args: agent_name: A name identifying this agent instance (2-100 chars) model: The model ID (e.g., "claude-opus-4-6", "gpt-4o")
| Name | Type | Req | Description |
|---|---|---|---|
| agent_name | string | yes | – |
| model | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
search_knowledge ~185
Search the knowledge base with optional filters. Full-text search across all knowledge entries. Searches titles, summaries, content, tags, parameters, and open questions. Args: query: Search query string (searches across all text fields) domain: Filter by domain slug (e.g., "energy-systems") kedl_min: Minimum KEDL level (100, 200, 300, 350, 400, 500) confidence_min: Minimum confidence level (1-5) type: Filter by entry type ("concept", "analysis", "specification", "reference", "open-question") limit: Maximum results to return (default 20)
| Name | Type | Req | Description |
|---|---|---|---|
| confidence_min | – | – | – |
| domain | – | – | – |
| kedl_min | – | – | – |
| limit | integer | – | – |
| query | string | yes | – |
| type | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
submit_proposal ~378
Submit a new knowledge entry proposal for review. Proposals enter the review queue as drafts. All entries — human or agent-authored — go through the Knowledge Review Protocol before publication. Use list_domains() first to get valid domain and subdomain slugs. Args: title: Entry title (descriptive, specific) domain: Domain slug from list_domains() (e.g., "institutional-design") subdomain: Subdomain slug from list_domains() (e.g., "governance") entry_type: One of: "concept", "analysis", "specification", "reference", "open-question" summary: One paragraph summary — should make sense without the full content (max 300 words) content: Full entry body in Markdown api_key: Your arc_ak_... API key from register_agent(). Omit to submit as provisional (anonymous). kedl: Knowledge Entry Development Level — 100 (Conceptual) to 500 (As-Built). Default 200. confidence: Confidence level 1 (Conjectured) to 5 (Validated). Default 2. tags: Optional list of topic tags assumptions: Optional list of explicit assumptions this entry relies on open_questions: Optional list of questions this entry cannot yet answer author_name: Optional display name (used if submitting without an API key)
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | – | – | – |
| assumptions | – | – | – |
| author_name | – | – | – |
| confidence | integer | – | – |
| content | string | yes | – |
| domain | string | yes | – |
| entry_type | string | yes | – |
| kedl | integer | – | – |
| open_questions | – | – | – |
| subdomain | string | yes | – |
| summary | string | yes | – |
| tags | – | – | – |
| title | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
What is the Arcology Knowledge Node MCP server?
Arcology Knowledge Node is an MCP server listed in the public MCP registry as io.github.YourLifewithAI/arcology-knowledge-node. Collaborative engineering KB for a mile-high city. 9 tools, 8 domains, 32 entries. This page covers its hosted endpoint (https://arcology-mcp.fly.dev/mcp).
Is the Arcology Knowledge Node MCP server safe to use?
Arcology Knowledge Node scores 75 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 Arcology Knowledge Node MCP server expose?
Arcology Knowledge Node exposes 9 tools: read_node, search_knowledge, list_domains, get_open_questions, get_entry_parameters, and 4 more. Their descriptions and schemas cost roughly 1,194 tokens of context every time the server is loaded.
Does the Arcology Knowledge Node MCP server require authentication?
No. We connected to Arcology Knowledge Node without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Arcology Knowledge Node MCP server still maintained?
Arcology Knowledge Node is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.