Peer Lookup Tools
REMOTE · TOOLS.PEERLOOKUP.COM · SCANNED SEP 28
Bounded agent tools: time, hash, UUID, codec, JSON, request identity, and service discovery.
Available components
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
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation 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. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
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 Management7
- Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
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
claude mcp add --transport http com-peerlookup-tools 'https://tools.peerlookup.com/mcp'
{
"mcpServers": {
"com-peerlookup-tools": {
"url": "https://tools.peerlookup.com/mcp"
}
}
} {
"servers": {
"com-peerlookup-tools": {
"type": "http",
"url": "https://tools.peerlookup.com/mcp"
}
}
} [mcp_servers.com-peerlookup-tools] url = "https://tools.peerlookup.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-peerlookup-tools": {
"type": "remote",
"url": "https://tools.peerlookup.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-peerlookup-tools --url 'https://tools.peerlookup.com/mcp' --transport streamable-http
mcp_servers:
com-peerlookup-tools:
url: "https://tools.peerlookup.com/mcp" {
"McpServers": {
"com-peerlookup-tools": {
"Transport": "http",
"Url": "https://tools.peerlookup.com/mcp"
}
}
} assistant mcp add com-peerlookup-tools -t streamable-http -u 'https://tools.peerlookup.com/mcp'
{
"mcpServers": {
"com-peerlookup-tools": {
"type": "http",
"url": "https://tools.peerlookup.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 28 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Sept 26 0
- The server changed its declared name: peerlookup-tools → com.peerlookup/tools security
- Stability: unverified → 0.03 ▲ functional
- Server version: 4c9ad30d3dc696c0b128daa9b74d8ba266361fad → 0.2.2-l2.2 functional
- 26 Sept 26 61
First indexed and scored.
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 28 Sept 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 | 19 Sept 2026 | 18 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | e43b24b64ff550e90ed0429109bdbf7c |
| 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. | present | 19718 | 13 | Verified |
| peerlookup.com. | present | 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 |
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 →
lab_codec ~66
Encode/decode base64, base64url, or hex. Max 4096 bytes. Decode returns UTF-8 text only. Same as POST /api/v1/codec.
| Name | Type | Req | Description |
|---|---|---|---|
| data | string | yes | – |
| encoding | string | yes | – |
| op | string | yes | – |
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.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | – | 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).
| Name | Type | Req | Description |
|---|---|---|---|
| data | string | yes | UTF-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.
| Name | Type | Req | Description |
|---|---|---|---|
| data | string | yes | JSON text as a string |
| op | string | yes | – |
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.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | – | – |
| count | integer | – | – |
| id | string | – | UUID to validate |
| version | integer | – | – |
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.
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 62 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 28 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.