Skip to content

SelfBadge MCP server

com.selfbadge/selfbadgeselfbadge.comstreamable-httpv1.0.0Scanned

Look up verified people on SelfBadge and tell them apart from namesakes.

3 tools: 3 only read.

Tools: 0 delete, 0 irreversible, 0 write, 3 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

Anlyon alternative

Run the operations that matter as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

Its sign-in does not let Anlyon set up an OAuth client on its own, so there is no link to it here.

What the SelfBadge MCP server can do

The SelfBadge MCP server is published by selfbadge.com, a domain the MCP Registry verified. It has 3 tools. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.

None of its tools reads private data, brings in text other people write, or sends data out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 14, 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.

3 tools

Only reads 3Show 3 read-only tools
  • find_personSearch SelfBadge for people with a given name.No findings

    Why it is in this group

    • The name "find_person" says "find": a word for reading.
    Description, as the server wrote it
    Search SelfBadge for people with a given name. Use this to identify a person correctly and tell them apart from namesakes: each candidate comes with their job title, organization, location and a short description. Pass what you already know (job title, organization, location) so the best match comes first, then call get_person with the chosen id for the full, verified profile. It returns public SelfBadge profiles, each marked claimed or created from public sources (seeded: level 0, unconfirmed until the person claims it). An empty result means SelfBadge has no public profile with that name, not that the person does not exist.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • get_organizationGet an organization's SelfBadge page: its public facts, schema.org JSON-LD, and the people on SelfBadge linked to it (team members who accepted their organization's invitation, and…No findings

    Why it is in this group

    • The name "get_organization" says "get": a word for reading.
    Description, as the server wrote it
    Get an organization's SelfBadge page: its public facts, schema.org JSON-LD, and the people on SelfBadge linked to it (team members who accepted their organization's invitation, and founders). Use it to check whether someone works at or founded an organization.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • get_personGet one person's SelfBadge profile: every public fact (name, roles, organizations, education, accounts, published work and more) with its verification level and source, plus schema…No findings

    Why it is in this group

    • The name "get_person" says "get": a word for reading.
    Description, as the server wrote it
    Get one person's SelfBadge profile: every public fact (name, roles, organizations, education, accounts, published work and more) with its verification level and source, plus schema.org JSON-LD. Use it after find_person, or when you already have a SelfBadge handle, profile address or id. Profiles created from public sources and not yet claimed are marked seeded; treat their facts as unconfirmed.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false

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 untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
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.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:46 UTC, unchanged since Oct 29, 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
0
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://selfbadge.com/.well-known/oauth-protected-resource
Authorization servers
https://selfbadge.com
Legacy HTTP+SSE transport
no
Dynamic client registration
no
Client ID metadata documents
no

Posture changes

  1. Oct 29, 2026
    • RFC 9728 protected resource metadata: none to https://selfbadge.com/.well-known/oauth-protected-resource
    • Authorization servers: none to https://selfbadge.com
    • Dynamic client registration: not observed to no
    • Client ID metadata documents: not observed to no

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. RFC 9728 protected resource metadata: none -> https://selfbadge.com/.well-known/oauth-protected-resource; Authorization servers: none -> https://selfbadge.com; Dynamic client registration: not observed -> no (and 1 m…View diff
    • RFC 9728 protected resource metadata: none to https://selfbadge.com/.well-known/oauth-protected-resource
    • Authorization servers: none to https://selfbadge.com
    • Dynamic client registration: not observed to no
    • Client ID metadata documents: not observed to no

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http selfbadge https://selfbadge.com/mcp
claude mcp add --transport http selfbadge https://selfbadge.com/mcp

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.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__selfbadge__find_person",
      "mcp__selfbadge__get_person",
      "mcp__selfbadge__get_organization"
    ],
    "ask": [],
    "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 selfbadge. Review it before you use it.

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/com.selfbadge/selfbadge/verify?hash=caa660d16c42bca66852dc28b23ff055bae91a3ef5846604af7b5cb8cb147d26" | jq -e '.changed == false'

Pinned hash caa660d16c42, from Nov 14, 2026, 07:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.selfbadge/selfbadge/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.selfbadge/selfbadge
[![Anlyon Radar](https://radar.anlyon.com/badge/com.selfbadge/selfbadge.svg)](https://radar.anlyon.com/servers/com.selfbadge/selfbadge)

Source: MCP Registry. Synced Oct 21, 2026, 18:04 UTC.

SelfBadge MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the SelfBadge MCP server safe?

No scan can promise that. What its definitions show: 3 tools, all of which only read, and 0 findings from fixed checks. Read-only tools can still pass private data to a model.

Can the SelfBadge MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the SelfBadge 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 SelfBadge MCP server have?

3 tools: 3 read. find_person, get_person and get_organization.

Does the SelfBadge MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the SelfBadge MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the SelfBadge MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 14, 2026.