Skip to content
ScrubMyText logo

ScrubMyText MCP server

Which MCP servers are ScrubMyText's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-25

← Back to ScrubMyText

Whose server it is
  • Registry namecom.scrubmytext/toolsverified in the MCP registry

The registry name sits under scrubmytext.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-25
  • Stateanswerschecked 2026-10-25
  • Tools49
  • Server calls itselfcom.scrubmytext/tools
  • Server version7.5.0
  • Protocol version2025-11-25

On 2026-10-25 the server answered initialize and tools/list without a sign-in. First answer in 252 ms.

Should an agent connect itNot proven either way yet
  • Its tools do every use case we checked: scan documents for likely secrets before a model reads them; check text for hidden instructions before an agent acts on it; stop an agent repeating a payment after a timeout retry.
  • Checked on 3 of the 7 days it takes to judge reliability.

Once connected

  • For "scan documents for likely secrets before a model reads them", the likely first call is detect_secrets.
  • create_signal, delete_signal, cancel_approval change data without a sign-in: anyone with the address can call them.
  • Parameters are untyped or undescribed in 48 of 49 tools: check arguments before calling.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 3, the first on 2026-10-25
  • INITE MCP scoreafter a weeka score needs 7 daily checks: 3 so far
  • What an agent can do with it3 of 3 use cases
  • Answeredmeasuring3 of the 7 daily checks it takes to print a share
  • Median first answer97 ms
  • Space in an agent's context≈ 8,082 tokensthe definitions of all its tools (49), which an agent carries on every turn
  • Tool definitionsB · 83 of 100
  • Typed results2 of 49 toolsdeclared outputSchema: results come typed, read once
  • Parameters without a type: in 1 of 49
  • Parameters without a description: in 48 of 49

What an agent can do with it

  • can do · scan documents for likely secrets before a model reads them
  • can do · check text for hidden instructions before an agent acts on it
  • can do · stop an agent repeating a payment after a timeout retry

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

