LookupLab MCP server
io.github.PpiNeaPpLe/lookuplabPpiNeaPpLestreamable-httpv1.0.0Scanned
Phone carrier, email domain, IP network and DNS checks using your LookupLab account.
4 tools: 4 change things.
- Reads private data · 0
- Reads text others write · 4
- Can send data out · 0
- 3 findings
Tools listed without sign-in. Remote posture
With Anlyon
4 tools here change things. Govern them.
- 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 LookupLab MCP server can do
The LookupLab MCP server is published by the GitHub account PpiNeaPpLe. It has 4 tools. It can create or change data (4 tools: phone_lookup, email_verify, ip_lookup and dns_check), but cannot delete data. None of its tools only reads.
4 tools bring in text other people can write (phone_lookup, email_verify, ip_lookup and 1 more).
The fixed checks matched 3 findings (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 16, 2026, version 1.0.0.
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
Changes things 4Claude Code: ask
dns_checkInspect a user-provided domain's MX, SPF, DMARC or DKIM record and report issues.Reads text others write1 finding
Why it is in this group
- The description's first verb is "inspect": a word for reading.
- The server marks it as not read-only (readOnlyHint: false).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- untrusted-inputThe description's first sentence says "inspect" and "issue": it reads issues, which other people can write.
Findings
- Warn
The server marks "dns_check" as not read-only (readOnlyHint: false), and its words say it reads.
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":true}; The description's first verb is "inspect": a word for reading.
Description, as the server wrote it Inspect a user-provided domain's MX, SPF, DMARC or DKIM record and report issues. Does not change DNS. DKIM requires a selector. Uses 1 existing account credit for a successful check.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
email_verifyCheck an email address supplied by the user for syntax, MX records, disposable-domain and role-address indicators.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Check an email address supplied by the user for syntax, MX records, disposable-domain and role-address indicators. Does not prove mailbox ownership or guarantee delivery. Uses 1 existing account credit for a successful check; does not send email.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
ip_lookupLook up approximate IP location and network/provider indicators for an IP address supplied by the user.Reads text others write1 finding
Why it is in this group
- The name "ip_lookup" says "lookup": a word for reading.
- The server marks it as not read-only (readOnlyHint: false).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Findings
- Warn
The server marks "ip_lookup" as not read-only (readOnlyHint: false), and its words say it reads.
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":true}; The name "ip_lookup" says "lookup": a word for reading.
Description, as the server wrote it Look up approximate IP location and network/provider indicators for an IP address supplied by the user. IP location is not a person's precise location or identity; privacy flags may be unavailable. Uses 1 existing account credit for a successful check.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
phone_lookupCheck a user-provided phone number for carrier and line type.Reads text others write1 finding
Why it is in this group
- The name "phone_lookup" says "lookup": a word for reading.
- The server marks it as not read-only (readOnlyHint: false).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Findings
- Warn
The server marks "phone_lookup" as not read-only (readOnlyHint: false), and its words say it reads.
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":true}; The name "phone_lookup" says "lookup": a word for reading.
Description, as the server wrote it Check a user-provided phone number for carrier and line type. Optional US/CA caller-name data is a carrier listing, not identity verification. Uses existing account credits: 1 for landline/VoIP/toll-free, 3 for mobile or unknown; caller name adds 2. Reserves up to 5 credits before execution. Does not place calls or send messages.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
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 outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write4
- 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, 19:00 UTC, unchanged since Oct 22, 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
- 4
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://lookuplab.io/.well-known/oauth-protected-resource/api/mcp
- Authorization servers
- https://lookuplab.io
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- yes
- Client ID metadata documents
- no
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 4 tools that change things (4 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://lookuplab.io/api/mcp: tools/list returned 4 tools to an anonymous client, including phone_lookup (write), email_verify (write), ip_lookup (write), dns_check (write)
Findings
Matches of fixed checks, with the text they matched.
- Warnphone_lookup
The server marks "phone_lookup" as not read-only (readOnlyHint: false), and its words say it reads.
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":true}; The name "phone_lookup" says "lookup": a word for reading.
- Warnip_lookup
The server marks "ip_lookup" as not read-only (readOnlyHint: false), and its words say it reads.
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":true}; The name "ip_lookup" says "lookup": a word for reading.
- Warndns_check
The server marks "dns_check" as not read-only (readOnlyHint: false), and its words say it reads.
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":true}; The description's first verb is "inspect": a word for reading.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http lookuplab https://lookuplab.io/api/mcp --header 'X-API-Key: <your-x-api-key>'claude mcp add --transport http lookuplab https://lookuplab.io/api/mcp --header 'X-API-Key: <your-x-api-key>'Run 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": [],
"ask": [
"mcp__lookuplab__phone_lookup",
"mcp__lookuplab__email_verify",
"mcp__lookuplab__ip_lookup",
"mcp__lookuplab__dns_check"
],
"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 lookuplab. Review it before you use it.
Capability tags behind 4 rules
- mcp__lookuplab__phone_lookup untrusted-input
- mcp__lookuplab__email_verify untrusted-input
- mcp__lookuplab__ip_lookup untrusted-input
- mcp__lookuplab__dns_check untrusted-input
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/io.github.PpiNeaPpLe/lookuplab/verify?hash=b004820994fd1ec8190626b2cab90e7ac6ce83e6e29ddde2a96eb018720ecd4a" | jq -e '.changed == false'Pinned hash b004820994fd, from Nov 16, 2026, 03:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.PpiNeaPpLe/lookuplab/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.PpiNeaPpLe/lookuplab)Source: MCP Registry · repository. Synced Oct 21, 2026, 18:18 UTC.
LookupLab MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the LookupLab MCP server safe?
- No scan can promise that. What its definitions show: 4 tools, 4 of which can change, send or delete something, and 3 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the LookupLab MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the LookupLab 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 LookupLab MCP server have?
- 4 tools: 4 write. phone_lookup, email_verify, ip_lookup and dns_check.
Does the LookupLab MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the LookupLab MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the LookupLab MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 16, 2026.