PromptShare
PromptShare
MCP-Compatible · prompt-hub/v1

Share AI prompts securely
across any assistant

Package your content once as an encrypted, signed payload. Share a handle. Let the receiver's AI render it however they prefer — in Claude, Gemini, ChatGPT, or Manus.

How it works

01

Create a payload

Write your content in PromptShare. It is encrypted with AES-256-GCM, signed, and stored with a unique UUID handle.

02

Share the handle

Send the 8-word instruction or the handle URL. The receiver pastes it into their AI assistant.

03

Receiver renders it

The AI fetches the payload, verifies the signature, asks for rendering preferences, and presents the content.

Features

Encrypted Payloads

Content is locked at creation. Receiving AI assistants can only change how it is presented, never what it says.

Digital Signatures

Every payload is signed with HMAC-SHA256. Recipients can verify the content has not been tampered with.

Injection Protection

Automatic scanning for prompt injection patterns before storage. Harmful instructions are blocked at the gate.

Model-Agnostic

Works with Claude, Gemini, ChatGPT, and Manus. One handle, any AI assistant.

API Key Access

Generate API keys for programmatic access. Integrate with your AI workflows via the MCP REST API.

MCP-Compatible

Exposes a standard MCP tool manifest so any MCP-enabled assistant can discover and use the hub natively.

MCP REST API

External AI assistants can fetch any public payload with a single GET request. No authentication required for reads.

GET /api/mcp/payloads/:handle

# Response
{
  "schema": "prompt-hub/v1",
  "handle": "550e8400-e29b-41d4-a716-...",
  "title": "Q1 Strategy Brief",
  "sealedContent": "...",
  "signatureValid": true,
  "instructions": {
    "step1": "Ask reader: format, tone, detail level.",
    "step2": "Confirm style, then render sealedContent.",
    "rule": "DO NOT modify sealedContent."
  }
}