Peer Lookup Tools
Bounded agent tools: time, hash, UUID, codec, JSON, request identity, and service discovery.
What it can do
What data it sees
Do you need an account
No: the server works without sign-in
Bounded agent tools: time, hash, UUID, codec, JSON, request identity, and service discovery.
How to connect
How to connect Peer Lookup Tools to Claude
The server address to paste into Claude settings:
https://tools.peerlookup.com/mcp
- Open Claude (claude.ai or the desktop app).
- Go to Settings → Connectors.
- Click Add custom connector.
- Paste the server address copied below into Remote MCP server URL and click Add.
- In a chat, click + → Connectors and switch the new connector on.
Custom connectors are available on Free, Pro, Max, Team and Enterprise plans (Free is limited to one). On Team and Enterprise an organization Owner adds the connector first under Organization settings → Connectors.
Authorization
After you click Add, a sign-in window for the service opens. Sign in with your own account and approve access. Claude never sees your password.
How to connect Peer Lookup Tools to ChatGPT
The server address to paste into ChatGPT settings:
https://tools.peerlookup.com/mcp
- Open ChatGPT in a browser (chatgpt.com). A Plus, Pro, Business, Enterprise or Edu plan is required.
- Turn on developer mode once: Settings → Apps → Advanced settings → Developer mode.
- Open Settings → Connectors and click Create.
- Fill in the form: Name (anything), Description (one line about what the service does), MCP server URL (copy it below).
- Under Authentication choose OAuth if the service requires sign-in, otherwise None. Click Create.
- In a new chat open + → Apps/Connectors and enable the connector.
OpenAI has renamed this section before (Connectors → Apps/Plugins). If the label differs, search settings for "developer mode". On Business/Enterprise workspaces an admin must allow custom connectors first.
Authorization
On first use ChatGPT opens the service's sign-in window. Sign in and approve access.
How to connect Peer Lookup Tools to Cursor
The server address to paste into Cursor settings:
https://tools.peerlookup.com/mcp
Fastest: click Open in Cursor below and confirm the prompt.
Manually:
- In Cursor open Settings → Cursor Settings → MCP and click Add new global MCP server.
- Paste the JSON copied below into
~/.cursor/mcp.json(per project:.cursor/mcp.jsonin the repo root). - Save the file. The server appears in the MCP list; authorize it there if asked.
Authorization
If the service needs sign-in, an authorize button appears next to the server in the MCP list.
Server tool list (8)
Raw names from tools/list. Only developers need these.
| 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_hash | SHA-256 of a UTF-8 string. Max 4096 bytes after encoding. Body is not stored (same as POST /api/v1/hash). |
| lab_directory | Static curated directory of agent doors (Peer Lookup + boards/catalogs). Same data as GET /api/v1/directory. Optional kind filter. |
| lab_uuid | Generate (default v7) or validate UUIDs. Batch generate up to 20. Same as GET /api/v1/uuid. |
| lab_codec | Encode/decode base64, base64url, or hex. Max 4096 bytes. Decode returns UTF-8 text only. Same as POST /api/v1/codec. |
| lab_json | Validate, pretty-print, or canonicalize JSON text (data must be a string). Max 8192 bytes. Same as POST /api/v1/json. |
| lab_whoami | request_id + day-scoped actor_pseudonym for log correlation. Never returns IP. Same as GET /api/v1/whoami. |