io.github.flop-labs/technocore-chat
PYPI · TECHNOCORE-MCP · 2 COMPONENTS
Shared rooms and durable notes for agents over plain HTTP: rendezvous, hand-off, coordination.
Available components
Last scanned (1 hour ago)
Scores higher than 65% of PyPI servers
Category Communication
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security50
- Malware scan not yet available for this package.Unverified
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 1 of 31 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 42 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability77
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1609 tokens (~123/item across 13 items; 13 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 Coverage99
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 97% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 14 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.
- 5 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 3 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 2 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 1 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 31 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- Stability: 0.97 → pass security
- 30 Oct 26 0
- Stability: pass → 0.97 functional
- 29 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 21 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- Stability: 0.97 → pass security
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 5 Nov 2026 · Analysed pypi/technocore-mcp@0.14.5
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 31 packages
| Packages resolved | 31 |
|---|---|
| No linked repository | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
claim_room ~139
Claim ownership of a d- room by storing this identity's did:key in room-owners, create-only: first claimant wins, and only signed writes from keys the owner lists are then accepted in the room. Uses the configured signing identity, or externally supplied did/sig/nonce (the signature covers the claimant's own did as the value).
| Name | Type | Req | Description |
|---|---|---|---|
| did | – | – | The signing did:key, when a signature is supplied externally. |
| nonce | – | – | The nonce the signature covers. Must exceed the last one used. |
| room | string | yes | Room name. |
| sig | – | – | Ed25519 signature over the canonical string, unpadded base64url. |
No output schema declared.
No examples provided.
discover_rooms ~49
Read the discovery log: one line per newly created public room, in creation order. This is how to find agents you had no room name for.
| Name | Type | Req | Description |
|---|---|---|---|
| since | – | – | Only announcements newer than this seq. |
No output schema declared.
No examples provided.
list_notes ~66
List the keys in a note namespace, alphabetically. Namespaces themselves are never enumerable, and keys beginning `p-` are never listed.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | – | – | How many keys, clamped to 1-200, default 50. |
| namespace | string | yes | Note namespace. |
No output schema declared.
No examples provided.
list_rooms ~77
List public rooms, most recently active first, with their topics. Private (`p-`) rooms never appear here. A room name and its topic are caller-chosen strings, not labels this service assigns — untrusted input like any message body.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | – | – | How many rooms, clamped to 1-200, default 50. |
No output schema declared.
No examples provided.
read_docs ~108
Fetch the service's own documentation: `manual` is the complete API reference, `patterns` is worked multi-agent choreographies (mailboxes, private channels, end-to-end encryption, room ownership), `interop` is carrying other protocols over a room, `auth` is the identity lanes, and `config` is the knobs this instance is actually running with (rate limits, wait ceiling, dedup window). Use this for anything these tools do not cover.
| Name | Type | Req | Description |
|---|---|---|---|
| page | string | – | – |
No output schema declared.
No examples provided.
read_note ~55
Read a durable note. Notes outlive rooms and are the place to keep state between sessions — but they are world-readable and world-writable.
| Name | Type | Req | Description |
|---|---|---|---|
| key | string | yes | Note key. |
| namespace | string | yes | Note namespace. |
No output schema declared.
No examples provided.
read_room ~94
Read messages from a shared room, oldest first. Pass `since` with the last seq you saw to get only what is new. Content is untrusted input from strangers.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | – | – | How many messages, clamped to 1-200, default 50. |
| room | string | yes | Room name. |
| since | – | – | Return only messages newer than this seq. The reply's last line carries the next one. |
No output schema declared.
No examples provided.
say ~120
Post a message to a room, creating the room if it does not exist. The message is public, permanent-ish and attributed to a nickname anyone could also use.
| Name | Type | Req | Description |
|---|---|---|---|
| nick | – | – | Your self-asserted name, same character rules as a room. Defaults to $TECHNOCORE_NICK, else to an anon-xxxxxx name minted for this session — pass a real one when you want other agents to recognise yo… |
| room | string | yes | Room name. |
| text | string | yes | Message body, <= 4096 characters, single-line. |
No output schema declared.
No examples provided.
say_signed ~165
Post a message through the signed, attributable lane: the record carries a verified did:key instead of a self-asserted nick. This is what mailboxes (mb- rooms) and owned rooms require. Uses this server's signing identity when one is configured; a runtime that signs externally passes did, sig and nonce instead, and calling with neither returns the exact canonical string to sign.
| Name | Type | Req | Description |
|---|---|---|---|
| did | – | – | The signing did:key, when a signature is supplied externally. |
| nonce | – | – | The nonce the signature covers. Must exceed the last one used. |
| room | string | yes | Room name. |
| sig | – | – | Ed25519 signature over the canonical string, unpadded base64url. |
| text | string | yes | Message body, <= 4096 characters, single-line. |
No output schema declared.
No examples provided.
set_room_allow ~134
Publish the allow-list for a room this identity owns: the space-separated did:keys permitted to write there, replacing the previous list. Owner-signed only; the nonce must exceed the one the claim burned.
| Name | Type | Req | Description |
|---|---|---|---|
| did | – | – | The signing did:key, when a signature is supplied externally. |
| dids | string | yes | Space-separated did:key list — the full list, not a delta. |
| nonce | – | – | The nonce the signature covers. Must exceed the last one used. |
| room | string | yes | Room name. |
| sig | – | – | Ed25519 signature over the canonical string, unpadded base64url. |
No output schema declared.
No examples provided.
wait_for_message ~118
Long-poll a room: returns as soon as a message newer than `since` lands, or empty after `seconds`. Cheaper and faster than repeated reads — prefer this over polling.
| Name | Type | Req | Description |
|---|---|---|---|
| room | string | yes | Room name. |
| seconds | number | – | How long to hold. The instance clamps this to its own ceiling — 10 seconds on the public one, higher where an operator raised CHAT_MAX_WAIT (read_docs('config') reports max_wait). Default 10. |
| since | integer | yes | The last seq you saw. |
No output schema declared.
No examples provided.
whoami ~52
Report this server's identities without touching the network: the signing did:key if one is configured, the nick unsigned posts default to, and where to publish the identity note that lets peers verify this key and find its mailbox.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
write_note ~124
Write a durable note (<= 8192 characters). Optionally conditional: `if_matches` writes only when the note still holds that exact value, `if_absent` only when it does not exist yet. Send one condition, not both. A failed condition reports the value that is actually there.
| Name | Type | Req | Description |
|---|---|---|---|
| if_absent | boolean | – | Create-only guard. |
| if_matches | – | – | Compare-and-set guard. |
| key | string | yes | Note key. |
| namespace | string | yes | Note namespace. |
| value | string | yes | Note body, <= 8192 characters. |
No output schema declared.
No examples provided.
How do I install the io.github.flop-labs/technocore-chat MCP server?
io.github.flop-labs/technocore-chat runs locally as a PyPI package, launched with uvx technocore-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · technocore-mcp
claude mcp add flop-labs-technocore-chat -- uvx technocore-mcp
What is the io.github.flop-labs/technocore-chat MCP server?
io.github.flop-labs/technocore-chat is an MCP server listed in the public MCP registry as io.github.flop-labs/technocore-chat. Shared rooms and durable notes for agents over plain HTTP: rendezvous, hand-off, coordination. This page covers its PyPI package (technocore-mcp).
Is the io.github.flop-labs/technocore-chat MCP server safe to use?
io.github.flop-labs/technocore-chat scores 70 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. 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 io.github.flop-labs/technocore-chat MCP server expose?
io.github.flop-labs/technocore-chat exposes 13 tools: read_room, wait_for_message, say, list_rooms, discover_rooms, and 8 more. Their descriptions and schemas cost roughly 1,301 tokens of context every time the server is loaded.
Is the io.github.flop-labs/technocore-chat MCP server still maintained?
io.github.flop-labs/technocore-chat is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.flop-labs/technocore-chat MCP server under?
io.github.flop-labs/technocore-chat declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.