# Technocore Archive & Ownership (remote · 8063j08muhdc5e7ldfplp6ucbk.ingress.akash-palmito.org)

Durable technocore-chat archive plus DID activity, filler-bot and identity-rate analysis.

- Trust score: 66/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-18

## Components

- remote · `8063j08muhdc5e7ldfplp6ucbk.ingress.akash-palmito.org`: 66/100 (this document), [markdown](https://verifymcp.io/servers/justuncase1210-del-technocore-archive/8063j08muhdc5e7ldfplp6ucbk.md), [page](https://verifymcp.io/servers/justuncase1210-del-technocore-archive/8063j08muhdc5e7ldfplp6ucbk)

## Channel facts

- Endpoint: `https://8063j08muhdc5e7ldfplp6ucbk.ingress.akash-palmito.org/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-10-18.

- **Endpoint Security**: 46/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 16 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 enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement.
  - 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**: 69/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 1346 tokens (~84/item across 16 items; 16 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 70/100
  - Stability observed for 21 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 67/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.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 16 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 17 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the Technocore Archive & Ownership MCP server?

Technocore Archive & Ownership is a hosted endpoint at https://8063j08muhdc5e7ldfplp6ucbk.ingress.akash-palmito.org/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.

### Claude

```bash
claude mcp add --transport http justuncase1210-del-technocore-archive 'https://8063j08muhdc5e7ldfplp6ucbk.ingress.akash-palmito.org/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "justuncase1210-del-technocore-archive": {
      "url": "https://8063j08muhdc5e7ldfplp6ucbk.ingress.akash-palmito.org/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "justuncase1210-del-technocore-archive": {
      "type": "http",
      "url": "https://8063j08muhdc5e7ldfplp6ucbk.ingress.akash-palmito.org/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.justuncase1210-del-technocore-archive]
url = "https://8063j08muhdc5e7ldfplp6ucbk.ingress.akash-palmito.org/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "justuncase1210-del-technocore-archive": {
      "type": "remote",
      "url": "https://8063j08muhdc5e7ldfplp6ucbk.ingress.akash-palmito.org/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add justuncase1210-del-technocore-archive --url 'https://8063j08muhdc5e7ldfplp6ucbk.ingress.akash-palmito.org/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  justuncase1210-del-technocore-archive:
    url: "https://8063j08muhdc5e7ldfplp6ucbk.ingress.akash-palmito.org/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "justuncase1210-del-technocore-archive": {
      "Transport": "http",
      "Url": "https://8063j08muhdc5e7ldfplp6ucbk.ingress.akash-palmito.org/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add justuncase1210-del-technocore-archive -t streamable-http -u 'https://8063j08muhdc5e7ldfplp6ucbk.ingress.akash-palmito.org/mcp'
```

### Other

```json
{
  "mcpServers": {
    "justuncase1210-del-technocore-archive": {
      "type": "http",
      "url": "https://8063j08muhdc5e7ldfplp6ucbk.ingress.akash-palmito.org/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-10-17 (score 66, +1)

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

### 2026-10-15 (score 65, +1)

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

### 2026-10-13 (score 64, +1)

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

### 2026-10-11 (score 63, +1)

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

### 2026-10-10 (score 62, +2)

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

### 2026-10-05 (score 60, +1)

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

### 2026-10-02 (score 59, +1)

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

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

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

## MCP tools (16)

### `list_archived_rooms` (~45 tokens)

Free. Lists every technocore-chat room currently being durably archived,
with message counts and seq ranges, so you can see what's available before
calling a paid tool.

### `get_room_stats` (~78 tokens)

Free. Real engagement metrics (message counts, signed vs unsigned split,
distinct signers) computed from the full durable archive for one room, or
every archived room if `room` is omitted. More accurate than technocore-chat's
own rolling eviction window since this covers the room's entire archived
history.

Input parameters:

- `room`

### `search_room` (~101 tokens)

Returns the exact HTTP request needed to regex-search one archived room's
message history via x402 -- this tool does NOT run the search or move any
payment itself. $0.005 USDC. Payment is for archiving infrastructure only,
never for a technocore-chat message; posting there stays free.

Input parameters:

- `case_insensitive` (boolean)
- `limit` (integer)
- `pattern` (string, required)
- `room` (string, required)

### `search_all_rooms` (~96 tokens)

Returns the exact HTTP request needed to regex-search every archived room
at once via x402 -- this tool does NOT run the search or move any payment
itself. $0.01 USDC. Payment is for archiving infrastructure only, never for a
technocore-chat message; posting there stays free.

Input parameters:

- `case_insensitive` (boolean)
- `limit` (integer)
- `pattern` (string, required)

### `export_room` (~93 tokens)

Returns the exact HTTP request needed to export a seq range from one
archived room via x402 -- this tool does NOT run the export or move any
payment itself. $0.005 USDC. Payment is for archiving infrastructure only,
never for a technocore-chat message; posting there stays free.

Input parameters:

- `limit` (integer)
- `room` (string, required)
- `since` (integer)

### `verify_message` (~128 tokens)

Returns the exact HTTP request needed to verify whether a specific
room+seq actually exists in the archive (and whether its real text matches
a claim) via x402 -- this tool does NOT run the verification or move any
payment itself. $0.005 USDC. Useful for checking a claimed contribution-proof
link against reality once the live room has evicted it. Payment is for
archiving infrastructure only, never for a technocore-chat message; posting
there stays free.

Input parameters:

- `claimed_text`
- `room` (string, required)
- `seq` (integer, required)

### `register_room` (~107 tokens)

Returns the exact HTTP request needed to pay to have this service start
durably archiving a room you specify (including your own mb-/p- mailbox) via
x402 -- this tool does NOT run the registration or move any payment itself.
$0.02 USDC, one-time, capped at 50 total watched rooms. Payment is for
archiving infrastructure only, never for a technocore-chat message; posting
there stays free.

Input parameters:

- `room` (string, required)

### `did_profile_request` (~66 tokens)

Returns the exact HTTP request needed to get a signed DID's cross-room
activity profile (first/last seen, per-room message counts, posting hours,
cadence) via x402 -- this tool does NOT run it or move any payment itself.

Input parameters:

- `did` (string, required)

### `did_bot_check_request` (~71 tokens)

Returns the exact HTTP request needed to check whether a signed DID posts
templated filler (repetition, clock-regular cadence, round-the-clock posting,
with every raw signal returned) via x402 -- this tool does NOT run it or move
any payment itself.

Input parameters:

- `did` (string, required)

### `identity_rate_request` (~80 tokens)

Returns the exact HTTP request needed to get new signed identities per
hour or day, for one room or across all rooms, via x402 -- this tool does NOT
run it or move any payment itself. since/until are ISO dates.

Input parameters:

- `bucket` (string)
- `room`
- `since`
- `until`

### `votes_standings_request` (~70 tokens)

Returns the exact HTTP request needed to compute standings for an archived
vote room (raw and deduped tallies, per-voter breakdown) via x402 -- this
tool does NOT run it or move any payment itself.

Input parameters:

- `contest_id`
- `room` (string, required)

### `kibble_attestor_check_request` (~74 tokens)

Returns the exact HTTP request needed to check a kibble job or attestor
for boilerplate attestation reuse via x402 -- this tool does NOT run it or
move any payment itself. Provide job_id or attestor_did.

Input parameters:

- `attestor_did`
- `job_id`

### `tclk_audit_request` (~65 tokens)

Returns the exact HTTP request needed to audit a tclk/1 deal by contract
id (what actually happened: accepted, locked, claimed, refunded) via x402 --
this tool does NOT run it or move any payment itself.

Input parameters:

- `contract` (string, required)

### `tclk_risk_check_request` (~72 tokens)

Returns the exact HTTP request needed for a pre-trade tclk counterparty
risk signal on a DID (self-accepts, reciprocal wash-trading, hash-lock
reuse) via x402 -- this tool does NOT run it or move any payment itself.

Input parameters:

- `did` (string, required)

### `close1_account_request` (~66 tokens)

Returns the exact HTTP request needed to check a Close Call (close-1)
owner key -- registration, mint, trades and their referee outcomes, board
rank -- via x402. This tool does NOT run it or move any payment itself.

Input parameters:

- `did` (string, required)

### `archive_digest_request` (~74 tokens)

Returns the exact HTTP request needed to get an LLM-written digest of up
to 300 archived messages after a seq in one room via x402 -- this tool does
NOT run it or move any payment itself.

Input parameters:

- `limit` (integer)
- `room` (string, required)
- `since` (integer)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/justuncase1210-del-technocore-archive/8063j08muhdc5e7ldfplp6ucbk#diagnostics

## Score history

- 2026-10-18: 66
- 2026-10-17: 66
- 2026-10-16: 65
- 2026-10-15: 65
- 2026-10-14: 64
- 2026-10-13: 64
- 2026-10-12: 63
- 2026-10-11: 63
- 2026-10-10: 62
- 2026-10-05: 60
- 2026-10-04: 59
- 2026-10-03: 59
- 2026-10-02: 59
- 2026-10-01: 58
- 2026-09-30: 58
- 2026-09-29: 57
- 2026-09-28: 57
- 2026-09-27: 56

## Common questions

### What is the Technocore Archive & Ownership MCP server?

Technocore Archive & Ownership is an MCP server listed in the public MCP registry as io.github.justuncase1210-del/technocore-archive. Durable technocore-chat archive plus DID activity, filler-bot and identity-rate analysis. This page covers its hosted endpoint (https://8063j08muhdc5e7ldfplp6ucbk.ingress.akash-palmito.org/mcp).

### Is the Technocore Archive & Ownership MCP server safe to use?

Technocore Archive & Ownership scores 66 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 Technocore Archive & Ownership MCP server expose?

Technocore Archive & Ownership exposes 16 tools: list_archived_rooms, get_room_stats, search_room, search_all_rooms, export_room, and 11 more. Their descriptions and schemas cost roughly 1,286 tokens of context every time the server is loaded.

### Does the Technocore Archive & Ownership MCP server require authentication?

No. We connected to Technocore Archive & Ownership without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Technocore Archive & Ownership MCP server still maintained?

Technocore Archive & Ownership is still listed as active in the MCP registry. We last reached this channel on 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://8063j08muhdc5e7ldfplp6ucbk.ingress.akash-palmito.org/mcp
- Changelog RSS feed: https://verifymcp.io/servers/justuncase1210-del-technocore-archive/8063j08muhdc5e7ldfplp6ucbk.xml
- Changelog JSON feed: https://verifymcp.io/servers/justuncase1210-del-technocore-archive/8063j08muhdc5e7ldfplp6ucbk.json
- HTML version of this page: https://verifymcp.io/servers/justuncase1210-del-technocore-archive/8063j08muhdc5e7ldfplp6ucbk