x402 Text Tools Catalog
net.tunnelmole.imkl13-ip-209-115-177-214Published by imkl13-ip-209-115-177-214.tunnelmole.netOfficial publisherv0.1.1Updated Oct 24, 2026
Pay-per-call NLP & embeddings APIs on Base via x402. No keys/signup; agents pay per call in USDC.
Overview
A remote MCP endpoint offering pay-per-call NLP and embeddings APIs on the Base network, paid in USDC per call without keys or signup.
- What you can do
- Provides natural language processing and embedding capabilities as callable tools, according to the registry description; the manifest lists no individual tools, so the exact operations are not documented here. Each call is billed individually in USDC over the x402 payment scheme on Base. No API keys or account signup are involved; payment itself is the access mechanism.
- When to use it
- Worth considering when an assistant needs NLP or embedding results and you are willing to pay per request in USDC on Base rather than manage API keys with a conventional provider. Less suitable if you need documented tool names, predictable flat pricing, or a provider with a verifiable identity.
- Requirements
- A remote streamable HTTP endpoint; no local runtime, packages, environment variables or headers are declared. A wallet able to send USDC on the Base network for per-call x402 payments. Network access to the endpoint.
Installation
In SourceWeft
- Open x402 Text Tools Catalog in the dashboard and add it to a workspace.
- 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/net.tunnelmole.imkl13-ip-209-115-177-214%2Fx402-text-tools/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": {
"x402-text-tools-catalog": {
"type": "http",
"url": "https://imkl13-ip-209-115-177-214.tunnelmole.net/mcp"
}
}
}Tools
0Version history
1- v0.1.1LatestSep 16, 2026
Score
56% 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
Publish an icon in the registry entry.
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.
