Pactlyst.ai — PactCheck document review for agents

io.github.Fikpeze123Published by GitHub account Fikpeze123v1.2.0Updated Oct 27, 2026

Score documents and check agent work — signed PactCheck Receipts: proof-of-review for agents.

The publisher's own server: Review Expert

VerifiedStreamable HTTPWeb executableProductivity & WorkflowAI & ML

Overview

AI-generated overview

Remote Pactlyst MCP endpoint that lets an assistant score documents and check its own work, returning signed PactCheck Receipts as proof of review.

What you can do
  • Score documents submitted to the Pactlyst service.
  • Check agent work and obtain signed PactCheck Receipts as proof-of-review.
  • No individual tools are listed in the manifest, so the exact operations are not documented here.
When to use it
Useful when an assistant needs to review or score documents and produce a verifiable, signed record that the review happened, for example to show that agent output was checked before being relied on.
Requirements
Remote streamable HTTP endpoint at api.pactlyst.ai; no local package or runtime needed. A Pactlyst API key is required, sent in the Authorization header as a bearer token. A free key is offered with a limited monthly scan quota.
Before you install
The API key is a secret sent in the Authorization header; keep it out of logs and shared configs. Documents submitted for scoring are sent to a third-party service. The free tier is limited to a small number of scans per month, and further use may require a paid plan.

Installation

In SourceWeft

  1. Open Pactlyst.ai — PactCheck document review for agents in the dashboard and add it to a workspace.
  2. Connect Authorization token credentials. They are stored privately and never shown on public pages.
  3. 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/io.github.Fikpeze123%2Fpactlyst/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.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "pactlyst-ai-pactcheck-document-review-fo": {
      "type": "http",
      "url": "https://api.pactlyst.ai/functions/v1/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

2
  1. v1.2.0LatestOct 26, 2026
  2. v1.0.0Oct 22, 2026

Score

67% 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 listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • 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.

Other Review integrations