lookmybio
REMOTE · MCP.LOOKMYBIO.COM
Look up creators on lookmybio: public bio pages, their links and published blog posts.
Available components
Last scanned (7 hours ago)
Scores higher than 62% of remote servers
Reachable. Last reached 5 Nov 2026.
Category News and Social
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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability70
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 307 tokens (~76/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
- Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage83
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 50% 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
- 5 Nov 26 +1
- Server version: 1.2.146 → 1.2.149 functional
- 4 Nov 26 0
- Server version: 1.2.141 → 1.2.146 functional
- 3 Nov 26 +1
- Server version: 1.2.137 → 1.2.141 functional
- 2 Nov 26 0
- Server version: 1.2.131 → 1.2.137 functional
- 1 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
- Server version: 1.2.129 → 1.2.131 functional
- 31 Oct 26 71
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 5 Nov 2026 · Probed https://mcp.lookmybio.com/public
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=lookmybio.com | CN=WE1,O=Google Trust Services,C=US | 10 Oct 2026 | 8 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | bdc38857a0ff5d411374fee9dc639909 |
| SANs: lookmybio.com, *.lookmybio.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 insecure
Validation of mcp.lookmybio.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| lookmybio.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
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 |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| content-security-policy | frame-src 'self' https://youtube.com https://*.youtube.com https://youtube-nocookie.com https://*.youtube-nocookie.com https://youtu.be https://vimeo.com https://*.vimeo.com https://tiktok.com https://*.tiktok.com https://player.twitch.tv https://clips.twitch.tv https://www.loom.com https://spotify.com https://*.spotify.com https://soundcloud.com https://*.soundcloud.com https://embed.music.apple.com https://embed.podcasts.apple.com https://bandcamp.com https://*.bandcamp.com https://widget.deezer.com https://twitter.com https://*.twitter.com https://x.com https://*.x.com https://instagram.com https://*.instagram.com https://facebook.com https://*.facebook.com https://*.pinterest.com https://embed.bsky.app https://www.google.com https://maps.google.com https://www.openstreetmap.org https://codepen.io https://*.codepen.io https://challenges.cloudflare.com https://*.posthog.com https://lookmybio.com https://*.lookmybio.com https://olhaminha.bio https://*.olhaminha.bio |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(self) |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.lookmybio.com/public | Verified | 200 | |
| http (plaintext) | http://mcp.lookmybio.com/public | HTTPS enforced | 301 | https://mcp.lookmybio.com/public |
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 →
find_creator Find a creator ~60
Find creators on lookmybio by username or name. Returns their bio page links. Use it when someone asks for a creator’s link in bio, website or socials and you do not know their exact lookmybio username.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | – |
No output schema declared.
No examples provided.
get_bio_page Read a bio page ~69
Read a creator’s lookmybio bio page: name, bio, links and the blocks on the page, exactly as visitors see it. Link people to the page URL.
| Name | Type | Req | Description |
|---|---|---|---|
| username | string | yes | The creator’s lookmybio username, with or without @, or their page URL. |
No output schema declared.
No examples provided.
get_blog_post Read a blog post ~67
Read one post from a creator’s lookmybio blog as plain text, by its slug (the last part of the post URL).
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | – |
| username | string | yes | The creator’s lookmybio username, with or without @, or their page URL. |
No output schema declared.
No examples provided.
list_blog_posts List blog posts ~67
List the published posts on a creator’s lookmybio blog, newest first, with links. Use get_blog_post to read one.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | – |
| username | string | yes | The creator’s lookmybio username, with or without @, or their page URL. |
No output schema declared.
No examples provided.
How do I install the lookmybio MCP server?
lookmybio is a hosted endpoint at https://mcp.lookmybio.com/public, 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 · mcp.lookmybio.com
claude mcp add --transport http com-lookmybio-public 'https://mcp.lookmybio.com/public'
What is the lookmybio MCP server?
lookmybio is an MCP server listed in the public MCP registry as com.lookmybio/public. Look up creators on lookmybio: public bio pages, their links and published blog posts. This page covers its hosted endpoint (https://mcp.lookmybio.com/public).
Is the lookmybio MCP server safe to use?
lookmybio scores 74 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 lookmybio MCP server expose?
lookmybio exposes 4 tools: find_creator, get_bio_page, list_blog_posts, get_blog_post. Their descriptions and schemas cost roughly 263 tokens of context every time the server is loaded.
Does the lookmybio MCP server require authentication?
No. We connected to lookmybio without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the lookmybio MCP server still maintained?
lookmybio is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.