Prototype · Preview: every server in the official registry, synced every 30 minutes. Sign in with Google to write reviews.Prototype · updated every 30 min
PopNx MCPMCP servers for people who use AI · explained in plain words

Novi Corpus

✓ service owner · novicorpus.com

by jb1011version 1.0.0i★ 4 (Stars belong to another repo)iRuns in the cloudOfficial site ↗
Registry namecom.novicorpus/legal-body

How to install

What it does

A legal body for AI agents: a real company, a verified human and spending rules on Arc (testnet).

  • Connects Runs in the cloud
  • Account or key Needs Authorization
  • Category Law & government data

Why it ranks here

Lists are ordered by a usage score (out of 100) built from these parts

Popularity0/80GitHub stars or weekly downloads: the larger counts 60, the smaller 20
Freshness12/12Full marks for a release or code change within 30 days
Still answering8/8The cloud endpoint answered at the last check
Usage score20/100

Quality: Passed 1/5 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)

Install

Pick the AI app you use, then copy the settings.

Let your AI install it with one sentence

Please install Novi Corpus. Follow https://mcp.popnx.com/i/novicorpus-legal-body.md, show me the commands and wait for my OK before running them.

Paste it into an AI that can work on your computer (such as Claude Code or Cursor). It reads our steps, shows you the commands and waits for your OK. No key, no sign-up. · See the full text your AI reads

Passed 1/5 checks · What you ask goes through the maker’s server (api.novicorpus.com) · ✓ Commands checked Nov 13, 2026

First: which AI do you use?

Pick your app and the steps appear below.

Works with Claude · about 5 min

You need a Novi Corpus key (create it on the maker’s site) · Set it up once on claude.ai or the desktop app, then use it in chat · free accounts can add 1 · on Team/Enterprise an Owner adds it

  1. Sign up and create a Novi Corpus key

    Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.

    Open the Novi Corpus site ↗

  2. Open Claude’s Connectors page

    CustomizeConnectors

    CustomizeConnectors1Add2https://…3Add4
  3. Click “Add” → “Custom” → “Web” and fill in these 2 fields

    Copy each value into the field with the same name in Claude, then click Continue

    Name · NameNovi Corpus
    Remote MCP server URL · Addresshttps://api.novicorpus.com/mcp

    Under Request headers, add this name and value

    Header nameAuthorization
    ValueBearer <paste your key here>

    Paste the key only into the app’s field, never into a chat or to anyone

    Click Continue past the sign-in settings Claude detected · under Authentication choose what the maker says (Sign in now, Sign in when needed or No sign in), then click Add

  4. Turn it on in a chat

    +ConnectorsNovi Corpus

  5. Try it

    Use Novi Corpus and tell me what you can do for me, then show me one thing

    ✓ If Claude says it is using Novi Corpus or shows a Novi Corpus tool in the answer, you are connected

Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version

ChatGPT cannot connect Novi Corpus yet

Novi Corpus needs your own key to connect, but OpenAI’s help page only describes OAuth sign-in; there is no key option we could verify

What you can do instead

A · Use an app that can connect Novi Corpus

  • You need a Novi Corpus key (create it on the maker’s site) · Set it up once on claude.ai or the desktop app, then use it in chat · free accounts can add 1 · on Team/Enterprise an Owner adds it
  • You need a Novi Corpus key (create it on the maker’s site)
  • You need a Novi Corpus key (create it on the maker’s site)
  • You need a Novi Corpus key (create it on the maker’s site)

B · Others in Law & government data that work with ChatGPT

Picked from the most used in the same category, only ones that connect by address with no key

Works with Claude Code · about 5 min

You need a Novi Corpus key (create it on the maker’s site)

  1. Sign up and create a Novi Corpus key

    Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.

    Open the Novi Corpus site ↗

  2. Open Terminal

    Mac: press Command+Space and type Terminal · Windows: open PowerShell

  3. Paste this command and press Enter

    claude mcp add --transport http --scope user legal-body https://api.novicorpus.com/mcp --header 'Authorization: Bearer your-value'

    Replace “your-value” with your key before pressing Enter

    Paste the key only into the app’s field, never into a chat or to anyone

  4. Type /mcp in Claude Code

    You should see Novi Corpus listed as connected

  5. Try it

    Use Novi Corpus and tell me what you can do for me, then show me one thing

    ✓ If Claude Code says it is using Novi Corpus or shows a Novi Corpus tool in the answer, you are connected

Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Works with Cursor · about 5 min

