Skip to content

Rewrite-regression probe pack MCP server

com.textforagents/rewrite-regression-probe-packtextforagents.comstreamable-httpv1.0.0Scanned

History-seeded rewrite-regression verdicts, signed per class.

4 tools: 4 change things.

Tools: 0 delete, 0 irreversible, 4 write, 0 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 1
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

4 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Rewrite-regression probe pack MCP server can do

The Rewrite-regression probe pack MCP server is published by textforagents.com, a domain the MCP Registry verified. It has 4 tools. It can create or change data (4 tools: rewrite_pack, rewrite_verdict, rewrite_verify_pack and rewrite_family), but cannot delete data. None of its tools only reads.

1 tool can send data out of your system (rewrite_pack).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 8, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

4 tools

Changes things 4Claude Code: ask
  • rewrite_familyThe launch advisory family: 5 shapes with classes and advisories.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    The launch advisory family: 5 shapes with classes and advisories.
  • rewrite_packRun a rewrite-regression pack against an authorised candidate (house_double or target_url+authorised+authorisation).Can send data outNo findings

    Why it is in this group

    • The description's first verb is "run": a word for a change.

    What it can reach

    • outboundThe input takes a URL (input.target_url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    Run a rewrite-regression pack against an authorised candidate (house_double or target_url+authorised+authorisation). Trial/pass/x402 billing as on POST /pack.
  • rewrite_verdictPrecomputed signed per-class verdict by candidate fingerprint ($0.01 x402 or pass).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Precomputed signed per-class verdict by candidate fingerprint ($0.01 x402 or pass).
  • rewrite_verify_packVerify a signed pack against the pinned production signing key.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Verify a signed pack against the pinned production signing key.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out1
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:32 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
4
Protocol version
2025-03-26
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 4 tools that change things (4 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://textforagents.com/products/rewrite-regression-probe-pack/mcp: tools/list returned 4 tools to an anonymous client, including rewrite_pack (write), rewrite_verdict (write), rewrite_verify_pack (write), rewrite_family (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http rewrite-regression-probe-pack https://textforagents.com/products/rewrite-regression-probe-pack/mcp
claude mcp add --transport http rewrite-regression-probe-pack https://textforagents.com/products/rewrite-regression-probe-pack/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [],
    "ask": [
      "mcp__rewrite-regression-probe-pack__rewrite_pack",
      "mcp__rewrite-regression-probe-pack__rewrite_verdict",
      "mcp__rewrite-regression-probe-pack__rewrite_verify_pack",
      "mcp__rewrite-regression-probe-pack__rewrite_family"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as rewrite-regression-probe-pack. Review it before you use it.

Capability tags behind 1 rule
  • mcp__rewrite-regression-probe-pack__rewrite_pack outbound

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.textforagents/rewrite-regression-probe-pack/verify?hash=a45205c53a68d2f150c97eb4b04b57044de4f0b7cb027f97cfaa631a760cb061" | jq -e '.changed == false'

Pinned hash a45205c53a68, from Nov 8, 2026, 11:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.textforagents/rewrite-regression-probe-pack/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.textforagents/rewrite-regression-probe-pack
[![Anlyon Radar](https://radar.anlyon.com/badge/com.textforagents/rewrite-regression-probe-pack.svg)](https://radar.anlyon.com/servers/com.textforagents/rewrite-regression-probe-pack)

Source: MCP Registry. Synced Oct 22, 2026, 00:17 UTC.

Rewrite-regression probe pack MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Rewrite-regression probe pack MCP server safe?

No scan can promise that. What its definitions show: 4 tools, 4 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Rewrite-regression probe pack MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Rewrite-regression probe pack MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Rewrite-regression probe pack MCP server have?

4 tools: 4 write. rewrite_pack, rewrite_verdict, rewrite_verify_pack and rewrite_family.

Does the Rewrite-regression probe pack MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Rewrite-regression probe pack MCP server send data to outside services?

1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): rewrite_pack.

Has the Rewrite-regression probe pack MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 8, 2026.