Verify

com.kenoodlPublished by kenoodl.comOfficial publisherv1.0.1Updated Oct 25, 2026

Runs your code against a contract; HELD or BROKE at the exact input. Deterministic. 0.10 USDC/call.

VerifiedStreamable HTTPWeb executableDeveloper ToolsSecurity & Monitoring

Overview

AI-generated overview

A remote MCP server that runs submitted code against a stated contract in a sealed sandbox and returns a deterministic HELD or BROKE verdict at the exact input.

What you can do
Verify code against a contract: submit code and the expected contract, and the server executes it in a sealed sandbox and returns a deterministic HELD or BROKE result at the exact input, as an outside check before code crosses a consequence boundary such as merging, deploying, publishing, settling a payout, or reporting work done.
When to use it
Use it when you want an independent, outside check on code before merging, deploying, publishing, paying out on it, or declaring it finished, rather than relying only on a self-audit written inside the same frame.
Requirements
A remote endpoint at kenoodl.com over streamable HTTP; no authentication, environment variables, or headers are declared. Each call costs 0.10 USDC, so a payment arrangement is needed.
Before you install
Each call costs 0.10 USDC, so usage spends money. Submitted code is sent to a third-party remote service for execution. The server states that a self-audit verifies consistency, never completeness, so treat a HELD result as limited to the stated contract and input.

Installation

In SourceWeft

  1. Open Verify 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/com.kenoodl%2Fverify/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": {
    "verify": {
      "type": "http",
      "url": "https://kenoodl.com/mcp"
    }
  }
}

Tools

1

verify

An outside check on code, executed in a sealed sandbox. Call it before code crosses a consequence boundary: before you merge it, deploy it, publish it, settle a payout on it, or report it done. A self-audit verifies consistency, never completeness: a check written inside the frame that produced the code passes on the code's own assumptions. This is the check that is not you. Also call it when a fix passes your own check but the target still fails; that means your check shares the code's assumption and cannot see the error. INPUT: code (JavaScript/Node or Python 3 source, deterministic only) plus ONE of: contract {fn, examples:[{call,expected}]} (copy call and expected from the test or spec the consequence depends on), or assumption (plain-language claim, weaker read). It checks the code against the contract exactly as given. VERDICTS (synchronous): BROKE: the code violates your contract, with the exact input and a rerunnable proof; do not proceed. HELD: the code meets the contract you gave; proceed on that contract, and nothing more. FINDINGS: a stated property strains under a generated input; check it before proceeding. DROP: not deterministically checkable. PAYMENT: 0.10 USDC per call, x402 v2 on Base, no account. Every delivered verdict is charged, HELD and DROP included. If no verdict is produced, the payment authorization is cancelled and you are not charged.

Parameterscoderequiredcontractassumption

Version history

1
  1. v1.0.1LatestSep 16, 2026

Score

72% 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 listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

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