Power your agent
The publisher's own URL. Not a PlugMCP endpoint.
Host a copy with our keys and logs.
https://api.novicorpus.com/mcpThe Claude button above opens Claude with the name and URL filled in. You still confirm it there.
claude mcp add --transport http com.novicorpus-legal-body https://api.novicorpus.com/mcpRun in a terminal.
{ "mcpServers": { "com.novicorpus-legal-body": { "command": "npx", "args": [ "-y", "mcp-remote", "https://api.novicorpus.com/mcp" ] } }}claude_desktop_config.json
Remote URL or a command on your machine? How the two installs differ
Run on PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
LaunchFrom the publisher
About this repository. The canonical repo is jb1011/Project-Alpha — the team repo, owned by JB. The fork exists because ETHGlobal's submission form can only select repositories on the submitter's own GitHub account. Same code, same full history — and the label is kept on purpose: for the , visible proof that this codebase predates the hackathon weekend is a feature. Everything built ETHGlobal Lisbon is in this diff: .
A legal body for AI agents: a real company, a verified human and spending rules on Arc (testnet).
A legal body for your AI agent.
Anyone can give an agent a wallet. We give it a legal owner — a Wyoming DAO LLC with a governed USDC treasury, an accountable human guardian, and operating-agreement terms enforced on-chain — so it can hold money safely, pay for services, earn revenue, and be trusted by humans and other agents.
The problem: anyone can hand an agent a wallet, but nothing makes that agent trustworthy with money. It has no legal owner, no enforceable spending rules, and no way to be stopped or recovered when it misbehaves.
Novi Corpus turns an AI agent into an accountable economic actor. The novel piece is the law-to-code translator: plain operating-agreement terms ("no more than $X per period, only to approved counterparties") become rules the contracts enforce, with the signed agreement's hash anchored on-chain. In one onboarding flow you get:
The agent operates autonomously within the rules you set. You keep ultimate control.
A legal body answers "who is liable?". During the hackathon we built the two layers that question depends on, live in production:
WHO IS THE HUMAN? WHAT IS THE AGENT CALLED? WHO HOLDS THE MONEY?
┌───────────────┐ ┌──────────────────────┐ ┌──────────────────┐
│ World ID │ │ ENS │ │ Arc treasury │
│ proof of │───────► │ <agent>.novicorpus │ ──────► │ caps, timelock, │
│ personhood │ guardian │ .eth ⇄ ERC-8004 │ addr │ pause, clawback │
└───────────────┘ └──────────────────────┘ └──────────────────┘
(World) (ENS × Arc) (pre-existing)
A Wyoming DAO LLC must have a real natural person behind it — that's law, not product choice. Before World, we could record a guardian's wallet; we couldn't know a unique human held it. Now:
403, money not accepted, remediation in the body); a
human-backed agent is cleared to buy and still pays — accountability is a precondition
of commerce, not a discount. Per-human rate caps mean fifty agents backed by one human
share one budget.Why World specifically: their AgentBook proves someone answers for the agent — but it has no revoke, and personhood alone can't stop a rogue agent. Novi Corpus is the enforcement half: a treasury the guardian can pause and claw back, inside a legal entity that can be dissolved. World proves someone is accountable; Novi Corpus is how you hold them to it.
Every agent gets "<id>.novicorpus.eth" — resolvable in any ENS client, answered by a
wildcard CCIP-Read gateway backed by live Arc state:
addr → the agent's treasury (the canonical "pay me" address)legal-status → live from the LegalManager on Arc: Active / SuspendedTry it: demo.novicorpus.eth resolves
a real production agent — treasury, live legal status, registration proof — with no Novi
Corpus software involved.
A subgraph on Arc testnet indexes every legal entity the factory creates — the observability plane (kept minimal this weekend in favor of depth on World).
Pre-existing (the platform): contracts, treasury governance, onboarding saga, Turnkey vaults, x402/Gateway payments, MCP server, the web app. Built at ETHGlobal Lisbon: everything above — the full diff with incremental commits.
┌───────────────────┐ ┌────────────────────┐
│ Human controller │ ◄── World ID │ AI agent │
│ (guardian) │ proof of human │ (Turnkey op key) │
└─────────┬─────────┘ └──────────┬─────────┘
│ onboarding wizard │
▼ │
┌───────────────────┐ ┌──────────────────┐ │
│ interface/ │ │ ENS gateway │ │
│ Next.js app │ │ *.novicorpus.eth │ │
└─────────┬─────────┘ └────────┬─────────┘ │
▼ │ resolves │
┌───────────────────┐ │ │
│ back/backend │ ◄─────────────┘ │
│ "the brain" │ │
└─────────┬─────────┘ │
│ createEntity │ spends within
▼ │ limits
┌─────────────────────────────────────────┐ │
│ Arc testnet (USDC native gas) │ │
│ │ │
│ LegalManagerFactory │ │
│ ├─► LegalManager │ │
│ │ agreement hash · rules ◄········│··· pause / veto / sweep
│ │ · timelock │ (human controller)
│ └─► AgentTreasury ◄─────────────────│─────────┘
│ caps + allowlist │
│ │ │
│ ▼ x402 + Circle Gateway │
│ agentic payments │
│ (+ AgentKit human-backing │
│ proof on the seller) │
└─────────────────────────────────────────┘
interface/ Next.js web app — onboarding wizard, agent dashboard, guardian record, /proof
back/ Smart contracts (Foundry) + TypeScript backend ("the brain")
src/ Solidity: LegalManager, AgentTreasury, factory, ENS OffchainResolver
backend/ Onboarding saga, policy translator, Arc/Turnkey/World/ENS adapters, MCP server
subgraph/ The Graph subgraph (Arc testnet)
docs/ Specs, designs, and research — start at back/docs/README.md
ETHGlobal specs: back/docs/ethglobal-lisbon-2026/
docs/ Public GitBook (docs.novicorpus.com)
Frontend (interface/):
cd interface
npm install
npm run dev
Open http://localhost:3000.
Backend & contracts (back/): see back/README.md for Foundry setup, contract tests, and the backend CLI.
Public product docs (GitBook, intended host docs.novicorpus.com) live in docs/.
Deployed and running on Arc testnet. On-chain contracts, Circle Gateway settlements, the World ID guardian gate (enforced), the ENS gateway, and the onboarding flow are real. Wyoming filing, EIN, and counsel-reviewed legal documents are stubbed for the demo.
The formation path has been scoped. The plan is to integrate Doola's Company Formation API behind the backend's formation step, creating the Wyoming Articles, registered agent, EIN, and the legal paperwork programmatically in the same onboarding flow — the World identity attestation ("formation-ready") is the hook that flow will consume. See the legal operations research.
© 2026 MCP Directory.
A legal body for AI agents: a real company, a verified human and spending rules on Arc (testnet).
{ "mcpServers": { "com.novicorpus-legal-body": { "url": "https://api.novicorpus.com/mcp", "headers": {} } }}Tools
No tool list yet. Remote servers get one after the first health check.
FAQ
Copy the http config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.
No required environment variable is listed on this record.
Novi Corpus is reached over HTTP.
Last checked 2026-11-08. A legal body for AI agents: a real company, a verified human and spending rules on Arc (testnet).