Should my agent depend on the MCP server io.github.apayne1987-droid/payne-machine-revenue?

Verdict: allow — mid-slow-solo — safe to depend on As of 2026-09-06T06:21:45Z: a dated observation with receipts, not a warranty.

PAYNE Commercial Truth & Machine Revenue Exchange

io.github.apayne1987-droid/payne-machine-revenue

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

— the operator's own registry description reported

Publisher io.github.apayne1987-droid · first seen 2026-08-23 · endpoint https://payne-machine-revenue-mcp.apayne1987.workers.dev/mcp

allow

verdict

mid-slow-solo

cluster

ok_tools

answers

tools served

Dependency rating derived

allow
allow — alive & usable · retrieval-public ● · V3 has answer key ◐

allow — because answers ●, 21 tools legible (band B) ●, no confirmed drift in 3 probes ●; not yet checked: truth (0 runs)

Cluster mid-slow-solo · distinctiveness 0.515 (moderate). Every figure is a percentile or class within the 15,472-server census — see the whole spectrum.

Does it answer? Q1 · observed

answersalive_tools

latency1123 ms

vs populationslow

protocolcurrent

authopen

Can it be used? Q4 · observed

tools21

vs populationmid

capabilities1

harnessB

Did it hold when checked? Q3–Q4 · derived

identitysolo

servers on its host1

verifiabilityunassessed

duplicate inventoryno

drift events0

answers trueno primary

🔏 Signed receipt rr_250b6adb391f84266b9ef190 · ed25519 · key rs-rcpt-2026-08 — this rating is tamper-evident; an agent gets the full signature from check_server and can verify it against the published key.

Q1Does it answer?alive & usable — 3 probes ●evidence ↓

Q2What is it?retrieval-public ● evidence ↓

Q3Can it be checked?V3 has answer key ◐evidence ↓

Q4Did it hold?harness B · truth not yet run · no drift ●evidence ↓

Q5What company does it keep?mid-slow-solo · 1 on its host (context, not verdict) ◐evidence ↓

● observed · ◐ derived · ○ reported — the verdict synthesizes Q1–Q4; Q5 is context. Methodology →

History observed

Every probe we made, oldest → newest (3 shown, 2026-08-23 → 2026-09-06). Green answered · amber answered-but-walled · red no useful answer. A gap in our cadence is a gap in coverage, not evidence about the server.

changelog (1 events)

date	type	what changed
2026-08-23	outcome	first probe: ok_tools

What kind of tools these are derived

Verification only means something relative to a tool's NATURE — an email-sender has no "true answer", a generator has no answer key. Classification evidence: classified from tool names/descriptions/annotations WE OBSERVED. What checking applies to each kind (the full methodology →):

nature	tools	meaning	what checking applies
retrieval-public	9	serves public facts	truth-checkable against a public source — the V-ladder applies in full
action	4	changes the world	no true answer exists; we check the CONTRACT (destructive/read-only/idempotent declarations, error legibility) and never fire real actions
unclassified	4	not classifiable from its text	Tier-1 only until its tools describe themselves
computational	2	deterministic transforms	self-checkable by re-computation and known-answer tests
generative	1	creates content	no answer key exists; disclosure + stability checks, never truth verdicts
orchestration	1	routes other tools	identity + fronted-service disclosure checks (gateway vs costume)

Tools last seen observed

base_block_number base_contract_code base_erc20_allowance base_erc20_balance base_native_balance base_nonce base_token_supply base_transaction commercial_terms_diff domain_intelligence federal_opportunity_search machine_revenue_router opportunity_changefeed partner_attribution_gate personalization_evidence_gate probe source_freshness_score verify_commercial_truth verify_deadline_eligibility web_read x402_preflight

Harness readiness observed

Can an agent's harness pick this tool and call it correctly? Graded on the three things an agent reads — name, description, typed parameters. Band B — usable, with rough edges.

legibility check	tools passing	ok
name is clear & specific	21/21	✓
has a description	21/21	✓
description is substantive	21/21	✓
parameters are typed	21/21	✓
parameters are described	1/21	1/21

21 of 21 tools graded · 21 with a captured input schema. RS-008, Tier-1 — no domain knowledge, applies to any tool. “Alive” is not the same as “usable”.

Truth checks observed

Not in the Tier-2 trade lane, or not yet checked. Tier-2 re-derives a server's answers against published primary sources — see truth checks.

Protocol conformance observed

2025-06-18

protocol version

—

session model

0.5.0

server version PAYNE Machine Revenue Exchange

Capabilities: tools

Drift observed

No confirmed drift on record. Baseline set 2026-09-06; changes appear here after human review.

raw probe records

probed (UTC)	outcome	http	ms	protocol
2026-09-06T06:15:44Z	ok_tools	200	1123	2025-06-18
2026-08-30T06:15:20Z	ok_tools	200	1268	2025-06-18
2026-08-23T06:13:09Z	ok_tools	200	1579	2025-06-18

Watch or embed this verdict

Operators: put the live verdict in your README — it updates with every census, links back here, and is a dated observation, never a warranty:

[![Robin Saige verdict](https://robinsaige.com/badge/io.github.apayne1987-droid/payne-machine-revenue.svg)](https://robinsaige.com/s/io.github.apayne1987-droid/payne-machine-revenue)

Depend on it? Subscribe to its change feed — outcome changes and confirmed drift, no account needed. Building on it? The full dossier as JSON — verdict, rating, truth checks, history — stable enough to gate CI on.

← overview

Operator of this server? Everything we hold about it is on this page — free, no account, for anyone. Wrong attribution, stale probe, misclassification? Dispute this record →