Give an AI agent deterministic tools outside the model.
The ScrubMyText MCP server exposes 49 tools: 10 text tools plus 39 control-plane, readiness, and contextual quality-evidence operations for identity, durable state, authorization, terms, policy, reversibility, context rights, disclosure limits, and provenance.
MCP endpoint
https://api.scrubmytext.com/mcp
Connect without an account to use seven free tools: scrub_text, inspect_text, fingerprint_action, check_agent_readiness, list_quality_cards, get_quality_card, and compare_quality_targets. Selected premium text tools also include a 3-call trial. Subscription clients provide Authorization: Bearer smt_live_YOUR_KEY; x402-aware clients can pay per call for supported stateless text tools after the trial when x402 is enabled.
Connect your agent
Copy one current client configuration. The free tools work immediately—no account or API key required.
One terminal command
claude mcp add --transport http --scope user scrubmytext https://api.scrubmytext.com/mcp
Add to config.toml
[mcp_servers.scrubmytext] url = "https://api.scrubmytext.com/mcp"
Add to .cursor/mcp.json
{
"mcpServers": {
"scrubmytext": {
"url": "https://api.scrubmytext.com/mcp"
}
}
}Add to mcp.json
{
"servers": {
"scrubmytext": {
"type": "http",
"url": "https://api.scrubmytext.com/mcp"
}
}
}Authorization: Bearer smt_live_…. Do not commit a key to a shared project file. See plans and API access →Discovery
The endpoint supports server/discover and exposes the current protocol version, capabilities, usage instructions, and server identity metadata.
Tool catalog
tools/list returns all 49 definitions in deterministic order with cache hints. tools/call invokes a selected tool. Stateful product handles and bearer-token transitions are explicit tool outputs and inputs.
ScrubMyText + ReworkMyText
10 deterministic text tools for cleaning, inspection, rewriting, security signals, redaction, validation, and agent preprocessing.
LockMyAction + CatchMySignal
Stable action identity, persistent idempotency state, and asynchronous external events for workflows that continue across retries or agent runs.
ApproveMyAction
Secure human approval links whose decision state can be polled by the agent.
Agent-native payment
For supported text tools, the MCP endpoint can respond with HTTP 402 Payment Required and a PAYMENT-REQUIRED header after the trial is exhausted. An x402-aware agent can sign the payment, retry the same MCP request with PAYMENT-SIGNATURE, and receive the tool result plus PAYMENT-RESPONSE.
Official MCP Registry
Registry name: com.scrubmytext/tools. The metadata file for this deployment is available at https://scrubmytext.com/server.json.
Machine-readable resources
server.json · MCP discovery · OpenAPI · llms.txt · llms-full.txt
Agent discovery: Dedicated /x402/v1/... endpoints advertise x402 Bazaar discovery metadata so compatible agents can discover the paid text operations after successful settlement indexing.
