Regennexus Uap

Created By
ReGenNow6 months ago
## Features - **Device Control**: GPIO, PWM, sensors, cameras - **Robotic Arms**: Amber B1, Lucid One with gripper support - **Mesh Networking**: Auto-discovery across LAN - **Security**: AES-256 encryption, token auth ## Installation pip install regennexus
Overview

What is Regennexus UAP?

Regennexus UAP is a Universal Adapter Protocol designed to connect devices, robots, applications, and AI agents with minimal latency and maximum security, making it ideal for IoT and robotics applications.

How to use Regennexus UAP?

To use Regennexus UAP, install it via pip with pip install regennexus, and then follow the quick start guide to initialize the protocol and register devices or send messages.

Key features of Regennexus UAP?

  • Device control for various hardware including Raspberry Pi, Arduino, and NVIDIA Jetson.
  • Support for robotic arms like Amber B1 and Lucid One.
  • Mesh networking for auto-discovery of devices.
  • High-level security features including AES-256 encryption and token authentication.
  • Integration with AI agents for direct hardware control.

Use cases of Regennexus UAP?

  1. Automating home devices and sensors.
  2. Controlling robotic arms for manufacturing or research.
  3. Implementing secure communication between IoT devices.
  4. Integrating AI for enhanced automation tasks.

FAQ from Regennexus UAP?

  • What devices are supported?

    Regennexus UAP supports a wide range of devices including Raspberry Pi, Arduino, and various IoT devices.

  • Is Regennexus UAP secure?

    Yes, it employs AES-256 encryption and token-based authentication for secure communications.

  • Can I integrate AI with Regennexus UAP?

    Yes, it allows for seamless integration with AI agents for controlling hardware.

Server Config

{
  "mcpServers": {
    "regennexus": {
      "command": "python",
      "args": [
        "-m",
        "regennexus.mcp_server"
      ],
      "env": {}
    }
  }
}
Project Info
Created At
6 months ago
Updated At
6 months ago
Author Name
ReGenNow
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago