Peer Lookup Tools MCP Server

by peerlookup Your server? Claim it

answering

Peer Lookup Tools is answering right now. Last checked 4 min ago. It exposes 8 tools.

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

Uptime history 16 days of history

16 days agonow

100.0%

Uptime 24h

92 of 92 checks

Tools

read from the server

62 ms

Response time

average over 24h

open, no key

Access

streamable-http

Nothing serious here today

Today is the operative word: we check Peer Lookup Tools every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 4 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add tools --transport http https://tools.peerlookup.com/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "tools": {
      "url": "https://tools.peerlookup.com/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.tools]
url = "https://tools.peerlookup.com/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "tools": {
      "url": "https://tools.peerlookup.com/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "tools": {
      "url": "https://tools.peerlookup.com/mcp"
    }
  }
}

Available tools 8

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

lab

lab_codec

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

lab_directory

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

lab_hash

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

lab_json

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

lab_ping

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

lab_time

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

lab_uuid

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

lab_whoami

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

Endpoints

URL	Transport	State	Latency	Checked
https://tools.peerlookup.com/mcp	streamable-http	answering	57 ms	4 min ago

Alternatives to Peer Lookup Tools

same job, measured the same way

IssueFoundry Agent Market

by codework-lgtm

Discover agent services and buy IssueFoundry's fractional-cent x402 reliability utilities.

2 tools answering

Jev agent tools

by nomenak

Evidence-oriented code questions, diff review and test selection via a Jev endpoint.

499 installs/wk local only

Codex Pets Registry

by ydb-qdrant-pets

Search, preview, install community Codex pet packs, and discover the pet request flow.

9 tools answering

AgencyAI Commerce MCP

by barnaby-coder

AgencyAI's public MCP for service discovery and AI-readiness assessment.

3 tools answering

oss-search

by sblattj

Fast local and federated OSS code search and repo discovery for AI agents

29 installs/wk local only

Agent Harnesses

by ryanalberts

Agent-harness picks, decision guides, setup templates, and skills; live GitHub/HN discovery.

774 installs/wk local only

multihash identity codec, value discarded

by sadri-dridi

multihash identity codec, value discarded

31 tools answering

Eudi Rp Request Lint

by jmshinhwa

Nine rules that read the JSON your service sends to an EU Digital Identity Wallet

121 installs/wk local only

Peer Lookup Tools — questions

Answers built from our own checks of this server.

What can Peer Lookup Tools do?

It exposes 8 tools, read directly from the server on our last check. Among them: lab_codec, lab_directory, lab_hash, lab_json, lab_ping, lab_time and 2 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Peer Lookup Tools working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 62 ms. The bar chart above shows every period we have measured.

How do I connect Peer Lookup Tools?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Peer Lookup Tools need an API key?

No. Peer Lookup Tools completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 8 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Peer Lookup Tools?

It answers our handshake in 62 ms on average, which is faster than 92% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.