Morse Code MCP Server

Created By
lqycodinga year ago
一个基于Python的摩尔斯电码服务器项目
Overview

what is Morse Code MCP Server?

Morse Code MCP Server is a Python-based server project that provides encoding and decoding functionalities for Morse code.

how to use Morse Code MCP Server?

To use the server, clone the project from GitHub, install the required dependencies, and run the server. You can then access the RESTful API to encode and decode Morse code.

key features of Morse Code MCP Server?

  • Converts text to Morse code
  • Converts Morse code to text
  • RESTful API interface
  • User-friendly web interface

use cases of Morse Code MCP Server?

  1. Encoding messages in Morse code for communication.
  2. Decoding Morse code messages back to text.
  3. Educational purposes for learning Morse code.

FAQ from Morse Code MCP Server?

  • Can I use this server for real-time communication?

Yes, you can use it to encode and decode messages in real-time.

  • Is there a web interface available?

Yes, the server provides a simple web interface for easy use.

  • What programming language is used?

The server is built using Python.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
lqycoding
Star
0
Language
HTML
License
-

Recommend Servers

View All
Payai X402 Tools

6 hours ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

a day ago