# SelfBadge (remote · selfbadge.com)

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

- Trust score: 83/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `selfbadge.com`: 83/100 (this document), [markdown](https://verifymcp.io/servers/com-selfbadge-selfbadge/selfbadge.md), [page](https://verifymcp.io/servers/com-selfbadge-selfbadge/selfbadge)

## Channel facts

- Endpoint: `https://selfbadge.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 68/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 605 tokens (~201/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 80/100
  - Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the SelfBadge MCP server?

SelfBadge is a hosted endpoint at https://selfbadge.com/mcp, 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.

### Claude

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

### Cursor

```json
{
  "mcpServers": {
    "com-selfbadge-selfbadge": {
      "url": "https://selfbadge.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-selfbadge-selfbadge": {
      "type": "http",
      "url": "https://selfbadge.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-selfbadge-selfbadge]
url = "https://selfbadge.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-selfbadge-selfbadge": {
      "type": "remote",
      "url": "https://selfbadge.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-selfbadge-selfbadge --url 'https://selfbadge.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-selfbadge-selfbadge:
    url: "https://selfbadge.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-selfbadge-selfbadge": {
      "Transport": "http",
      "Url": "https://selfbadge.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-selfbadge-selfbadge -t streamable-http -u 'https://selfbadge.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-selfbadge-selfbadge": {
      "type": "http",
      "url": "https://selfbadge.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 83, +1)

No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-01 (score 82, +1)

No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-30 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-28 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-26 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-24 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-22 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-20 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (3)

### `find_person` (~236 tokens)

Find a person by name

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.

Input parameters:

- `job_title` (string): Optional. What you know of their job title, for example "Managing Partner".
- `limit` (integer): Optional. How many candidates to return (default 10).
- `location` (string): Optional. A city or country you associate with them.
- `name` (string, required): The person's full name, for example "Noa Bergman".
- `organization` (string): Optional. An organization you associate with them, for example "Harbor Ventures".

### `get_person` (~144 tokens)

Get a person's verified profile

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.

Input parameters:

- `handle` (string): The profile handle, for example "jane-doe" (from selfbadge.com/jane-doe).
- `id` (string): Or the SelfBadge id, for example "https://selfbadge.com/jane-doe#person".

### `get_organization` (~85 tokens)

Get an organization

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.

Input parameters:

- `slug` (string, required): The organization's slug, from its address selfbadge.com/org/<slug> or its @id.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-selfbadge-selfbadge/selfbadge#diagnostics

## Score history

- 2026-11-05: 83
- 2026-11-04: 83
- 2026-11-03: 82
- 2026-11-02: 82
- 2026-11-01: 82
- 2026-10-31: 81
- 2026-10-30: 81
- 2026-10-29: 80
- 2026-10-28: 80
- 2026-10-27: 79
- 2026-10-26: 79
- 2026-10-25: 78
- 2026-10-24: 78
- 2026-10-23: 77
- 2026-10-22: 77
- 2026-10-21: 76
- 2026-10-20: 76
- 2026-10-19: 75
- 2026-10-18: 75
- 2026-10-17: 75
- 2026-10-16: 74
- 2026-10-15: 74
- 2026-10-14: 73
- 2026-10-13: 73
- 2026-10-12: 72

## Common questions

### What is the SelfBadge MCP server?

SelfBadge is an MCP server listed in the public MCP registry as com.selfbadge/selfbadge. Look up verified people on SelfBadge and tell them apart from namesakes. This page covers its hosted endpoint (https://selfbadge.com/mcp).

### Is the SelfBadge MCP server safe to use?

SelfBadge scores 83 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 SelfBadge MCP server expose?

SelfBadge exposes 3 tools: find_person, get_person, get_organization. Their descriptions and schemas cost roughly 465 tokens of context every time the server is loaded.

### Does the SelfBadge MCP server require authentication?

No. We connected to SelfBadge without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the SelfBadge MCP server still maintained?

SelfBadge 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.

## Links

- Remote endpoint: https://selfbadge.com/mcp
- Website: https://selfbadge.com/developers
- Changelog RSS feed: https://verifymcp.io/servers/com-selfbadge-selfbadge/selfbadge.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-selfbadge-selfbadge/selfbadge.json
- HTML version of this page: https://verifymcp.io/servers/com-selfbadge-selfbadge/selfbadge