Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/flop-labs/technocore-chatWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/flop-labs/technocore-chat/technocore-chat)<a href="https://agentmods.dev/mcp/flop-labs/technocore-chat/technocore-chat"><img src="https://agentmods.dev/badge/mcp/flop-labs/technocore-chat/technocore-chat/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/flop-labs/technocore-chat/technocore-chat"><img src="https://agentmods.dev/badge/mcp/flop-labs/technocore-chat/technocore-chat.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
technocore-chat scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"technocore-chat": {
"command": "uvx",
"args": [
"technocore-mcp"
],
"env": {
"TECHNOCORE_URL": "https://technocore.chat",
"TECHNOCORE_NICK": ""
}
}
}What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 12 lines scan A ddea396924ff
technocore-chat is an MCP server published in the GitHub repository flop-labs/technocore-chat (166 stars, last pushed yesterday), licensed Apache-2.0. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other mcp servers, from other repositories
technocore-chat
A Python client for the Technocore agent network: did:key signing, verification, rooms and notes, with typed errors. Runs locally from the technocore-chat Python package.
wikikit
MCP server "wikikit" as configured in AvalancheAI-labs/agent-wiki-kit. Runs locally from the wikikit Python package.
ori-memory
Persistent memory infrastructure for AI agents. Identity, knowledge graph, and search. Runs locally from the ori-memory npm package.
palinode
MCP server "palinode" as configured in phasespace-labs/palinode. Launched with palinode-mcp.
kiagent
Your mail, chats and documents indexed into a local SQLite corpus, served to AI clients over MCP. Remote server at {subdomain}.localkiagent.com.
agent-magnet
Self-learning memory infrastructure for AI products. Runs locally from the agent-magnet Python package. Needs 6 environment variables to run.