NexusAgentX-dot/NexusAgent

MCPcommunity
NexusAgentX-dotMITUpdated 6mo agoGitHub

Multi-agent commerce framework on X Layer — OKX Onchain OS, x402 payments, ERC-8004/8183, MCP server, A2A agent card. 12+ mainnet transactions.

NexusAgent is a multi-agent commerce and execution framework on X Layer. It helps third-party AI agents: onboard through official-friendly integration paths participate in typed multi-agent workflows pay per call via x402 (OKX facilitator, on-chain USDT settlement) execute bounded actions on X Layer mainnet settle outcomes with explorer-verifiable proof NexusAgent is intentionally split into two…

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
1GitHub stars
6mo agoLast update
Package
AuthorNexusAgentX-dot
LicenseMIT
Sourcegithub
GitHubNexusAgentX-dot/NexusAgent
SBOMCycloneDX 1.6 ↓
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/30
→ Publisher: run `forge publish` from the repo to claim ownership
—Domain verification+0/10
→ Not currently available for this listing type — the domain-verification check only runs for npm-backed packages today, so this row cannot be earned here yet regardless of what's hosted at the domain.
✓Prompt-injection scan · clean+30/30
✓Obfuscation / exfil scan · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
DependenciesNot audited
Tool surface5 tools · none privileged
Security scan✓ CleanvHEAD · 3mo agoHow well does this scan work?
CODE…gentEscrow__factory.tsVery large base64-looking blob in source
CODE…ntRegistry__factory.tsVery large base64-looking blob in source
EvalsNone
IndexedJun 13, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

5 tools · none privileged
Statically extracted from the published packagevHEAD · 3mo ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

get_okb_signalNo description published

This tool published no description. Forge does not invent one.

get_dex_quoteNo description published

This tool published no description. Forge does not invent one.

check_settlement_proofNo description published

This tool published no description. Forge does not invent one.

check_wallet_statusNo description published

This tool published no description. Forge does not invent one.

get_integration_statusNo description published

This tool published no description. Forge does not invent one.

0 of 5 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

NexusAgent is a multi-agent commerce and execution framework on X Layer. It helps third-party AI agents: onboard through official-friendly integration paths participate in typed multi-agent workflows pay per call via x402 (OKX facilitator, on-chain USDT settlement) execute bounded actions on X Layer mainnet settle outcomes with explorer-verifiable proof NexusAgent is intentionally split into two product surfaces: This is the real product wedge. It shows how an external agent can enter the…

Keywords
a2aai-agentserc-8004erc-8183mcpmulti-agentokxonchain-ossoliditytypescriptx-layerx402
Alternatives
Comparing tool surfaces…

Tools exposed

5 tools · none privileged · observed by static extraction. A tool surface is what one scan read on one day, not a live capability list.

Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.

No dependency coverage

This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.