You need a Novi Corpus key (create it on the maker’s site)

  1. Sign up and create a Novi Corpus key

    Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.

    Open the Novi Corpus site ↗

  2. Click this button to open Cursor

    Open in Cursor

    Cursor asks you to confirm; click Install

  3. Fill in your key

    In the Novi Corpus settings, Authorization is empty; add your key and save

    Paste the key only into the app’s field, never into a chat or to anyone

  4. Open the AI chat in Cursor in Agent mode

  5. Try it

    Use Novi Corpus and tell me what you can do for me, then show me one thing

    ✓ If Cursor says it is using Novi Corpus or shows a Novi Corpus tool in the answer, you are connected

Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Works with VS Code · about 5 min

You need a Novi Corpus key (create it on the maker’s site)

  1. Sign up and create a Novi Corpus key

    Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.

    Open the Novi Corpus site ↗

  2. Click this button to open VS Code

    Open in VS Code

    VS Code asks you to confirm; click Install

  3. Fill in your key

    In the Novi Corpus settings, Authorization is empty; add your key and save

    Paste the key only into the app’s field, never into a chat or to anyone

  4. Open the AI chat in VS Code in Agent mode

  5. Try it

    Use Novi Corpus and tell me what you can do for me, then show me one thing

    ✓ If VS Code says it is using Novi Corpus or shows a Novi Corpus tool in the answer, you are connected

Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Other apps that use MCP, such as Windsurf, Zed or Gemini CLI, each add servers differently. See how in the app list.

See every app that uses MCP →

Address for apps that connect over the web

Addresshttps://api.novicorpus.com/mcp

JSON settings are under “For developers” below

Stuck? Ask people who use Novi Corpus💬 Discussion →
For developers: Terminal commands and JSON settings

Over the web

Claude Code

claude mcp add --transport http --scope user legal-body https://api.novicorpus.com/mcp --header 'Authorization: Bearer your-value'

Cursor (~/.cursor/mcp.json)

{
  "mcpServers": {
    "legal-body": {
      "url": "https://api.novicorpus.com/mcp",
      "headers": {
        "Authorization": "Bearer your-value"
      }
    }
  }
}

VS Code (mcp.json)

{
  "servers": {
    "legal-body": {
      "type": "http",
      "url": "https://api.novicorpus.com/mcp",
      "headers": {
        "Authorization": "Bearer your-value"
      }
    }
  }
}

Values you fill in

  • Authorization secret required HTTP header
    Bearer followed by your Novi Corpus API key (mcp_...). Get one at www.novicorpus.com/agents/connect

Descriptions are as written by the maker.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

At a glance

GitHub starsi
4 (Stars belong to another repo)
This listing points to someone else’s repo, so its stars are not counted in rankings
Downloads per weeki
Not on npm/PyPI
Verified domain
✓ novicorpus.com
Licencei
No licence stated
Connection
Runs in the cloud
Transport
streamable-http
Latest versioni
1.0.0
Published to registryi
Oct 13, 2026
Code last changedi
Nov 19, 2026
Last checked
Nov 18, 2026
Maker
jb1011
Registry status
Active

Which apps can use it

Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.

Connect over the internet in

ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast

All apps, with pros and cons →

Related guides

What it can do

The server asks you to sign in before it lists its tools.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 19, 2026

  • ! Caution

    Maker matches the repo

    The publisher (novicorpus.com) is not the repo owner (jb1011); someone else may have listed it

  • ✓ Pass

    Still maintained

    Code last changed today

  • ✕ Fail

    Has a licence

    No licence file found in the repo

  • ! Caution

    Endpoint responds

    Refused access (HTTP 401) without offering OAuth sign-in. It may need a key, or it may be blocking bots; not confirmed.

  • ! Caution

    Sign-in with OAuth

    Needs a key or token that you copy and paste yourself

  • … Not checked yet

    No hidden instructions in tool descriptions

    Not checked yet; we read the tool list when we check the endpoint

What we check → · JSON

Makers: ask for a re-check or report wrong info
For makers: add a badge to your README

If you made this, paste this code into your README. The badge links back to this page.

