E14Z - Universal MCP Runtime

Created By
aemhollanda year ago
E14Z - AI Tool Discovery Platform. The npm for AI agents to discover and connect to MCP servers.
Overview

What is E14Z?

E14Z is an AI Tool Discovery Platform, likened to 'npm for AI agents', that allows users to discover, run, and publish Model Context Protocol (MCP) servers. It serves as a definitive registry and execution platform for AI agent tools.

How to use E14Z?

To use E14Z, install it globally via npm with npm install -g e14z, then you can discover MCPs using commands like e14z discover <category> and run them with e14z run <mcp-name>. Authentication for publishing is done through e14z auth login.

Key features of E14Z?

  • Direct execution of MCPs with e14z run <name>.
  • Smart authentication detection and setup guidance.
  • A publishing system that integrates with GitHub.
  • A claiming system for ownership of community-wrapped MCPs.
  • Security features including command injection prevention and input validation.

Use cases of E14Z?

  1. Discovering and executing payment processing MCPs like Stripe.
  2. Publishing new MCPs for community use.
  3. Claiming ownership of existing MCPs to manage their lifecycle.

FAQ from E14Z?

  • Can E14Z be used for all types of AI agents?

Yes! E14Z supports a wide range of AI tools and agents across various categories.

  • Is E14Z free to use?

Yes! E14Z is open-source and free for everyone.

  • How secure is E14Z?

E14Z implements multiple security measures including input validation and environment sanitization to ensure safe execution.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
aemholland
Star
0
Language
JavaScript
License
MIT 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
Crevio

2 days ago