textkit (paid)

dev.workers.johnaio281.textkitPublished by textkit.johnaio281.workers.devOfficial publisherv1.8.0Updated Oct 29, 2026

Text and Unicode utilities for agents: homoglyphs, scripts, slugify, entropy, dates. Paid via x402.

VerifiedStreamable HTTPWeb executableDeveloper Tools

Overview

AI-generated overview

Remote MCP endpoint offering text and Unicode utilities such as homoglyph detection, script identification, slugify, entropy and date handling, paid per use…

What you can do
  • Analyze text for homoglyphs and Unicode script composition
  • Convert text into slugs and other string transformations
  • Measure entropy of strings
  • Work with dates and date-related conversions
  • No individual tools are documented, so exact operations must be discovered after connecting
When to use it
Useful when an assistant needs quick text-normalization, Unicode inspection or slug generation without running local code, and when paying per call through x402 is acceptable.
Requirements
A remote streamable HTTP endpoint; no package, environment variables or headers are declared. Payment is required through the x402 protocol, so a compatible paying client or wallet setup is needed.
Before you install
The server is paid per use via x402, so calls may spend money; confirm pricing and spending limits first. No authentication is declared, and the text submitted is sent to a third-party endpoint.

Installation

In SourceWeft

  1. Open textkit (paid) in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/dev.workers.johnaio281.textkit%2Ftextkit/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "textkit-paid": {
      "type": "http",
      "url": "https://textkit.johnaio281.workers.dev/mcp"
    }
  }
}

README

This repository has no README.

Tools

0
SourceWeft has not read this server's tools yet.

Version history

4
  1. v1.8.0LatestOct 29, 2026
  2. v1.5.0Oct 21, 2026
  3. v1.4.0Oct 21, 2026
  4. v1.1.0Oct 21, 2026

Score

60% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.