Agreement Obligation Reader

io.github.Wxt-aiPublished by GitHub account Wxt-aiv1.0.7Updated Oct 8, 2026

Prepare an agreement obligation schedule

VerifiedStreamable HTTPWeb executableProductivity & Workflow

Overview

AI-generated overview

Remote MCP server that lets an assistant prepare an agreement obligation schedule from contract terms.

What you can do
  • Prepare an agreement obligation schedule.
  • The registry lists no individual tools, so the exact operations are not documented; the stated purpose is assembling a schedule of obligations from an agreement.
When to use it
Worth considering when you want an assistant to turn agreement or contract text into a structured schedule of obligations, for example during contract review or compliance tracking.
Requirements
A remote streamable HTTP endpoint; no package, environment variables, headers or authentication are declared. The endpoint is a trycloudflare.com address, which is typically a temporary tunnel.
Before you install
No authentication is declared, so anyone with the endpoint address may be able to reach it; avoid sending confidential contract text. The trycloudflare.com hostname suggests an ephemeral tunnel that may move or disappear. No tool list or documentation is provided, so behavior cannot be verified in advance.

Installation

In SourceWeft

  1. Open Agreement Obligation Reader in the dashboard and add it to a workspace.
  2. 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.Wxt-ai%2Fagreement-obligation-reader/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": {
    "agreement-obligation-reader": {
      "type": "http",
      "url": "https://openings-vote-drilling-initially.trycloudflare.com/mcp/agreement-obligation-reader"
    }
  }
}

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.0.7LatestSep 16, 2026

Score

28% 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

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • 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.