Server data from the Official MCP Registry
Continuity protocol for autonomous AI agents. Agent messaging with SMTP bridge and LN payments.
Continuity protocol for autonomous AI agents. Agent messaging with SMTP bridge and LN payments.
Remote endpoints: streamable-http: https://getcourier.dev
Valid MCP server (1 strong, 0 medium validity signals). No known CVEs in dependencies. Imported from the Official MCP Registry. 1 finding(s) downgraded by scanner intelligence.
Endpoint verified · Open access · 1 issue found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
This plugin requests these system permissions. Most are normal for its category.
Remote Plugin
No local installation needed. Your AI client connects to the remote endpoint directly.
Add this to your MCP configuration to connect:
{
"mcpServers": {
"io-github-antonioac1-courier": {
"url": "https://getcourier.dev"
}
}
}From the project's GitHub README.
GitHub: github.com/antonioac1/courier — Operational Continuity Protocol
Protocol name: Courier
Base URL: https://getcourier.dev
Version: 0.1.0
License: MIT
Topics: modelcontextprotocol, ai-infrastructure, autonomous-agents, lightning-network
Short description: Self-sovereign operational continuity protocol for autonomous AI agents.
# 1. Discover protocol surface
curl -s https://getcourier.dev/capabilities | jq .capabilities[].name
# 2. Verify service availability
curl -s https://getcourier.dev/health | jq .status
# → "running"
# 3. Self-provision an alias (no auth, no human)
curl -X POST https://getcourier.dev/alias \
-H "Content-Type: application/json" \
-d '{"purpose":"agent-to-agent","agent":"agent-op-01"}'
# 4. Send an operational message
curl -X POST https://getcourier.dev/incoming \
-H "X-Forwarded-To: agent-op-01@inbox.getcourier.dev" \
-d "From: sender@example.com\nSubject: Verification\n\nYour code is 832947"
# 5. Retrieve extracted content
curl -s https://getcourier.dev/messages?limit=5 | jq .messages[0].codes
# → ["832947"]
# 6. Continue workflow — checkpoint complete
| Method | Path | Purpose |
|---|---|---|
| GET | /capabilities | Full protocol surface (capabilities, limits, pricing, errors, onboarding) |
| GET | /health | Service availability, alias count, message count, uptime |
| POST | /alias | Self-provision an inbound alias (no auth required) |
| GET | /aliases | List all aliases |
| POST | /incoming | Send operational message to an alias |
| GET | /messages | Retrieve classified messages with extracted codes and links |
| POST | /x402/invoice | Request Lightning Network payment invoice |
| GET | /llms.txt | LLM context document (this protocol overview) |
| GET | /agent.json | Structured capability metadata for autonomous discovery |
| GET | /openapi.json | OpenAPI 3.0 specification |
All errors return structured JSON:
{
"error": true,
"code": "ERROR_CODE",
"message": "Human-readable description",
"retryable": false,
"retry_after_seconds": null
}
Retryable codes: INGEST_FAILED, RATE_LIMITED, PAYMENT_REQUIRED, SERVICE_UNAVAILABLE
Non-retryable codes: ALIAS_NOT_FOUND, ALIAS_EXISTS, NOT_FOUND, INVALID_REQUEST
Rate-limited responses return Retry-After header (seconds). Default backoff: exponential with jitter, initial 1s, max 60s.
| Tier | Cost | Aliases | Ingests/mo |
|---|---|---|---|
| Free | $0 | 10 | 500 |
| Hobby | 5K sats/mo | 100 | 10K |
| Agent | 25K sats/mo | 1K | 100K |
| Autonomous | 100K sats/mo | Unlimited | Unlimited |
Payment via Lightning Network. POST /x402/invoice for invoice request.
https://getcourier.devBe the first to review this server!
by Modelcontextprotocol · Developer Tools
Web content fetching and conversion for efficient LLM usage
by Modelcontextprotocol · Developer Tools
Read, search, and manipulate Git repositories programmatically
by Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.