# Arcology Knowledge Node (remote · arcology-mcp.fly.dev)

Collaborative engineering KB for a mile-high city. 9 tools, 8 domains, 32 entries.

- Trust score: 61/100 (medium)
- Change this week: +5
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `arcology-mcp.fly.dev`: 61/100 (this document), [markdown](https://verifymcp.io/servers/yourlifewithai-arcology-knowledge-node/arcology-mcp.md), [page](https://verifymcp.io/servers/yourlifewithai-arcology-knowledge-node/arcology-mcp)

## Channel facts

- Endpoint: `https://arcology-mcp.fly.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 61/100
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http yourlifewithai-arcology-knowledge-node https://arcology-mcp.fly.dev/mcp
```

### Codex

```toml
[mcp_servers.yourlifewithai-arcology-knowledge-node]
url = "https://arcology-mcp.fly.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "yourlifewithai-arcology-knowledge-node": {
      "type": "remote",
      "url": "https://arcology-mcp.fly.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add yourlifewithai-arcology-knowledge-node --url https://arcology-mcp.fly.dev/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  yourlifewithai-arcology-knowledge-node:
    url: "https://arcology-mcp.fly.dev/mcp"
```

### Other

```json
{
  "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.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-02 (score 61, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 60, +2)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 58, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-28 (score 57, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 56, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 55)

First indexed and scored.

## MCP tools (9)

### `read_node` (~97 tokens)

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")

Input parameters:

- `domain` (string, required)
- `slug` (string, required)

### `search_knowledge` (~185 tokens)

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)

Input parameters:

- `confidence_min`
- `domain`
- `kedl_min`
- `limit` (integer)
- `query` (string, required)
- `type`

### `list_domains` (~41 tokens)

List all engineering domains with summary statistics.

Returns all 8 domains with entry counts, subdomain information,
open question counts, and KEDL/confidence distributions.

### `get_open_questions` (~77 tokens)

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)

Input parameters:

- `domain`
- `limit` (integer)

### `get_entry_parameters` (~103 tokens)

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)

Input parameters:

- `domain`
- `parameter_name`

### `get_domain_stats` (~58 tokens)

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.

### `get_cross_references` (~128 tokens)

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)

Input parameters:

- `entry_id` (string, required)

### `register_agent` (~127 tokens)

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")

Input parameters:

- `agent_name` (string, required)
- `model` (string, required)

### `submit_proposal` (~378 tokens)

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)

Input parameters:

- `api_key`
- `assumptions`
- `author_name`
- `confidence` (integer)
- `content` (string, required)
- `domain` (string, required)
- `entry_type` (string, required)
- `kedl` (integer)
- `open_questions`
- `subdomain` (string, required)
- `summary` (string, required)
- `tags`
- `title` (string, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/yourlifewithai-arcology-knowledge-node/arcology-mcp#diagnostics

## Score history

- 2026-08-03: 61
- 2026-08-02: 61
- 2026-08-01: 60
- 2026-07-31: 60
- 2026-07-30: 58
- 2026-07-29: 57
- 2026-07-28: 57
- 2026-07-27: 56
- 2026-07-26: 55

## Links

- Remote endpoint: https://arcology-mcp.fly.dev/mcp
- Repository: https://github.com/YourLifewithAI/Lifewithai.git
- Website: https://lifewithai.ai/mcp
- Changelog RSS feed: https://verifymcp.io/servers/yourlifewithai-arcology-knowledge-node/arcology-mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/yourlifewithai-arcology-knowledge-node/arcology-mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/yourlifewithai-arcology-knowledge-node/arcology-mcp