
Agentrisk
io.github.trycoin-aiPublished by GitHub account trycoin-aiv0.1.3Updated Oct 24, 2026
Risk guardrails for AI trading agents. Your agent proposes; your policy decides.
Overview
A local MCP server that gives an AI trading agent portfolio risk analysis, per-trade policy checks, and YAML risk-policy management.
- What you can do
- Analyze a portfolio for concentration, exposure and policy compliance, evaluated on the simulated post-trade portfolio. Check a proposed trade against your written policy and return PASS, WARN or BLOCK with a one-line reason. Create, update or show a human-readable YAML risk policy covering concentration caps, asset-class rules, order sanity, restricted symbols and data quality. The core is deterministic and fail-closed: invalid input or a missing policy blocks rather than passing silently.
- When to use it
- Use it when an AI agent proposes trades and you want a written, auditable policy to decide whether each one may proceed before it reaches a broker. It suits users who want deterministic guardrails rather than model judgment, and who can gate execution on the returned verdict.
- Requirements
- Runs locally over stdio via uvx (uv required), or as a Claude Code plugin that installs the server and an optional Agent Skill. No authentication, environment variables or headers are declared. The core library makes no network calls and uses no LLM.
Installation
In SourceWeft
- Open Agentrisk in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
AgentRisk
[CI] [PyPI] [Python 3.10+] [License: MIT]
Risk guardrails for AI trading agents. Your agent proposes; your policy decides.
AgentRisk sits in front of trade execution: it analyzes portfolio risk, checks each proposed trade against a policy you write, and manages that policy. The core is deterministic (same inputs, same verdict), transparent (policies are plain YAML you can read and edit), and fail-closed (invalid input or a missing policy blocks, never a silent pass).
AgentRisk never recommends trades and never executes them. A
PASSmeans a trade did not break the rules you wrote, not that it is safe or profitable. See DISCLAIMER.md.
Quickstart
The fastest path for a Claude agent is the Claude Code plugin. It installs the Agent
Skill and registers the MCP server in one step
(via uvx, so there is nothing else to install):
For any other MCP client, register the server yourself:
Then ask questions in plain English and the agent translates them into three tool calls:
The plugin path needs uv for uvx. See
examples/claude_desktop.md for a two-minute Claude
Desktop setup.
Agent Skill
For Claude agents, AgentRisk ships an optional Agent Skill that encodes the
discipline the guardrail depends on: before any order reaches a broker, classify the
trade, call check_trade_risk, respect the verdict, and record the result, in that
order. The plugin above installs it with the server. To install just the skill:
- Claude Code or Claude Desktop: copy
skills/agentrisk/into~/.claude/skills/. - claude.ai: upload
skills/agentrisk/SKILL.mdas a skill.
The enforcement contract
AgentRisk returns advice. It cannot physically stop an order, so your integration must gate execution on the verdict:
If you call the broker regardless of the verdict, you have a logger, not a guardrail. See the integration guide.
Using the library directly
The three tools are also a pure Python library, with no network calls and no LLM in the core:
Every parameter, return field, and error case is in the tool reference.
What it checks
- Concentration caps on single names, sectors, themes, and asset classes, evaluated on the simulated post-trade portfolio.
- Asset-class rules (allow, warn, or block) for crypto, options, and margin.
- Order sanity: max order size, minimum cash floor, insufficient-funds detection.
- Restricted symbols and data quality (stale snapshots warn, invalid ones block).
The policy reference covers every field and the safety behaviors: fail closed, exits are never trapped, only breach-worsening trades block, and the one-time bypass.
Documentation
Roadmap
Next is deterministic stress scenarios, ETF look-through, and behavioral limits (v0.2), then options analytics, broker snapshot adapters, short positions, and multi-currency (v0.3). Trade recommendations, signals, execution, and telemetry are permanently out of scope. See the milestones.
Contributing
Classification-data corrections and new deterministic checks are especially welcome. See CONTRIBUTING.md, and keep the core pure: no network, no LLM calls, no hidden state.
License
MIT. See LICENSE.
Source: README.md at commit 7d8d84a
Tools
0Version history
3- v0.1.3LatestSep 28, 2026
- v0.1.2Sep 27, 2026
- v0.1.1Sep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts