Technocore Archive & Ownership
REMOTE · 8063J08MUHDC5E7LDFPLP6UCBK.INGRESS.AKASH-PALMITO.ORG
Durable technocore-chat archive plus DID activity, filler-bot and identity-rate analysis.
Available components
Last scanned (9 hours ago)
Scores higher than 56% of remote servers
Reachable. Last reached 18 Oct 2026.
Category Search and Retrieval
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 Security46
- 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 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. See how to fix → View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- 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 Usability69
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1346 tokens (~84/item across 16 items; 16 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management70
- Stability observed for 21 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 16 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 17 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
- 17 Oct 26 +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.
- 15 Oct 26 +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.
- 13 Oct 26 +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.
- 11 Oct 26 +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.
- 10 Oct 26 +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.
- 5 Oct 26 +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.
- 2 Oct 26 +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.
- 30 Sept 26 +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.
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 18 Oct 2026 · Probed https://8063j08muhdc5e7ldfplp6ucbk.ingress.akash-palmito.org/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.akash-palmito.org | CN=YR2,O=Let's Encrypt,C=US | 1 Sept 2026 | 30 Nov 2026 | RSA 2048 | SHA256-RSA | 5a0aed914ecec11cbdfd26546e653f90785 |
| SANs: *.akash-palmito.org, *.ingress.akash-palmito.org | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of 8063j08muhdc5e7ldfplp6ucbk.ingress.akash-palmito.org. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| org. | present | 26974 | 8 | Verified |
| akash-palmito.org. | 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://8063j08muhdc5e7ldfplp6ucbk.ingress.akash-palmito.org/mcp | Verified | 200 | |
| http (plaintext) | http://8063j08muhdc5e7ldfplp6ucbk.ingress.akash-palmito.org/mcp | Inconclusive | 406 |
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 →
archive_digest_request ~74
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| room | string | yes | – |
| since | integer | – | – |
No output schema declared.
No examples provided.
close1_account_request ~66
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.
| Name | Type | Req | Description |
|---|---|---|---|
| did | string | yes | – |
No output schema declared.
No examples provided.
did_bot_check_request ~71
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.
| Name | Type | Req | Description |
|---|---|---|---|
| did | string | yes | – |
No output schema declared.
No examples provided.
did_profile_request ~66
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.
| Name | Type | Req | Description |
|---|---|---|---|
| did | string | yes | – |
No output schema declared.
No examples provided.
export_room ~93
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| room | string | yes | – |
| since | integer | – | – |
No output schema declared.
No examples provided.
get_room_stats ~78
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.
| Name | Type | Req | Description |
|---|---|---|---|
| room | – | – | – |
No output schema declared.
No examples provided.
identity_rate_request ~80
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.
| Name | Type | Req | Description |
|---|---|---|---|
| bucket | string | – | – |
| room | – | – | – |
| since | – | – | – |
| until | – | – | – |
No output schema declared.
No examples provided.
kibble_attestor_check_request ~74
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.
| Name | Type | Req | Description |
|---|---|---|---|
| attestor_did | – | – | – |
| job_id | – | – | – |
No output schema declared.
No examples provided.
list_archived_rooms ~45
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
register_room ~107
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.
| Name | Type | Req | Description |
|---|---|---|---|
| room | string | yes | – |
No output schema declared.
No examples provided.
search_all_rooms ~96
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.
| Name | Type | Req | Description |
|---|---|---|---|
| case_insensitive | boolean | – | – |
| limit | integer | – | – |
| pattern | string | yes | – |
No output schema declared.
No examples provided.
search_room ~101
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.
| Name | Type | Req | Description |
|---|---|---|---|
| case_insensitive | boolean | – | – |
| limit | integer | – | – |
| pattern | string | yes | – |
| room | string | yes | – |
No output schema declared.
No examples provided.
tclk_audit_request ~65
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.
| Name | Type | Req | Description |
|---|---|---|---|
| contract | string | yes | – |
No output schema declared.
No examples provided.
tclk_risk_check_request ~72
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.
| Name | Type | Req | Description |
|---|---|---|---|
| did | string | yes | – |
No output schema declared.
No examples provided.
verify_message ~128
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.
| Name | Type | Req | Description |
|---|---|---|---|
| claimed_text | – | – | – |
| room | string | yes | – |
| seq | integer | yes | – |
No output schema declared.
No examples provided.
votes_standings_request ~70
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.
| Name | Type | Req | Description |
|---|---|---|---|
| contest_id | – | – | – |
| room | string | yes | – |
No output schema declared.
No examples provided.
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.
remote · 8063j08muhdc5e7ldfplp6ucbk.ingress.akash-palmito.org
claude mcp add --transport http justuncase1210-del-technocore-archive 'https://8063j08muhdc5e7ldfplp6ucbk.ingress.akash-palmito.org/mcp'
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.