# PAYNE Commercial Truth & Machine Revenue Exchange (remote · payne-machine-revenue-mcp.apayne1987.workers.dev)

Verify live jobs/RFPs, deadlines, eligibility, terms changes, and Base/web data via x402.

- Trust score: 70/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-21

## Components

- remote · `payne-machine-revenue-mcp.apayne1987.workers.dev`: 70/100 (this document), [markdown](https://verifymcp.io/servers/apayne1987-droid-payne-machine-revenue/payne-machine-revenue-mcp.md), [page](https://verifymcp.io/servers/apayne1987-droid-payne-machine-revenue/payne-machine-revenue-mcp)

## Channel facts

- Endpoint: `https://payne-machine-revenue-mcp.apayne1987.workers.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.3.1`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-21.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 21 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 66/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 1027 tokens (~48/item across 21 items; 21 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 67/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 21 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 21 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the PAYNE Commercial Truth & Machine Revenue Exchange MCP server?

PAYNE Commercial Truth & Machine Revenue Exchange is a hosted endpoint at https://payne-machine-revenue-mcp.apayne1987.workers.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http apayne1987-droid-payne-machine-revenue 'https://payne-machine-revenue-mcp.apayne1987.workers.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "apayne1987-droid-payne-machine-revenue": {
      "url": "https://payne-machine-revenue-mcp.apayne1987.workers.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "apayne1987-droid-payne-machine-revenue": {
      "type": "http",
      "url": "https://payne-machine-revenue-mcp.apayne1987.workers.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.apayne1987-droid-payne-machine-revenue]
url = "https://payne-machine-revenue-mcp.apayne1987.workers.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "apayne1987-droid-payne-machine-revenue": {
      "type": "remote",
      "url": "https://payne-machine-revenue-mcp.apayne1987.workers.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add apayne1987-droid-payne-machine-revenue --url 'https://payne-machine-revenue-mcp.apayne1987.workers.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  apayne1987-droid-payne-machine-revenue:
    url: "https://payne-machine-revenue-mcp.apayne1987.workers.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "apayne1987-droid-payne-machine-revenue": {
      "Transport": "http",
      "Url": "https://payne-machine-revenue-mcp.apayne1987.workers.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add apayne1987-droid-payne-machine-revenue -t streamable-http -u 'https://payne-machine-revenue-mcp.apayne1987.workers.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "apayne1987-droid-payne-machine-revenue": {
      "type": "http",
      "url": "https://payne-machine-revenue-mcp.apayne1987.workers.dev/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-21 (score 70, +1)

- [security] Stability: 0.97 → pass

### 2026-09-19 (score 69, +1)

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

### 2026-09-17 (score 68, +1)

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

### 2026-09-15 (score 67, +1)

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

### 2026-09-13 (score 66, +1)

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

### 2026-09-11 (score 65, +1)

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

### 2026-09-08 (score 64, +1)

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

### 2026-09-06 (score 63, +1)

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

## MCP tools (21)

### `probe` (~47 tokens)

Free reachability and stale-risk probe for a public job, RFP, grant, auction, listing, pricing page, or other commercial URL before buying full verification.

Input parameters:

- `url` (string, required)

### `web_read` (~59 tokens)

Fetch a public URL as bounded clean markdown-ish text with metadata, links, JSON-LD, and content hash for agent research and verification.

Input parameters:

- `includeLinks` (boolean)
- `maxChars` (integer)
- `url` (string, required)

### `verify_commercial_truth` (~62 tokens)

Check whether a job, RFP, grant, auction, marketplace listing, partner program, pricing page, or commercial offer is still live; verify deadline and economics, flag contradictions/stale evidence, and return RELEASE or HOLD.

Input parameters:

- `url` (string, required)

### `verify_deadline_eligibility` (~53 tokens)

Extract and gate submission deadline, timezone, eligibility, geography, credential requirements, and disqualifiers for jobs, RFPs, grants, competitions, and other opportunities.

Input parameters:

- `url` (string, required)

### `commercial_terms_diff` (~57 tokens)

Compare two versions of commercial text and find material changes in pricing, fees, payout, commission, eligibility, renewal, restrictions, SLA, or other economic terms.

Input parameters:

- `afterText` (string, required)
- `beforeText` (string, required)

### `personalization_evidence_gate` (~49 tokens)

Fact-check personalized sales, recruiting, partnership, or outreach copy against supplied evidence and block unsupported claims before an automated send.

Input parameters:

- `draft` (string, required)
- `evidenceText` (string, required)

### `partner_attribution_gate` (~46 tokens)

Check referral or partner-program approval, attribution, duplicate/collision risk, consent, eligibility, and compliance gates before an introduction or lead handoff.

Input parameters:

- `payload` (object, required)

### `source_freshness_score` (~60 tokens)

Score whether web evidence is current enough for a consequential decision such as applying, bidding, pricing, outreach, procurement, or partner routing; returns reverify-before-action guidance.

Input parameters:

- `claimClass` (string)
- `url` (string, required)

### `opportunity_changefeed` (~58 tokens)

Compare opportunity snapshots and emit NEW, CHANGED, and REMOVED_OR_CLOSED events for job boards, RFP feeds, grants, auctions, and other monitored commercial sources.

Input parameters:

- `current` (array, required)
- `previous` (array, required)

### `machine_revenue_router` (~61 tokens)

Rank direct service, marketplace work, referral, data/API, product, and other monetization routes by probability-adjusted expected gross profit, automation, time-to-cash, and risk.

Input parameters:

- `routes` (array, required)
- `signal` (object)

### `domain_intelligence` (~60 tokens)

Combine privacy-filtered RDAP and DNS facts for a public domain: registrar, age, expiry, DNSSEC, nameservers, MX, SPF, DMARC and risk signals.

Input parameters:

- `domain` (string, required)
- `timeoutMs` (integer)

### `x402_preflight` (~59 tokens)

Run an unpaid Coinbase/CDP x402 configuration preflight before an agent spends: required checks, simulation verdict, warnings and payment requirements.

Input parameters:

- `method` (string)
- `resource` (string, required)
- `timeoutMs` (integer)

### `federal_opportunity_search` (~70 tokens)

Search live SAM.gov contract opportunities by title/query and return normalized open notices ranked by relevance and deadline urgency. Discovery only; never submits a bid.

Input parameters:

- `limit` (integer)
- `lookbackDays` (integer)
- `query` (string, required)
- `timeoutMs` (integer)

### `base_block_number` (~24 tokens)

Read the current Base mainnet block number with RPC-source attribution and fallback.

### `base_native_balance` (~31 tokens)

Read an address native ETH balance on Base mainnet in wei and ETH.

Input parameters:

- `address` (string, required)

### `base_erc20_balance` (~44 tokens)

Read an ERC-20 balance on Base with decimals, symbol, atomic amount and formatted amount.

Input parameters:

- `owner` (string, required)
- `token` (string, required)

### `base_transaction` (~37 tokens)

Read and summarize a Base transaction plus receipt: status, value, gas, fee, logs and contract creation.

Input parameters:

- `hash` (string, required)

### `base_nonce` (~25 tokens)

Read the latest transaction nonce for a Base address.

Input parameters:

- `address` (string, required)

### `base_token_supply` (~33 tokens)

Read an ERC-20 total supply on Base with decimals, symbol and formatted supply.

Input parameters:

- `token` (string, required)

### `base_erc20_allowance` (~51 tokens)

Read an ERC-20 owner-to-spender allowance on Base and flag unlimited-like approvals.

Input parameters:

- `owner` (string, required)
- `spender` (string, required)
- `token` (string, required)

### `base_contract_code` (~41 tokens)

Check whether a Base address has contract bytecode; returns byte length, prefix and SHA-256 hash without dumping full code.

Input parameters:

- `address` (string, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/apayne1987-droid-payne-machine-revenue/payne-machine-revenue-mcp#diagnostics

## Score history

- 2026-09-21: 70
- 2026-09-20: 69
- 2026-09-19: 69
- 2026-09-18: 68
- 2026-09-17: 68
- 2026-09-16: 67
- 2026-09-15: 67
- 2026-09-14: 66
- 2026-09-13: 66
- 2026-09-12: 65
- 2026-09-11: 65
- 2026-09-10: 64
- 2026-09-09: 64
- 2026-09-08: 64
- 2026-09-07: 63
- 2026-09-06: 63
- 2026-09-05: 62
- 2026-09-04: 62
- 2026-09-03: 61
- 2026-09-02: 61
- 2026-09-01: 60
- 2026-08-31: 60
- 2026-08-30: 59
- 2026-08-29: 59
- 2026-08-28: 58
- 2026-08-27: 58
- 2026-08-26: 57
- 2026-08-25: 55
- 2026-08-24: 54
- 2026-08-23: 54

## Common questions

### What is the PAYNE Commercial Truth & Machine Revenue Exchange MCP server?

PAYNE Commercial Truth & Machine Revenue Exchange is an MCP server listed in the public MCP registry as io.github.apayne1987-droid/payne-machine-revenue. Verify live jobs/RFPs, deadlines, eligibility, terms changes, and Base/web data via x402. This page covers its hosted endpoint (https://payne-machine-revenue-mcp.apayne1987.workers.dev/mcp).

### Is the PAYNE Commercial Truth & Machine Revenue Exchange MCP server safe to use?

PAYNE Commercial Truth & Machine Revenue Exchange scores 70 out of 100 on VerifyMCP. 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 PAYNE Commercial Truth & Machine Revenue Exchange MCP server expose?

PAYNE Commercial Truth & Machine Revenue Exchange exposes 21 tools: probe, web_read, verify_commercial_truth, verify_deadline_eligibility, commercial_terms_diff, and 16 more. Their descriptions and schemas cost roughly 1,027 tokens of context every time the server is loaded.

### Does the PAYNE Commercial Truth & Machine Revenue Exchange MCP server require authentication?

No. We connected to PAYNE Commercial Truth & Machine Revenue Exchange without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the PAYNE Commercial Truth & Machine Revenue Exchange MCP server still maintained?

PAYNE Commercial Truth & Machine Revenue Exchange is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://payne-machine-revenue-mcp.apayne1987.workers.dev/mcp
- Repository: https://github.com/apayne1987-droid/-payne-autonomous-product-factory
- Changelog RSS feed: https://verifymcp.io/servers/apayne1987-droid-payne-machine-revenue/payne-machine-revenue-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/apayne1987-droid-payne-machine-revenue/payne-machine-revenue-mcp.json
- HTML version of this page: https://verifymcp.io/servers/apayne1987-droid-payne-machine-revenue/payne-machine-revenue-mcp