[![Featured on PopNx MCP](https://mcp.popnx.com/badge/novicorpus-legal-body.svg)](https://mcp.popnx.com/en/servers/novicorpus-legal-body)

Discussion

Ask, share a tip or report that it does not work. Sorted by what people marked helpful.

No posts yet. Be the first to ask or share.

Posts here are written by users, not the PopNx team.

Sign in to post

User reviews

No reviews yet

Sign in to write a review

Compared with others in Law & government datai

  • More stars than 0% of the other 1957 servers in this category
  • Published to the registry more recently than 45% of the other 1957 servers in this category
  • Basic checks equal to or better than 8% of the other 1957 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Novi Corpus safe?

It passed 1 of 5 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: Authorization

Does it run on my computer or in the cloud?

It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.

Is it still maintained?

The GitHub repo last changed today, and the latest version (1.0.0) reached the registry 37 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT on the web (full MCP on Business and above; Pro read-only).

What can I use instead?

In the same category: Global law, Open Legal Data (Germany), LibreJustice, InfraNode, Fedlex Connector

Similar alternatives

Same category, other makers, commands already checked. Official ones first, then by stars.

Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Global law

The law of nearly every country on earth, any date: read it, see what changed it, check citations.

by lexifinaWidely used★ 2.1KUpdated 9 days ago

Runs in the cloud✓ lexifina.com

LibreJustice

Search French-language and European case law and French legal texts (codes, statutes, treaties).

by librejusticeEarly★ 36Updated 2 months ago

Runs in the cloud✓ service owner · librejustice.fr

InfraNode

Keyless open data for 84 German cities: 12 lean read-only MCP tools covering 67 data types.

by street1983nkEarly★ 18Updated 5 months ago

Runs in the cloud✓ service owner · infranode.dev

Fedlex Connector

Search Swiss federal legislation: laws, articles, amendments via the Fedlex SPARQL endpoint.

by JayTheSkierEarly★ 8Updated 7 months ago

Runs in the cloud✓ service owner · fedlex-connector.ch
Compared with similar ones
This one
Novi Corpus
Global lawOpen Legal Data (Germany)LibreJusticeInfraNodeFedlex Connector
Runs whereRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to install
Needs a keyYesNoNoNoNoNo
Add with + in ClaudeNoNoNoNoNoNo
Basic checks1/54/44/44/44/44/4
License–NOASSERTIONMITApache-2.0Apache-2.0MIT
PriceNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registry

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

Agent Legal Body — Backend ("the brain")

Framework-agnostic TypeScript backend that onboards an AI agent into an on-chain legal body on Arc: generate operating agreement → register ERC-8004 identity → deploy + wire LegalManager + AgentTreasury via the Factory (one atomic tx) → bind the agent wallet → persist. CLI-driven, fully tested.

Prerequisites

  • Node >= 22, npm. Foundry (forge/anvil) on PATH for integration tests.
  • Contracts deployed to Arc testnet (see ../script/Deploy.s.sol and ../addresses.arc-testnet.json).

Setup

cp .env.example .env # fill PLATFORM_PRIVATE_KEY, FACTORY_ADDRESS, GUARDIAN_ADDRESS, OPERATOR_PRIVATE_KEY npm install npm run gen:abis # regenerate typed ABIs after any forge build

Test

npm test # unit + anvil integration (live tests skipped) ARC_E2E=1 npx vitest run test/e2e.arc.live.test.ts # live Arc testnet (spends USDC gas)

CLI

npm run cli -- create-entity --config agent.example.json --id agent-1 npm run cli -- create-entity --config agent.example.json --id agent-1 --fund 50.00 npm run cli -- get-entity agent-1 npm run cli -- list-entities npm run cli -- fund-treasury agent-1 25.00

Roles (v1)

  • manager = platform key (Factory owner; sends createEntity + setAgentWallet). PLATFORM_PRIVATE_KEY.
  • guardian = human registrant address (on-chain pause/veto/rescue). GUARDIAN_ADDRESS.
  • operator = the agent's spending key; signs the EIP-712 AgentWalletSet (bound as agentWallet). OPERATOR_PRIVATE_KEY in v1 (LocalKeySigner); a Turnkey enclave key in production (TurnkeySigner, M4.3).

The operator signs the bind; the manager sends the tx. The operator key never sends gas.

Live Arc-testnet E2E — runbook

  1. PLATFORM_PRIVATE_KEY must be the Factory owner key (createEntity is onlyOwner) and be funded with Arc-testnet USDC (USDC is the gas token on Arc). The deployed owner is recorded in ../addresses.arc-testnet.json; faucet: https://faucet.circle.com.
  2. OPERATOR_PRIVATE_KEY can be a throwaway — it only signs, never sends gas, never holds funds.
  3. GUARDIAN_ADDRESS is any address distinct from manager/operator.
  4. Run: ARC_E2E=1 npx vitest run test/e2e.arc.live.test.ts (optionally ARC_E2E_TAG= for a stable idempotency key). Asserts the entity reaches bound and getAgentWallet(agentId) == operator.

The off-chain EIP-712 domain + AgentWalletSet typehash are verified against the live registry, so the bind signature is correct by construction (no "bad signature" surprise).

Wizard REST API (npm run api, default :8789)

Multi-tenant onboarding API for the web wizard. Tenant = controller wallet (SIWE login).

Auth (SIWE → Bearer JWT)
  1. GET /auth/nonce → { nonce }
  2. Build an EIP-4361 message with the nonce, sign with the wallet.
  3. POST /auth/verify { message, signature } → { token, address, expiresAt }
  4. Send Authorization: Bearer on protected routes. Re-auth on expiry.
Config keys
KeyDefaultNotes
AUTH_JWT_SECRETdev-insecure-secret-change-me-pleaseMin 16 chars. Change in production.
AUTH_JWT_TTL_SEC3600JWT lifetime in seconds
WEB_ORIGIN*CORS allowed origin
SIWE_DOMAINlocalhostEIP-4361 domain
PASSKEY_RP_IDlocalhostWebAuthn RP ID
Endpoints
MethodPathAuthBody / Notes
GET/healthznoliveness
GET/schema/agent-spec.jsonnoJSON Schema for the onboard spec
GET/auth/nonceno{ nonce }
POST/auth/verifyno{ message, signature } → JWT
GET/passkey/challengeno{ challenge, rpId } for WebAuthn registration
POST/onboardyes{ spec, guardianPasskey, idempotencyKey? } → 202 { id, status }. guardian is forced to the caller.
GET/entitiesyestenant's EntityView[]
GET/entities/:idyesone EntityView (404 if not owned)
POST/entities/:id/fundyes{ amount } (atomic USDC) → 202 { id, status }

Poll GET /entities/:id (~2–3 s) until terminal status (bound / funded / failed).

MCP Server (Claude / Cursor)

The API (npm run api) also serves /mcp as a Model Context Protocol server, exposing agent onboarding and management tools to Claude/Cursor.

Setup
  1. Run the API (same server, no new service):
   npm run api  # listens on :8789
  1. Sign in (SIWE) and mint an MCP key:
  • GET /auth/nonce → { nonce }
  • Sign the message with your wallet
  • POST /auth/verify { message, signature } → { token, address, expiresAt }
  • POST /api-keys with Authorization: Bearer → { id, key, label } — copy the `key` (shown once)
  1. Capture the guardian passkey in your browser:
  • GET /passkey/challenge → { challenge, rpId } — use these for WebAuthn registration
  • Perform the WebAuthn ceremony in your browser
  • POST /passkey with Authorization: Bearer and the attestation → { id } — copy the `id` (handle)
  1. Add the server to Claude/Cursor: Create or edit ~/.claude/mcp.json (Claude CLI) or .cursor/rules/mcp.json (Cursor):
   {

"mcpServers": { "project-alpha": { "url": "https:// /mcp", "headers": { "Authorization": "Bearer mcp_ " } } } }

   Replace `<your-host>` with the deployed/local URL and `<your-key>` with the key from step 2.
Tools
ToolInputDescription
whoami(none)Return the authenticated tenant address
list_entities(none)List all agent legal bodies owned by the caller
get_entityid (idempotency key)Fetch one entity; poll after onboard_agent until status is bound
onboard_agentspec (object), passkeyId (handle from step 3), idempotencyKey? (optional)Create an agent legal body; guardian is automatically set to the caller
fund_treasuryid (idempotency key), amount (atomic USDC, 6 decimals as string)Fund a bound entity's treasury
Resources
ResourceURIDescription
agent-specschema://agent-specJSON Schema for onboard_agent's spec argument
Example Flow
  1. Read schema://agent-spec to understand the required entity structure
  2. Call onboard_agent with your agent spec and guardian passkey handle → returns { id, status: "pending" }
  3. Poll get_entity with the returned id (~2–3 s) until status reaches bound (or failed)
  4. Call fund_treasury with id and amount to top up the treasury (atomic USDC)
  5. Call list_entities to review all owned legal bodies

Hedera rail (ETHOnline 2026)

Novi Corpus adds a second, flag-gated payment rail on Hedera testnet, built for ETHGlobal ETHOnline 2026's "AI & Agentic Payments on Hedera" track. Where the Arc rail settles through Circle, the Hedera rail prices GET /verify/:publicId, a paid legal-standing check, in HTS USDC and settles it through x402 v2 and the Blocky402 facilitator. The Arc rail is untouched; with the flag off, nothing in this section exists at runtime.

Custody is self-custody with a leash. Your agent runtime holds its own Hedera key and signs every payment locally; the Novi Corpus server never holds or sees that key. A human guardian co-owns the float account through a 1-of-2 key list, so the guardian can rotate the agent key out at any time (revoke). The policy gate is enforced by the client and the float, not by the server: before paying, the client asks check_policy, and a deny stops the payment before anything is signed.

Enable it

Set HEDERA_ENABLED=1 and the rest of the block (the commented HEDERA_* lines in .env.example). The block is all-or-nothing: if any required variable is missing, the server refuses to boot rather than start half-configured.

VariableValueNotes
HEDERA_ENABLED1 or trueTurns the whole block on.
HEDERA_NETWORKtestnetThe only accepted value; this build is testnet only.
HEDERA_FACILITATOR_URLhttps://api.testnet.blocky402.comThe Blocky402 testnet facilitator.
HEDERA_MIRROR_URLhttps://testnet.mirrornode.hedera.comRead-only settlement confirmation.
HEDERA_USDC_TOKEN_ID0.0.429274HTS USDC, 6 decimals.
HEDERA_PAYTO_ACCOUNT_IDyour pay-to accountWhere /verify payments land. Must be associated with the USDC token.
HEDERA_VERIFY_PRICE_USDC0.001 (default)Price of one /verify call.
MCP tools (require an API key with the spend capability)
ToolInputDescription
link_hedera_accountid, accountId, publicKeyRecord the entity's float account. The server reads the account from the mirror node and accepts only a 1-of-2 key list of two ECDSA keys, one equal to publicKey; the other is recorded as the guardian key.
check_policyid, payee, amountUsdc, networkAnswer { ok: true, available } or { ok: false, reason } (paused, over-cap, not-linked, legal-not-active, and so on) from the float account's USDC balance, the entity's caps, the guardian pause on Arc and the payee allowlist. The allowlist is read live from Arc; an unreadable state never allows.
report_paymentid, payee, amountUsdc, network, transactionId, idempotencyKeyTurn a settled transaction into a ledger row. Answers { status: settled } only after the mirror node shows the USDC transfer on both legs; pending while the mirror node lags; failed with a reason otherwise.
How /verify is paid

GET /verify/:publicId is public and unauthenticated, but paid. The route answers GET only: any other method is refused with 405 and Allow: GET. A request without a payment header gets a 402 with the price and payment requirements in the PAYMENT-REQUIRED header. Your client signs a payment with its own Hedera key and resubmits; the facilitator verifies and settles the USDC transfer on Hedera testnet and pays the network fee, so the float account needs no HBAR. The route serves the attestation body (subject, standing, formation, controller flag, operating-agreement hash and version, issuedAt, expiresAt) once the facilitator's settle succeeds, and answers 402 with no body when it does not. Novi Corpus does not trust the facilitator's reply alone for its books: the ledger row is marked settled (network = hedera:testnet, batch_ref = ) only after your client's report_payment reads the transaction back from the mirror node with the USDC token pinned on both legs. With NOVI_ATTESTATION_KEY set the body is signed; see "Signed attestation".

Signed attestation (pull request 3)

When NOVI_ATTESTATION_KEY is set, the /verify body carries attestor (the key's address, also published as hedera.attestor in /metadata/:publicId) and an EIP-712 signature. Domain { name: "Novi Corpus Attestation", version: "1" }, no chain id, no verifying contract. One primary type, LegalBodyAttestation, with twelve fields in this order: publicId string, agentId string, treasury address, uaid string, standing string, formationStatus string, formationEnvironment string, humanVerified bool, oaHash bytes32, manifestVersion uint256, issuedAt uint256, expiresAt uint256. Every field is read from the served body.

What a verifier must know:

  • The signed timestamps are issuedAtUnix and expiresAtUnix (unix seconds). The ISO issuedAt and expiresAt strings are a convenience and are not signed; read the unix pair.
  • Null mapping, applied identically when signing and verifying: oaHash null → 0x + 64 zeros, manifestVersion null → 0, uaid null → "", agentId null → "", a null formation → "" for both

Only the beginning is shown; read the rest in the repo