Murre gives agents one system for research, portfolio construction, monitoring, and guarded execution. The account, mandate, session limits, and venue credentials remain outside the model.
Callable MCP serverPaper by defaultGuarded Robinhood bridge
research · construct · monitor · execute
One portfolio layer · two planes
A full portfolio loop with a hard execution boundary.
Murre is growing into the layer an agent calls to understand a portfolio, form a view, build targets, watch risk, and act. The mandate is the foundation that keeps that broader loop under operator-defined authority.
01Intelligence plane
Operate the portfolio.
Agents and deterministic models bring evidence into the system, form views, construct target books, and watch the portfolio between decisions.
Research and account-aware context
Portfolio construction and rebalance proposals
Drift, event, and order-state monitoring
Growing surface · never receives venue credentials
02Authority plane
Keep the operator in control.
A deterministic engine evaluates the portfolio, binds approval to the exact order, and gives the credentialed relay only the authority that survived policy.
Fixed account, policy, and session ceilings
Single-use exact-order execution permits
Replay protection and inspectable receipts
Foundation · enforced by the current runtime
The portfolio layer
Research, construct, monitor, execute.
The goal is one callable layer for the full portfolio loop. Some capabilities work today; others are being built in public behind the same operator-controlled boundary.
01
RESEARCH
Bring evidence into the decision.
Connect market, asset, and account context so an agent can explain what it sees before it proposes a position.
Early workflow · adapters next
02
CONSTRUCTION
Turn views into a portfolio.
Translate scores and target weights into bounded rebalance proposals that still pass through the same policy kernel.
Paper cycle · working
03
MONITORING
Keep the book tied to reality.
Read status and event history, track remaining authority, surface drift, and reconcile the next decision against fresh state.
Status + ledger · reconciliation next
04
EXECUTION
Route only the exact allowed action.
Review the order, consume its permit, and submit through Robinhood MCP without exposing the account or credentials to the agent.
It is not the whole product. It is the part that lets research, construction, monitoring, and execution share one system without giving the calling model unchecked authority. Agents submit intents; Murre returns a denial or a permit bound to the exact action.
01
One execution pathThe credentialed relay is the only component allowed to reach the venue.
02
Order-bound authorityChange the amount, asset, price, account, or route and the permit becomes invalid.
03
Inspectable proofEvery approval, denial, fill, and revocation becomes a replayable receipt.
authorization.traceprotocol specimen
agent→murre mcp→policy→robinhood mcp
intent
side BUY
asset PRIVATE_AI
amount $50,000
account fund-01
policy
id private-growth-v1
maxPosition 25.0%
decision
result DENIED
observed 29.0%
rule max_position
permit null
Asset coverage
One book. Different proofs.
Every asset class needs its own eligibility and settlement evidence. Murre should share one authorization model without pretending the underlying assets are interchangeable.
Public + tokenized equities
The current guarded bridge supports long public-equity limit orders. Canonical token contracts, jurisdiction, market status, and settlement evidence come next.
Equity bridge experimental
Private assets
Issuer authority, investor eligibility, transfer restrictions, valuation age, custody, and exit liquidity.
Robinhood MCP is available as an experimental, explicitly armed equity-order adapter. Robinhood Chain registry and settlement adapters remain future work. Murre is independent and not affiliated with Robinhood. Availability and eligibility vary by jurisdiction.
Build status
Working now. Expanding deliberately.
Murre is already callable infrastructure for policy, paper portfolios, event history, and guarded Robinhood execution. The broader portfolio layer is being added without pretending planned features are live.
Working
Callable MCP + deterministic portfolio kernel
Status, policy checks, paper orders, target-weight cycles, hash-chained events, and single-use exact-order permits.