Security & Testing

username.md

Provides identity and credential verification for username.md handles, exposing DID documents, verifiable claims, agent instructions, and platform signing keys.

1 endpoint6 known toolsFirst detected September 24, 2026Last detected September 24, 2026

ENDPOINT 1

https://mcp.username.md/mcp

No auth detected

MCP server metadata

Name: username-md-mcp
Version: 1.0.0

Capabilities

tools

Server instructions

Stateless read-only MCP for username.md identity lookups. No session is created; every call is independent. On HTTP 429 honor the Retry-After header and back off exponentially. Use verify_handle when you need cryptographic assurance of profile data.

Known tools 6

resolve_handle

Fetch the structured public profile for a username.md handle (name, DID, public key, links, tagline).

Inferred read-only

get_did_document

Fetch the W3C DID document (did:web) for a handle.

Inferred read-only

list_claims

List the signed Verifiable Credentials (claims) issued under a handle's key — domain ownership, account control, imported Keybase proofs.

Inferred read-only

get_agent_instructions

Fetch the per-user llms.txt — the handle owner's standing instructions for AI agents interacting with them.

Inferred read-only

get_platform_keys

Fetch the username.md platform JWKS used to sign every API response (RFC 9421, Ed25519, kid 'platform-ed25519').

Inferred read-only

verify_handle

Fetch a handle's profile and verify the platform's RFC 9421 response signature (Ed25519) and Content-Digest against the published JWKS.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.username-md-mcp]
url = "https://mcp.username.md/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "username-md-mcp": {
      "type": "http",
      "url": "https://mcp.username.md/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: username-md-mcp
Remote MCP URL: https://mcp.username.md/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "username-md-mcp": {
      "url": "https://mcp.username.md/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "username-md-mcp": {
      "type": "http",
      "url": "https://mcp.username.md/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "username-md-mcp",
  "transport": "streamable-http",
  "url": "https://mcp.username.md/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.