Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Peer Lookup Tools

REMOTE · TOOLS.PEERLOOKUP.COM

Bounded agent tools: time, hash, UUID, codec, JSON, request identity, and service discovery.

0 this week 75 Trust /100

Last scanned (17 hours ago)

Scores higher than 62% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Developer Tools

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security60
Transport & Reachability100
Schema Quality & AI Usability68
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 415 tokens (~51/item across 8 items; 8 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage79
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 36% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
What we tested

Checks we ran (12)

  • TLS certificate
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 8 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 11 Nov 26 0
    • Stability: 0.97 → pass security
  • 10 Nov 26 0
    • Stability: pass → 0.97 functional
  • 9 Nov 26 0
    • Stability: 0.97 → pass security
  • 8 Nov 26 0
    • Stability: pass → 0.97 functional
  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Oct 26 0
    • Stability: 0.97 → pass security
  • 25 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://tools.peerlookup.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=peerlookup.com CN=WE1,O=Google Trust Services,C=US 18 Nov 2026 16 Feb 2027 ECDSA 256 ECDSA-SHA256 7d25143b9dc6bd750e88cdb66affd834
SANs: peerlookup.com, tools.peerlookup.com, *.tools.peerlookup.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC secure

Validation of tools.peerlookup.com. — Secure

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
peerlookup.com. DS published 2371 13 Verified
tools.peerlookup.com. Verified address RRset verified with the apex keys
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
x-content-type-options nosniff
referrer-policy no-referrer

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://tools.peerlookup.com/mcp Verified 200
http (plaintext) http://tools.peerlookup.com/mcp HTTPS enforced 308 https://tools.peerlookup.com/mcp
MCP tools · 8 exposed · ~392 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
lab_codec ~66

Encode/decode base64, base64url, or hex. Max 4096 bytes. Decode returns UTF-8 text only. Same as POST /api/v1/codec.

NameTypeReqDescription
datastringyes–
encodingstringyes–
opstringyes–

No output schema declared.

No examples provided.

lab_directory ~49

Static curated directory of agent doors (Peer Lookup + boards/catalogs). Same data as GET /api/v1/directory. Optional kind filter.

NameTypeReqDescription
kindstring–Optional filter by entry kind

No output schema declared.

No examples provided.

lab_hash ~60

SHA-256 of a UTF-8 string. Max 4096 bytes after encoding. Body is not stored (same as POST /api/v1/hash).

NameTypeReqDescription
datastringyesUTF-8 text to hash (≤ 4096 encoded bytes)

No output schema declared.

No examples provided.

lab_json ~59

Validate, pretty-print, or canonicalize JSON text (data must be a string). Max 8192 bytes. Same as POST /api/v1/json.

NameTypeReqDescription
datastringyesJSON text as a string
opstringyes–

No output schema declared.

No examples provided.

lab_ping ~22

Liveness check (same as GET /api/v1/ping).

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

lab_time ~30

Current UTC time from the Worker clock (same as GET /api/v1/time). No external time API.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

lab_uuid ~67

Generate (default v7) or validate UUIDs. Batch generate up to 20. Same as GET /api/v1/uuid.

NameTypeReqDescription
actionstring––
countinteger––
idstring–UUID to validate
versioninteger––

No output schema declared.

No examples provided.

lab_whoami ~39

request_id + day-scoped actor_pseudonym for log correlation. Never returns IP. Same as GET /api/v1/whoami.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Install

How do I install the Peer Lookup Tools MCP server?

Peer Lookup Tools is a hosted endpoint at https://tools.peerlookup.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · tools.peerlookup.com

# add to Claude Code
claude mcp add --transport http com-peerlookup-tools 'https://tools.peerlookup.com/mcp'
Common questions

What is the Peer Lookup Tools MCP server?

Peer Lookup Tools is an MCP server listed in the public MCP registry as com.peerlookup/tools. Bounded agent tools: time, hash, UUID, codec, JSON, request identity, and service discovery. This page covers its hosted endpoint (https://tools.peerlookup.com/mcp).

Is the Peer Lookup Tools MCP server safe to use?

Peer Lookup Tools scores 75 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Peer Lookup Tools MCP server expose?

Peer Lookup Tools exposes 8 tools: lab_ping, lab_time, lab_hash, lab_directory, lab_uuid, and 3 more. Their descriptions and schemas cost roughly 392 tokens of context every time the server is loaded.

Does the Peer Lookup Tools MCP server require authentication?

No. We connected to Peer Lookup Tools without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Peer Lookup Tools MCP server still maintained?

Peer Lookup Tools is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Peer Lookup Tools MCP server?

VerifyMCP ran 12 checks on Peer Lookup Tools, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Peer Lookup Tools: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.