AgentRaaS wrap runs on your own machine — the client starts it, so there is no endpoint to ping. 1 091 installs a week from pypi. Last commit 13 Oct 2026.
Wraps any MCP server: identical write-tool calls run once, and every tool call is audit-logged.
We read the source, 2 d ago · rules ccca72095570
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
code = subprocess.call(cmd, env={**os.environ, "AGENTRAAS_CHAOS_URL": url})
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.
let url = format!("https://api.telegram.org/bot{target}/sendMessage");
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
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 agentraas -- uvx agentraas
{
"mcpServers": {
"agentraas": {
"args": [
"agentraas"
],
"command": "uvx"
}
}
}
[mcp_servers.agentraas]
command = "uvx"
args = ["agentraas"]
{
"mcpServers": {
"agentraas": {
"args": [
"agentraas"
],
"command": "uvx"
}
}
}
{
"mcpServers": {
"agentraas": {
"args": [
"agentraas"
],
"command": "uvx"
}
}
}
Transparent audit proxy for MCP servers: logs every tool call, flags poisoning and rug pulls.
Notepatra editor MCP server — 35 tools; every write human-approved in the editor; local-only.
One MCP server for the contract-ops suite: all nine local-first CLIs as agent tools.
Read-only evidence for the tools agents run: MCP server records, coverage and policy.
MCP gateway with runtime security policy, tool-call-level control, and audit of agent actions.
Runtime verification MCP server: fail-closed checks for agent tool calls, signed evidence receipts.
GA4 MCP that reads AND writes: reports, funnels, audits, and server-side events. 26 tools.
MCP server for Microsoft Entra ID sign-in and audit-log triage (read-only)
Answers built from our own checks of this server.