Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Pain in the Agent

MCPB · PAININTHEAGENT-MCP-0.2.0.MCPB · SCANNED SEP 21

Humanize, rewrite and analyze prose with one shared Pain in the Agent account allowance.

+6 this week 50 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security13
  • Malware scan not yet available for this package.Unverified
  • Known CVEs could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.Unverified
  • No install/post-install scripts declared.Pass
  • Dependency health could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.Unverified
Provenance & Transparency45
Schema Quality & AI Usability77
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 711 tokens (~101/item across 7 items; 7 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management37
  • Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage95
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 85% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

mcpb · painintheagent-mcp-0.2.0.mcpb

Download bundle
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 21 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

  • 19 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Sept 26 +4
    • Stability: unverified → 0.27 functional
  • 10 Sept 26 44

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Sept 2026 · Analysed mcpb/https://github.com/krllagent/painintheagent-mcp/releases/download/v0.2.0/painintheagent-mcp-0.2.0.mcpb

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem mcpb

Background: How many MCP packages publish verified provenance →

MCP tools · 7 exposed · ~623 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
get_limits ~43

Read this account's character limit and monthly successful-run usage, shared with the website. Does not rewrite text or consume rewrite quota. Running requests also reserve slots until they finish.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_result ~54

Read progress or a result by run_id for any text tool. Never starts model work or uses another run.

NameTypeReqDescription
run_idstringyesThe run_id returned by start_rewrite. Reuse it to retrieve that run.

No output schema declared.

No examples provided.

get_rewrite ~74

Read a previous run by its run_id. Does not start or retry model processing and does not consume rewrite quota. A pending result includes a suggested polling interval. Keep the existing process open while it works.

NameTypeReqDescription
run_idstringyesThe run_id returned by start_rewrite. Reuse it to retrieve that run.

No output schema declared.

No examples provided.

start_ai_detection ~97

Inspect at least 80 words of English or Russian prose for AI-like writing patterns. Shows quoted evidence, not a calibrated authorship probability. Uses one shared run and stores the text. Read with get_result.

NameTypeReqDescription
run_idstringThe run_id returned by start_rewrite. Reuse it to retrieve that run.
textstringyes100–10,000 Unicode characters of prose the user asked to process.

No output schema declared.

No examples provided.

start_humanize ~106

Make targeted style edits with source checks. Optional watermark_removal adds deep rewriting. Uses one shared run, stores submitted text, and returns a run_id. Read with get_result. No private watermark guarantee.

NameTypeReqDescription
run_idstringThe run_id returned by start_rewrite. Reuse it to retrieve that run.
textstringyes100–10,000 Unicode characters of prose the user asked to process.
watermark_removalboolean

No output schema declared.

No examples provided.

start_rewrite ~149

Rewrite 100–10,000 characters through Pain in the Agent, with fidelity checks. Sends text to the hosted service; successful runs use the shared free account quota. Returns a run_id promptly. Keep the MCP process open and call get_rewrite after 15 seconds. No private-key watermark guarantee. Use only for text the user asked to process.

NameTypeReqDescription
run_idstringOptional lowercase UUID for idempotency. Reusing the same ID and input cannot start another model run.
slop_removalbooleanAlso remove formulaic AI phrasing. Off by default.
textstringyesThe complete text to rewrite. Do not include secrets or unrelated files.

No output schema declared.

No examples provided.

start_watermark_comparison ~100

Compare source_text and candidate_text for meaning changes. Uses one shared run and stores both supplied texts. This does not detect Claude or Gemini private watermarks. Read with get_result.

NameTypeReqDescription
candidate_textyes
run_idstringThe run_id returned by start_rewrite. Reuse it to retrieve that run.
source_textstringyes100–10,000 Unicode characters of prose the user asked to process.

No output schema declared.

No examples provided.

Common questions

What is the Pain in the Agent MCP server?

Pain in the Agent is an MCP server listed in the public MCP registry as io.github.krllagent/painintheagent-mcp. Humanize, rewrite and analyze prose with one shared Pain in the Agent account allowance. This page covers its MCPB bundle (https://github.com/krllagent/painintheagent-mcp/releases/download/v0.2.0/painintheagent-mcp-0.2.0.mcpb).

Is the Pain in the Agent MCP server safe to use?

Pain in the Agent scores 50 out of 100 on VerifyMCP. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Pain in the Agent MCP server expose?

Pain in the Agent exposes 7 tools: start_rewrite, get_rewrite, get_limits, start_humanize, start_watermark_comparison, and 2 more. Their descriptions and schemas cost roughly 623 tokens of context every time the server is loaded.

What licence is the Pain in the Agent MCP server under?

Pain in the Agent declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.