
Word Counter API
io.github.Br0ski777Published by GitHub account Br0ski777v1.1.0Updated Oct 24, 2026
Count words, characters, sentences, paragraphs, reading time. x402 micropayment.
Overview
Remote MCP endpoint that counts words, characters, sentences and paragraphs in text and estimates reading time, billed per call via x402 micropayments.
- What you can do
- Count words, characters, sentences and paragraphs in a piece of text
- Estimate reading time from the returned statistics
- Return a combined statistics response (words, characters with and without spaces, sentences, paragraphs, reading time)
- When to use it
- Useful when an assistant needs quick text-length metrics, such as validating content against minimum word counts or estimating how long an article takes to read before publishing. It is a narrow single-purpose service, so it only makes sense if you want that check as a paid remote call.
- Requirements
- A remote MCP client pointed at the hosted endpoint; nothing to install locally. No API key or signup, but each call is paid in USDC on the Base L2 network through the x402 protocol, so an x402-capable client and a funded wallet are needed. Network access to the provider's domain is required.
Installation
In SourceWeft
- Open Word Counter API in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Web executable via SSE. 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/io.github.Br0ski777%2Fword-counter/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.Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"word-counter-api": {
"type": "sse",
"url": "https://word-counter.api.klymax402.com/mcp"
}
}
}README
Word Counter API
[MCP Server] [x402] [License: MIT]
Analyze text metrics: word count, characters, sentences, paragraphs, and estimated reading time in one call. Pay-per-call via x402 (USDC on Base L2) -- no API key, no signup, no rate-limit wall.
Part of the klymax402 marketplace -- 100 x402 micropayment APIs for AI agents, one wallet, USDC on Base.
Quickstart -- MCP
Add to your MCP client config (Claude Desktop, Cursor, ElizaOS, etc.):
Quickstart -- HTTP (x402)
Any x402-aware client (@x402/fetch, x402-agent-tools, ATXP) handles the 402 -> sign -> retry cycle automatically.
Tools
text_count_words
Use this when you need to count words, characters, sentences, or paragraphs in text. Returns comprehensive text statistics with reading time estimate.
Parameters
Example response:
When to use: content length validation, estimating article reading time, or checking if text meets minimum word count requirements. Essential BEFORE publishing blog posts or submitting content with length constraints.
Not for: language detection (use text_detect_language), sentiment analysis (use text_analyze_sentiment), text comparison (use text_compare_diff).
Example agent prompts
- "Count words, characters, sentences, or paragraphs in text"
Payment
- Protocol: x402 -- HTTP-native pay-per-call, no signup, no API key
- Network: Base L2 (
eip155:8453) - Asset: USDC
- Facilitator: Coinbase CDP (primary), PayAI (fallback)
- Also reachable via ATXP (OAuth-wrapped x402, RFC 9728 protected-resource metadata)
Part of klymax402
100 x402 micropayment APIs for AI agents -- one wallet, USDC on Base, zero signup.
- Catalog: https://klymax402.com/llms.txt
- Full API reference: https://klymax402.com/llms-full.txt
- Live stats: https://klymax402.com/stats
License
MIT
Source: README.md at commit 63ca8ed
Tools
0Version history
1- v1.1.0LatestSep 16, 2026
Score
50% 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
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declaredRequired10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts