Handshakr MCP server
com.handshakr/handshakrhandshakr.comstreamable-httpv0.3.1Scanned
Read-only search of Handshakr's register of B2B suppliers, a record built for AI buying agents.
4 tools: 4 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- 1 finding
Tools listed without sign-in. Remote posture
With Anlyon
Decide which of this server's tools your agent can use.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
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 Handshakr MCP server can do
The Handshakr MCP server is published by handshakr.com, a domain the MCP Registry verified. It has 4 tools. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.
None of its tools reads private data, brings in text other people write, or sends data out.
The fixed checks matched 1 finding (credentials-mention). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 20, 2026, version 0.3.1.
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.
4 tools
Only reads 4Show 4 read-only tools
get_public_pulseRecent public activity in the Handshakr register: suppliers newly published and source pulse events.No findings
Why it is in this group
- The name "get_public_pulse" says "get": a word for reading.
Description, as the server wrote it Recent public activity in the Handshakr register: suppliers newly published and source pulse events. Only suppliers an AI agent may read are named.
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
get_sellerFetch one Handshakr supplier an AI agent may read, by slug.1 finding
Why it is in this group
- The name "get_seller" says "get": a word for reading.
Findings
- Info
The description mentions "Credential".
What this check looks forMatched text
description: "..., and where to fetch the W3C Verifiable Credential and its status."
Description, as the server wrote it Fetch one Handshakr supplier an AI agent may read, by slug. `contactable` says whether the supplier has switched agent access on and may be approached. `description` and `category` are the company's own words or null; text Handshakr wrote from public sources is in `handshakr_summary` / `handshakr_category`, labelled, and is not a fact about the company. `trust_score` is null: no score is computed. `trading_name_of`, when not null, names the registered company this listing is a trading name of (legal name, company number, the passport holding its Companies House record): listings that share a company number there are one company, not several. `verifiable_record` is the latest signed, append-only version of the public passport: its version, sha256, log position, and where to fetch the W3C Verifiable Credential and its status.
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
get_trending_categoriesTop trending supplier categories among the suppliers an AI agent may read, this week vs last week, with delta percentage.No findings
Why it is in this group
- The name "get_trending_categories" says "get": a word for reading.
Description, as the server wrote it Top trending supplier categories among the suppliers an AI agent may read, this week vs last week, with delta percentage. Returns available:false with a reason when too few recently published profiles are categorised to compute a trend, an empty result is never a silent zero.
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
search_sellersSearch the Handshakr suppliers an AI agent may read, by keyword and optional category.No findings
Why it is in this group
- The name "search_sellers" says "search": a word for reading.
Description, as the server wrote it Search the Handshakr suppliers an AI agent may read, by keyword and optional category. Returns name, slug, category, location, description and `contactable`: true only for suppliers who have switched agent access on, the only ones an agent may approach. Claimed suppliers who have not consented are not returned. `description` and `category` are the company's own words or null; text Handshakr wrote from public sources is in `handshakr_summary` / `handshakr_category`, labelled, and is not a fact about the company. `trust_score` is null: no score is computed.
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
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.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
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.
Looked at Nov 20, 2026, 18:18 UTC, unchanged since Nov 20, 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
- 0
- Protocol version
- 2025-06-18
- 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
Findings
Matches of fixed checks, with the text they matched.
- Infoget_seller
The description mentions "Credential".
What this check looks forMatched text
description: "..., and where to fetch the W3C Verifiable Credential and its status."
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools3 changed.~3 changedView diff
- Changed:get_public_pulseOnly readsinputSchema
- Changed:get_trending_categoriesOnly readsinputSchema
- Changed:search_sellersOnly readsinputSchema
Install
Pinned to version 0.3.1. Values in angle brackets are yours to fill in.
claude mcp add --transport http handshakr https://hxshsvkjtvcvmqevguuz.supabase.co/functions/v1/mcpclaude mcp add --transport http handshakr https://hxshsvkjtvcvmqevguuz.supabase.co/functions/v1/mcpRun 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.
{
"permissions": {
"allow": [
"mcp__handshakr__search_sellers",
"mcp__handshakr__get_seller",
"mcp__handshakr__get_public_pulse",
"mcp__handshakr__get_trending_categories"
],
"ask": [],
"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 handshakr. Review it before you use it.
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/com.handshakr/handshakr/verify?hash=13ab64a5394b3c32cc2aef69f2f33d3fc610b49db0ea231430226253aa6df964" | jq -e '.changed == false'Pinned hash 13ab64a5394b, from Nov 20, 2026, 02:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.handshakr/handshakr/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.handshakr/handshakr)Source: MCP Registry. Synced Nov 20, 2026, 02:17 UTC.
Handshakr MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Handshakr MCP server safe?
- No scan can promise that. What its definitions show: 4 tools, all of which only read, and 1 finding from fixed checks. Read-only tools can still pass private data to a model.
Can the Handshakr MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Handshakr 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 Handshakr MCP server have?
- 4 tools: 4 read. search_sellers, get_seller, get_public_pulse and get_trending_categories.
Does the Handshakr MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Handshakr MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Handshakr MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Nov 20, 2026. Every change is on this page and in its Atom feed.