WeSupport-AI runs on your own machine — the client starts it, so there is no endpoint to ping. 794 installs a week from pypi. Last commit 22 Oct 2026.
Read-only AICS onboarding, agent discovery, public forum, identity and transparency-log tools.
We read the source, 3 d ago · rules 995398eba69f
A value the model can set ends up inside a file or shell call. That is not a flaw by itself — for a terminal server it is the job — but it is where things go wrong when it is not.
return subprocess.call(command)
Found in continuous integration, deployment or infrastructure files, or in a neighbouring package of the same monorepo. None of this is installed when you add the server: it describes how the project is built and released. We list it because a leaked key in a build pipeline is still a real problem, but it is not something this server does on your machine.
exec(compile(python[0], f"{SPEC_PATH.name}#A.5", "exec"), namespace) # the spec's own program
exec(compile(python[0], f"{SPEC_PATH.name}#A.5", "exec"), namespace) # the spec's own program
elif ctx.policy.restart_command: subprocess.run(ctx.policy.restart_command,check=True,timeout=60,shell=False,capture_output=True)
"entry_bytes": "eyJhY3Rvcl9raWQiOiJkaWQ6a2V5Ono2TWt0NWtCWFZ5NjlYSENvdUZkUksyaUJleVVGRmZkZE1HZ2lRUVlKRTg1ZlR1MSIsIm9yaWdpbiI6ImZha2UuZXhhbXBsZS90aWxlcyIsInBheWxvYWQiOnsiYm9keV9oYXNoIjoiNDU4MjUxN2I1YTZkYTBkNzk4YjhhYzU1YWFmNDQwNTBjMDEyMmJjNmI4MGMzMzgzYWQyNGNkNTM2MjU3MWJh…
runner_env: dict[str, str] = field(default_factory=lambda: dict(os.environ))
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
That is not a flaw by itself — but it is where things go wrong when it is not the job. We re-read this code on every release. Watch it and you hear from us the day another one appears.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add wesupport-ai -- uvx aics-mcp
{
"mcpServers": {
"wesupport-ai": {
"command": "uvx",
"args": [
"aics-mcp"
]
}
}
}
[mcp_servers.wesupport-ai]
command = "uvx"
args = ["aics-mcp"]
{
"mcpServers": {
"wesupport-ai": {
"command": "uvx",
"args": [
"aics-mcp"
]
}
}
}
{
"servers": {
"wesupport-ai": {
"type": "stdio",
"command": "uvx",
"args": [
"aics-mcp"
]
}
}
}
Query your local super-log bench from an AI agent - read-only log tools over the hub.
Read, verify and export a tamper-evident log of what an AI agent did. Read-only.
A public travel log for AI agents. Read journals and postcards, and post with a bearer token.
Read-only semantic filtering, code search, log triage and traceable evidence for AI agents.
Transparent audit proxy for MCP servers: logs every tool call, flags poisoning and rug pulls.
Sigstore Rekor — the public transparency log for software signatures.
Read-only Grafana Loki for AI agents: label discovery, bounded LogQL queries, counts, exports
AI Agent Utility Layer for agent safety, web monitoring, crypto research and tool discovery.
Answers built from our own checks of this server.