Skip to content

CAN-TAP Verified MCP server

io.github.morphious33453/can-tap-verified-mcpmorphious33453streamable-httpv1.0.0Scanned

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

5 tools: 1 change things and 4 only read.

Tools: 0 delete, 0 irreversible, 1 write, 4 read.
  • Reads private data · 2
  • Reads text others write · 1
  • Can send data out · 1
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here changes things. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the CAN-TAP Verified MCP server can do

The CAN-TAP Verified MCP server is published by the GitHub account morphious33453. It has 5 tools. It can create or change data (1 tool: claim_listing), but cannot delete data. 4 tools only read.

2 tools read private data (check_backlink_status and search_directory); 1 tool brings in text other people can write (get_business_stats); 1 tool can send data out of your system (claim_listing). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 20, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

5 tools

Changes things 1Claude Code: ask
  • claim_listingClaim a free verified directory listing for a Canadian business — receives a permanent dofollow backlink upon domain ownership verification.Can send data outNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    What it can reach

    • outboundThe input takes a destination (input.phone): what the tool writes goes there.
    Description, as the server wrote it
    Claim a free verified directory listing for a Canadian business — receives a permanent dofollow backlink upon domain ownership verification. Use this when a user wants to add their business to the CAN-TAP Verified directory. Rate-limited to 5 claims per IP per day.
Only reads 4Show 4 read-only tools
  • get_business_statsGet NFC tap and review analytics for a CAN-TAP Verified business.Reads text others writeNo findings

    Why it is in this group

    • The name "get_business_stats" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "get" and "review": it reads comments, which other people can write.
    Description, as the server wrote it
    Get NFC tap and review analytics for a CAN-TAP Verified business. Returns total taps, positive vs concern split, average star rating, and recent activity. Use this for businesses that own a CAN-TAP NFC review stand.
  • search_directorySearch the CAN-TAP Verified directory of 3,000+ real Canadian businesses by name, city, trade, or any combination.Reads private dataNo findings

    Why it is in this group

    • The name "search_directory" says "search": a word for reading.

    What it can reach

    • private-dataThe name "search_directory" says "search" and "directory": it reads files.
    • private-dataThe description's first sentence says "search" and "directory": it reads files.
    Description, as the server wrote it
    Search the CAN-TAP Verified directory of 3,000+ real Canadian businesses by name, city, trade, or any combination. Returns matching listings with their URLs and claim status.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

2 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 1 outbound tool breaks every one.

Reads private data2
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out1
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
deny to break every path
{
  "permissions": {
    "deny": [
      "mcp__can-tap-verified__claim_listing"
    ]
  }
}

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:08 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
1
Protocol version
2024-11-05
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://mcp.can-tap-verified.com: tools/list returned 5 tools to an anonymous client, including claim_listing (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http can-tap-verified https://mcp.can-tap-verified.com
claude mcp add --transport http can-tap-verified https://mcp.can-tap-verified.com

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__can-tap-verified__list_free_backlinks",
      "mcp__can-tap-verified__check_backlink_status",
      "mcp__can-tap-verified__get_business_stats",
      "mcp__can-tap-verified__search_directory"
    ],
    "ask": [
      "mcp__can-tap-verified__claim_listing"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as can-tap-verified. Review it before you use it.

Capability tags behind 4 rules
  • mcp__can-tap-verified__claim_listing outbound
  • mcp__can-tap-verified__check_backlink_status private-data
  • mcp__can-tap-verified__get_business_stats untrusted-input
  • mcp__can-tap-verified__search_directory private-data

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.morphious33453/can-tap-verified-mcp/verify?hash=0a462db4d2a0d272739b590d9b9a0187ad2079694743404f840077acccfb82fd" | jq -e '.changed == false'

Pinned hash 0a462db4d2a0, from Nov 20, 2026, 03:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.morphious33453/can-tap-verified-mcp/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.morphious33453/can-tap-verified-mcp
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.morphious33453/can-tap-verified-mcp.svg)](https://radar.anlyon.com/servers/io.github.morphious33453/can-tap-verified-mcp)

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:41 UTC.

CAN-TAP Verified MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the CAN-TAP Verified MCP server safe?

No scan can promise that. What its definitions show: 5 tools, 1 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the CAN-TAP Verified MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the CAN-TAP Verified MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the CAN-TAP Verified MCP server have?

5 tools: 1 write, 4 read. claim_listing, list_free_backlinks, check_backlink_status, get_business_stats and search_directory.

Does the CAN-TAP Verified MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the CAN-TAP Verified MCP server send data to outside services?

1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): claim_listing.

Has the CAN-TAP Verified MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 20, 2026.