1. Conduid
  2. Developer Tools
  3. arian-gogani/nobulex
MCP server · Developer Tools

arian-gogani/nobulex

no proof, no transaction. MIT licensed, 4,244 tests.

Unclaimed devtools
39Low

Scored 6 months ago · breakdown

About arian-gogani/nobulex

arian-gogani/nobulex is an MCP server in the Developer Tools category: no proof, no transaction. MIT licensed, 4,244 tests.

Install

From source
git clone https://github.com/arian-gogani/nobulex

This server has no ConduID identity, so agent calls to it are not receipted. Pin the version you install and review the source before granting it credentials.

Ask AI

✦

Ask AI about arian-gogani/nobulex

Powered by Claude · Grounded in docs

I know everything about arian-gogani/nobulex. Ask me about installation, configuration, usage, or troubleshooting.

Security checks

  • ✓README presentThe repository ships documentation.

5 checks have not been run yet.

README

Nobulex

CI OpenSSF Best Practices

The trust layer for the autonomous economy.

AI agents are shipping into production. Nobody can prove what they actually do. Nobulex fixes that with cryptographic receipts: signed proof before and after every agent action, hash-chained, verifiable by anyone.

Status

$ npx tsx examples/demo.ts

Agent A declares covenant: permit read, forbid transfer > 500
Agent A executes 5 actions...
  ✓ read /data/users — allowed
  ✓ transfer $300 — allowed
  ✓ read /data/orders — allowed
  ✗ transfer $600 — BLOCKED by covenant
  ✓ read /data/config — allowed

Agent B verifies Agent A...
  ✓ Step 1: Covenant signature valid
  ✓ Step 2: Proof signature valid
  ✓ Step 3: Log integrity verified (5 entries, chain intact)
  ✓ Step 4: Compliance check passed (0 violations)
  ✓ Step 5: History length sufficient (5 ≥ 1)
  ✓ Step 6: Covenant matches requirements
  ✓ Step 7: Audience binding confirmed
  ✓ Step 8: Task class verified

Result: Agent B trusts Agent A ✅

Agent C presents tampered proof...
  ✓ Step 1: Covenant signature valid
  ✓ Step 2: Proof signature valid
  ✗ Step 3: FAILED — hash chain broken at entry 2

Result: Agent B refuses Agent C ❌

Three primitives. That's the whole protocol:

  1. Declare — write rules: permit, forbid, require
  2. Enforce — check every action before it runs
  3. Prove — tamper-evident hash chain anyone can verify

Tests License TypeScript

Try it live · Policy Designer · Quickstart · Compare · Receipt Schema · Pricing · IETF Draft

What is Proof-of-Behavior?

You can't audit a neural network. But you can audit actions against stated commitments.

verify(covenant, actionLog) → { compliant: boolean, violations: Violation[] }

This is always decidable, always deterministic, always efficient. No ML, no heuristics — mathematical proof.

Proof-of-behavior means every autonomous agent action is:

  • Declared — behavioral rules defined before deployment in a formal language
  • Enforced — violations blocked at runtime, before execution
  • Proven — every action hash-chained into a tamper-evident audit trail that third parties can independently verify

Quick Start

npm install @nobulex/sdk
import { createDID, parseSource, EnforcementMiddleware, verify } from '@nobulex/core';

// 1. Create an agent identity
const agent = await createDID();

// 2. Write behavioral rules
const spec = parseSource(`
  covenant SafeTrader {
    permit read;
    permit transfer (amount <= 500);
    forbid transfer (amount > 500);
    forbid delete;
  }
`);

// 3. Enforce at runtime
const mw = new EnforcementMiddleware({ agentDid: agent.did, spec });

// $300 transfer — allowed
await mw.execute(
  { action: 'transfer', params: { amount: 300 } },
  async () => ({ success: true }),
);

// $600 transfer — BLOCKED before execution
await mw.execute(
  { action: 'transfer', params: { amount: 600 } },
  async () => ({ success: true }),  // never runs
);

// 4. Prove compliance
const result = verify(spec, mw.getLog());
console.log(result.compliant);    // true
console.log(result.violations);   // []

Cross-Agent Verification Handshake

Before two agents transact, they verify each other's proof-of-behavior. No proof, no transaction.

import { generateProof, verifyCounterparty } from '@nobulex/sdk';

