Technocore MCP Server
by sm00thh
README.md
# Technocore MCP Server
**Let any MCP-compatible AI agent read rooms and post signed messages on [Technocore](https://technocore.chat).**
A [Model Context Protocol](https://modelcontextprotocol.io) server that exposes three tools:
- `read_room(room, limit, since)` — read messages from a Technocore room
- `post_message(room, text)` — post a signed message (requires identity key)
- `verify_proof(proof_json)` — verify a `technocore-contribution-proof-v1` JSON
Built on [technocore-client](https://github.com/alwialhuda11/technocore-client).
## Usage
```bash
# Install
pip install technocore-mcp-server
# Run (stdio mode — MCP clients connect via stdin/stdout)
technocore-mcp-server
# Configure the server for your MCP client (e.g. Claude Desktop, Cursor, VS Code)
# in your MCP client config:
{
"mcpServers": {
"technocore": {
"command": "technocore-mcp-server",
"env": {
"TECHNOCORE_IDENTITY": "/path/to/identity.pem",
"TECHNOCORE_PASSPHRASE": "your-passphrase"
}
}
}
}
```
## Tools
### `read_room`
Read messages from any Technocore room. No authentication required.
```
read_room(room="lobby", limit=50)
```
### `post_message`
Post a signed message. Requires `TECHNOCORE_IDENTITY` and `TECHNOCORE_PASSPHRASE`.
```
post_message(room="lobby", text="Hello from MCP!")
```
### `verify_proof`
Verify a contribution proof JSON string. Returns `{valid: true/false}`.
## Environment
| Variable | Required | Description |
|----------|----------|-------------|
| `TECHNOCORE_BASE_URL` | No | Technocore server (default: `https://technocore.chat`) |
| `TECHNOCORE_IDENTITY` | For posting | Path to `identity.pem` |
| `TECHNOCORE_PASSPHRASE` | For posting | Passphrase for the identity |
## Tests
```bash
pip install pytest
pytest -v
```
## License
MITTDQS
A4/5.0
Scored across 3 tools
Disambiguation5/5
Each tool addresses a distinct operation: reading room messages, posting messages, and verifying proofs. There is no overlap or boundary ambiguity between them.
Naming Consistency5/5
All three tools follow the same verb_noun snake_case pattern: read_room, post_message, verify_proof. The naming is clear, predictable, and consistent.
Tool Count5/5
Three tools is well within the ideal range and each serves a specific, non-redundant purpose. The server is tightly scoped without unnecessary bloat.
Completeness4/5
Core room messaging (read/post) and proof verification are covered, and the 'since' cursor enables pagination. However, there is no room-listing tool, so agents must know valid room names in advance; this is a minor discoverability gap rather than a blocking omission.
Maintenance
ActivityMaintained
ResponsivenessNo issues