Should my agent depend on the MCP server ru.maxzoa/1cent?

Verdict: allow — rich-slow-solo — safe to depend on As of 2026-09-13T06:22:43Z: a dated observation with receipts, not a warranty.

1cent Web Intelligence for AI Agents

ru.maxzoa/1cent

SSRF-safe web intelligence: 4 outcomes, 43 paid x402 tools, 3 free tools and a URL preview.

— the operator's own registry description reported

Publisher ru.maxzoa · first seen 2026-08-12 · endpoint https://1cent.maxzoa.ru/mcp

allow

verdict

rich-slow-solo

cluster

ok_tools

answers

tools served

Dependency rating derived

allow
allow — alive & usable · retrieval-public ● · V1 shows its work ◐

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

Cluster rich-slow-solo · distinctiveness 0.949 (unusual). Every figure is a percentile or class within the 19,148-server census — see the whole spectrum.

Does it answer? Q1 · observed

answersalive_tools

latency1436 ms

vs populationslow

protocolcurrent

authopen

Can it be used? Q4 · observed

tools46

vs populationhigh

capabilities4

harnessA

Did it hold when checked? Q3–Q4 · derived

identitysolo

servers on its host1

verifiabilityunassessed

duplicate inventoryno

drift events0

answers trueno primary

🔏 Signed receipt rr_2c32816c58ffe2c80dfd3d05 · 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 — 7 probes ●evidence ↓

Q2What is it?retrieval-public ● evidence ↓

Q3Can it be checked?V1 shows its work ◐evidence ↓

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

Q5What company does it keep?rich-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 (7 shown, 2026-08-12 → 2026-09-13). 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 (2 events)

date	type	what changed
2026-09-13	outcome	ok_tools (was not_mcp)
2026-08-12	outcome	first probe: not_mcp

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	39	serves public facts	truth-checkable against a public source — the V-ladder applies in full
computational	4	deterministic transforms	self-checkable by re-computation and known-answer tests
action	2	changes the world	no true answer exists; we check the CONTRACT (destructive/read-only/idempotent declarations, error legibility) and never fire real actions
generative	1	creates content	no answer key exists; disclosure + stability checks, never truth verdicts

Tools last seen observed

catalog.tools.search demo.live.pulse demo.url.pulse web.batch.url_status web.site.coherence web.site.feeds web.site.llms_txt web.site.openapi web.site.robots web.site.security_txt web.site.sitemaps web.url.access_flags web.url.accessibility web.url.canonical web.url.changed web.url.citations web.url.content_quality web.url.content_type web.url.diff web.url.extract web.url.hash web.url.headers web.url.headings web.url.images web.url.jsonld web.url.language web.url.links web.url.localization web.url.markdown web.url.metadata web.url.passport web.url.performance web.url.policy web.url.pulse web.url.rag_chunks web.url.redirects web.url.schema_validation web.url.security_headers web.url.social_cards web.url.status web.url.tables web.url.technology web.url.text web.url.timing web.url.tls web.url.word_stats

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 A — an agent can pick and call these reliably.

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

46 of 46 tools graded · 46 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

1.28.1

server version 1cent URL Intelligence

Capabilities: experimental prompts resources tools

Drift observed

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

raw probe records

probed (UTC)	outcome	http	ms	protocol
2026-09-13T06:19:14Z	ok_tools	200	1436	2025-06-18
2026-09-06T06:18:08Z	not_mcp	308	1422
2026-08-30T06:17:48Z	not_mcp	308	2326
2026-08-23T06:14:57Z	not_mcp	308	2713
2026-08-16T06:14:18Z	not_mcp	308	1018
2026-08-14T20:00:40Z	not_mcp	308	1601
2026-08-12T05:35:54Z	not_mcp	308	1039

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/ru.maxzoa/1cent.svg)](https://robinsaige.com/s/ru.maxzoa/1cent)

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 →