// Agent A generates its proof-of-behavior
const proof = await generateProof({
  identity: agentA,
  covenant: spec,
  actionLog: middleware.getLog(),
});

// Agent B verifies Agent A before transacting
const result = await verifyCounterparty(proof);

if (!result.trusted) {
  console.log('Refusing transaction:', result.reason);
  return; // No proof, no transaction
}

// Safe to transact — Agent A is verified
await executeTransaction(proof.agentDid, amount);

The handshake checks eight things in order: covenant signature, proof signature, log integrity, compliance, minimum history, required covenant, audience binding, and task class scoping. If any check fails, the transaction is refused.

Why Proof-of-Behavior Matters

What exists today What's missing
Guardrails filter prompts and outputs No proof the agent followed rules at the action layer
Monitoring watches what agents do after the fact No enforcement before execution
Identity verifies who the agent is No verification of what the agent did
Governance platforms provide dashboards and policies No cryptographic evidence a third party can independently verify

Proof-of-behavior fills the gap: declare → enforce → prove.

Conceptual Comparison

Bitcoin Ethereum Nobulex
What it verifies Monetary transfers Contract execution Agent behavior
Mechanism Proof of Work Proof of Stake Proof of Behavior
What's proven Transaction validity State transitions Behavioral compliance
Guarantee Trustless money Trustless contracts Trustless agents

Live Demo

npx tsx examples/demo.ts

Creates two agents, defines behavioral rules, enforces at runtime, blocks a forbidden transfer, generates a proof-of-behavior, runs the 8-step handshake, and then shows the same handshake rejecting a third agent whose log was tampered with.

npx tsx examples/langchain-agent.ts   # covenant enforcement around a mocked LangChain agent
npx tsx benchmarks/bench.ts           # protocol performance on your hardware

Security Audit

We've conducted an internal security review. Here's what we tested and what we found:

Verified secure:

  • Hash chain integrity: modifying any entry breaks the chain (property-tested with fast-check across random chains of varying length).
  • Signature forgery: invalid signatures are rejected 100% of the time.
  • Replay attack prevention: audience-bound proofs fail when replayed to a different verifier (property-tested).
  • Covenant enforcement: forbidden actions are blocked before execution, never after.

Known limitations:

  • No key revocation mechanism yet.
  • No rate limiting on handshake verification.
  • Single-threaded chain verification.
  • Clock skew tolerance is 0.

See docs/threat-model.md for the full threat model.

Development

git clone https://github.com/arian-gogani/nobulex.git
cd nobulex
npm install
npx vitest run             # full test suite (incl. fast-check property tests)
npx tsx examples/demo.ts   # see the protocol run end-to-end
npx tsx benchmarks/bench.ts

Standards

  • IETF Internet-Draft — draft-gogani-nobulex-proof-of-behavior-00: Proof-of-Behavior Protocol for Autonomous AI Agents
  • LangChain RFC #35691 — ComplianceCallbackHandler, 10+ implementations converging
  • NIST RFI Response — Formal comments to NIST AI Agent Standards Initiative
  • Microsoft AGT — Bilateral receipt primitive merged (PRs #1302, #1333)

Ecosystem

Projects building on or composing with Nobulex:

Partner Layer Integration
Microsoft AGT Governance toolkit Bilateral receipt primitive (PR #1333)
APS Receipt schema 10/10 byte-match on bilateral-delegation fixtures
AgentGraph CTEF vectors Cross-implementation byte-match validation
AgentID Identity layer Claim type convergence
HiveTrust Compliance Bilateral receipt endorsement
Concordia Envelope layer JCS canonicalization alignment
Dominion Observatory Pre-call trust scores Feeds trust_score into covenant require
Signet Signing layer Bilateral co-signing, policy attestation

Documentation

Links

License

MIT

README copy captured when this server was indexed; it may lag the repository. The original is authoritative.

Questions

About arian-gogani/nobulex

How do I install arian-gogani/nobulex?

No package has been published for this server, so install it from source: clone the repository and follow its README.

Is arian-gogani/nobulex safe to use with an AI agent?

Its trust score is 39 out of 100 (low). It passes 1 of the 1 static security checks run so far. It has no ConduID identity yet, so agent calls to it are not receipted.

Is arian-gogani/nobulex still maintained?

Conduid hasn't recorded a commit date for this repository yet. Check the repository directly for recent activity.