Worth a look

  • Tools that change data, on a server that answers without a sign-in: create_signal, delete_signal, cancel_approval

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers49 tools · read 2026-10-25
  • scrub_text

    Normalize hidden/control characters and formatting artifacts without rewriting wording. Free or paid.

  • inspect_text

    Inspect exact Unicode, invisible characters, normalization, and mixed-script anomalies. Free or paid.

  • scan_untrusted_text

    Use before an agent ingests pasted, retrieved, uploaded, or externally supplied text. Returns structural and heuristic risk signals; it does not determine maliciousness or safety. Trial, subscription, or x402 pay-per-call.

  • redact_sensitive_text

    Use before storing, sharing, logging, or sending text downstream when it may contain credentials or identifiers. Pattern-based redaction; trial, subscription, or x402 pay-per-call.

  • compare_text

    Use to verify what changed between two text versions and whether differences are only scrub/format artifacts. Trial, subscription, or x402 pay-per-call.

  • detect_secrets

    Use before an agent logs, stores, or forwards text that may contain credentials. Finds likely API keys, private keys, JWTs, cloud credentials, and secret patterns without echoing values. Trial, subscription, or x402 pay-per-call.

  • validate_output

    Use immediately before a downstream action when model output must be valid JSON or match a schema. Trial, subscription, or x402 pay-per-call.

  • sanitize_agent_context

    Use before putting untrusted retrieved or uploaded text into a model context. Normalizes structural artifacts, returns risk signals, and can redact sensitive patterns. Trial, subscription, or x402 pay-per-call.

  • prepare_for_agent

    Use as the default preprocessing step before an AI agent consumes untrusted external text. Returns agent-ready text plus inspection, risk-scan, and secret-detection reports. Trial, subscription, or x402 pay-per-call.

  • rework_text

    Use when an agent needs a deterministic, no-LLM rewrite while preserving protected facts such as numbers, URLs, emails, and quotes. Returns change metrics and preservation checks; does not verify authorship or watermark status. Trial…

  • fingerprint_action

    Use before retryable work to derive a stable SHA-256 action fingerprint and idempotency key from an action name, optional scope, and JSON arguments. Object key order does not affect the result. Returns no input values and stores nothing…

  • lock_action

    Use immediately before a consequential agent action to atomically claim an idempotency key so retries cannot execute it twice. Subscription API key required.

  • lock_action_intent

    Use immediately before a consequential retryable action when no stable idempotency key exists. Deterministically fingerprints the action and arguments, atomically claims that key, and returns safe_to_execute. Repeat calls with equivalent…

  • check_action

    Use to inspect an idempotency key before or after an agent action. Subscription API key required.

  • complete_action

    Paid: mark the current lock completed and preserve the idempotency record for its configured retention period.

  • release_action

    Paid: release an uncompleted action lock using its lock_id so another attempt can safely acquire it.

  • create_signal

    Use when an agent must wait for an external callback, webhook, job completion, or asynchronous event. Subscription API key required.

  • get_signal_events

    Paid: retrieve events received by a temporary signal inbox in arrival order.

  • delete_signal

    Paid: immediately delete a signal inbox and all stored event bodies.

  • request_approval

    Use when an agent needs independent human approval before a consequential action. Creates a secure approval link. Subscription API key required.

  • check_approval

    Paid: check whether a human approval request is pending, approved, rejected, expired, or cancelled.

  • cancel_approval

    Paid: cancel a pending human approval request so its link can no longer approve the action.

  • manage_action_challenge

    Create, inspect, consume, or cancel a digest-bound cooling-off window. A bearer challenger can veto before the deadline; afterward the owner can atomically consume one execution right during a bounded window. This is exception handling…

  • reserve_action_budget

    Atomically reserve integer units under a named, period-scoped ceiling. A reservation_key makes retries idempotent. The service stores hashes and counters, not purchase details. Production; subscription API key required.

  • record_action_receipt

    Create or retrieve an immutable receipt digest for an action outcome without storing the action or outcome payload. Production; subscription API key required.

  • verify_signed_signal

    Verify an HMAC-SHA256 signal, enforce timestamp freshness, and reject a replayed nonce. The message and shared secret are never stored. Production; subscription API key required.

  • manage_resource_lease

    Atomically acquire, inspect, or release a short-lived exclusive lease on a hashed resource key. Production; subscription API key required.

  • manage_authority_delegation

    Issue, consume, inspect, or revoke a narrow bearer capability bound to one action fingerprint and a maximum use count. This is a technical capability, not identity proof or a legal delegation. Production; subscription API key required.

  • manage_agent_stop

    Set, inspect, or clear a durable stop signal for a hashed agent or workflow key. Callers should fail closed whenever stopped is true. Production; subscription API key required.

  • manage_task_handoff

    Create a bearer-token task handoff, let another paid API identity claim it exactly once, and inspect, complete, or cancel the transfer. Only task fingerprints are stored. Production.

  • manage_action_reconciliation

    Open, inspect, append digest-only evidence to, or resolve a discrepancy between expected and observed action outcomes. Production; subscription API key required.

  • anchor_context_trace

    Create or inspect an immutable provenance anchor from a context digest, parent digests, and processing stage. No context content is stored. Production; subscription API key required.

  • manage_task_contract

    Offer, accept, inspect, complete, or cancel a digest-bound technical task commitment. This records service state; it is not a legal contract, escrow, payment, or identity verification. Production.

  • check_agent_readiness

    Deterministically check a supplied MCP server card against a narrow, published integration contract. The service does not fetch arbitrary URLs and does not certify security or correctness. Free or paid.

  • manage_action_quorum

    Create, inspect, consume, or cancel an N-of-M bearer authorization quorum. Each unique bearer can decide once; only a successful one-time consume grants an execution right. Subscription API key required.

  • manage_task_deadline

    Create, inspect, complete, or cancel a task deadline whose due and escalation state is derived from an independent server clock even when the agent is offline. Subscription API key required.

  • manage_attention_budget

    Create, inspect, reserve, release, or close a finite review-capacity pool with per-subject caps, retry-safe reservations, and protected priority capacity. Subscription API key required.

  • manage_agent_escalation

    Create, inspect, or cancel a digest-only incident with a private bearer operator link and deterministic response and resolution SLA state. Link delivery remains the caller’s responsibility. Subscription API key required.

  • manage_terms_pin

    Pin, inspect, or revoke an immutable digest-bound record of observed terms, interface, version, and price. Stores bounded metadata and digests, not the terms body. This is technical evidence, not a legal agreement. Subscription API key…

  • match_policy_requirements

    Deterministically compare bounded provider capabilities with consumer-required and forbidden policy tokens. Processes supplied tokens without storing policy content and does not make legal or compliance conclusions. Subscription API key…

  • manage_action_compensation

    Bind a compensating-action digest before execution, record that the primary action executed, and atomically mark compensation once. Stores digests only and does not perform either action. Subscription API key required.

  • manage_context_status

    Publish, inspect, supersede, dispute, or revoke digest-only context status so downstream agents can stop using stale inputs. Stores no context body and does not invalidate copies outside this service. Subscription API key required.

  • manage_context_rights

    Issue, inspect, evaluate, or revoke a digest-bound machine-readable context-rights envelope. It is a technical policy signal, not legal advice or proof of ownership. Subscription API key required.

  • manage_disclosure_budget

    Create, inspect, record against, or close a cumulative disclosure budget with total, per-recipient, and per-category limits. Stores hashes and counters, not disclosed content or recipient identities. Subscription API key required.

  • list_quality_cards

    List exact service-version/task quality cards that have reached the public three-verified-contributor evidence threshold. Results are ordered by recent evidence, not quality, payment, or sponsorship. Free.

  • get_quality_card

    Retrieve a public, contextual quality card for an exact MCP server or REST API version. Scores remain unavailable until at least three independent verified contributors submit structured observations. Free.

  • compare_quality_targets

    Return contextual quality cards for two to ten exact targets in caller-provided order. It exposes evidence and uncertainty without producing a paid ranking or universal winner. Free.

  • record_quality_observation

    Submit an opt-in structured observation for an exact target and task. Receipt-linked observations are labeled E1; other observations are E0. Stores no prompt, response, credential, email, or free-form review. Free verified contributor or…

  • request_quality_correction

    Attach a digest-only correction or appeal request to a quality card. Requests are visible as unverified pending state and do not erase evidence or prove provider identity. Free verified contributor or subscription key required.

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "tools": {
      "type": "http",
      "url": "https://api.scrubmytext.com/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http scrubmytext https://api.scrubmytext.com/mcp

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://api.scrubmytext.com/mcp as a custom connector in the settings.

OpenAPI spec

70 paths, read 2026-10-25. Open the spec ↗

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.