Robin Saige we check the tools AI agents call

CAN-TAP Verified

io.github.morphious33453/can-tap-verified-mcp

Free dofollow backlinks for Canadian businesses. Claim, verify, and track NFC tap analytics.

— the operator's own registry description reported

Publisher io.github.morphious33453 · first seen 2026-08-12 · endpoint https://mcp.can-tap-verified.com

allow
verdict
stale-mid-fast-solo
cluster
ok_tools
answers
5
tools served

Dependency rating derived

allow — stale-mid-fast-solo — safe to depend on

Cluster stale-mid-fast-solo · distinctiveness 0.381 (moderate). Every figure is a percentile or class within the 11,094-server censussee the whole spectrum.

Reach — can an agent get to it?
answersalive_tools
latency32 ms
vs populationfast
protocolstale
authopen
Use — can it use it?
tools5
vs populationmid
capabilities1
harnessA
Trust — can it rely on it?
identitysolo
servers on its host1
verifiabilityunassessed
duplicate inventoryno
drift events0
answers trueno primary

🔏 Signed receipt rr_81647a6a601bfdd5dcf5e8e0 · 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.

Tools last seen

check_backlink_status claim_listing get_business_stats list_free_backlinks search_directory

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 checktools passingok
name is clear & specific5/5
has a description5/5
description is substantive5/5
parameters are typed5/5
parameters are described5/5

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

2024-11-05
protocol version
session model
1.0.0
server version can-tap-verified

Capabilities: tools

Drift

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

History observed

Every probe we made, oldest → newest (2 shown, 2026-08-12 → 2026-08-14). 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)
datetypewhat changed
2026-08-12outcomefirst probe: ok_tools
raw probe records
probed (UTC) outcomehttpmsprotocol
2026-08-14T19:59:52Zok_tools200322024-11-05
2026-08-12T05:35:09Zok_tools200572024-11-05

Watch or embed this verdict

verdict badge

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.morphious33453/can-tap-verified-mcp.svg)](https://robinsaige.com/s/io.github.morphious33453/can-tap-verified-mcp)

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