@proof-holdings/mcp-server

Official

Overview Schema Source Related Servers Discussions Admin

get_my_profile

Read-only

Retrieve the current user's primary profile, including profile details, theme, custom links, and public proof display settings for account-based Proof integrations.

Instructions

Get the current user's primary profile. Returns profile details, theme, custom links, and public proof display settings.

ACCESS: needs a Proof account. Set PROOF_API_KEY and restart this server, then call this tool again. start_login does NOT open this tool.

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description
`id`	Yes	MongoDB ObjectId
`bio`	No
`theme`	Yes	Profile theme customization
`username`	No	Absent until a username is claimed
`is_public`	Yes
`avatar_url`	No	A URL or a data URI; null once cleared
`created_at`	Yes
`is_primary`	Yes
`profile_id`	Yes	The public id used in profile URLs
`updated_at`	Yes
`view_count`	Yes
`email_theme`	Yes	Theme of this sub-account's emails; null when unset (read as `dark`).
`is_business`	Yes
`proof_order`	Yes	Who decided the order of a profile's proofs. `default`: domain, social account, Telegram bot, email, phone, wallet, then each proof's `display_order`. `owner`: the owner's `display_order` alone — send it when the owner reorders. The first shown proof that is not hidden leads the profile's preview card, share tags and badge. Omitted on an update, the profile keeps its current setting.
`custom_links`	Yes
`display_name`	No
`business_name`	No
`public_proofs`	Yes	The shown proofs, in the order the public profile shows them
`support_email`	Yes	Support address shown in this sub-account's messages; null when unset.
`show_delegations`	Yes
`verification_level`	Yes	Always 'basic'; no levels are computed; removed in the next major.
`show_proof_channels`	Yes
`show_verification_dates`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv1.7.2Nov 6, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": {},
+  "description": "A sub-account as its owner sees it",
+  "properties": {
+    "avatar_url": {
+      "description": "A URL or a data URI; null once cleared",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "bio": {
+      "type": "string"
+    },
+    "business_name": {
+      "type": "string"
+    },
+    "created_at": {
+      "type": "string"
+    },
+    "custom_links": {
+      "items": {
+        "additionalProperties": {},
+        "properties": {
+          "_id": {
+            "type": "string"
+          },
+          "display_order": {
+            "maximum": 9007199254740991,
+            "minimum": -9007199254740991,
+            "type": "integer"
+          },
+          "icon": {
+            "type": "string"
+          },
+          "is_visible": {
+            "type": "boolean"
+          },
+          "title": {
+            "type": "string"
+          },
+          "url": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "_id",
+          "title",
+          "url",
+          "is_visible",
+          "display_order"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "display_name": {
+      "type": "string"
+    },
+    "email_theme": {
+      "description": "Theme of this sub-account's emails; null when unset (read as `dark`).",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "id": {
+      "description": "MongoDB ObjectId",
+      "type": "string"
+    },
+    "is_business": {
+      "type": "boolean"
+    },
+    "is_primary": {
+      "type": "boolean"
+    },
+    "is_public": {
+      "type": "boolean"
+    },
+    "profile_id": {
+      "description": "The public id used in profile URLs",
+      "type": "string"
+    },
+    "proof_order": {
+      "description": "Who decided the order of a profile's proofs. `default`: domain, social account, Telegram bot, email, phone, wallet, then each proof's `display_order`. `owner`: the owner's `display_order` alone — send it when the owner reorders. The first shown proof that is not hidden leads the profile's preview card, share tags and badge. Omitted on an update, the profile keeps its current setting.",
+      "type": "string"
+    },
+    "public_proofs": {
+      "description": "The shown proofs, in the order the public profile shows them",
+      "items": {
+        "additionalProperties": {},
+        "properties": {
+          "asset_id": {
+            "type": "string"
+          },
+          "channel": {
+            "type": "string"
+          },
+          "delegate_type": {
+            "type": "string"
+          },
+          "delegation_id": {
+            "type": "string"
+          },
+          "display_order": {
+            "maximum": 9007199254740991,
+            "minimum": -9007199254740991,
+            "type": "integer"
+          },
+          "display_value": {
+            "type": "string"
+          },
+          "is_revoked": {
+            "type": "boolean"
+          },
+          "is_visible": {
+            "type": "boolean"
+          },
+          "label": {
+            "type": "string"
+          },
+          "mask_level": {
+            "type": "string"
+          },
+          "type": {
+            "type": "string"
+          },
+          "verified_at": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "asset_id",
+          "type",
+          "display_value",
+          "verified_at",
+          "is_visible",
+          "display_order",
+          "mask_level"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "show_delegations": {
+      "type": "boolean"
+    },
+    "show_proof_channels": {
+      "type": "boolean"
+    },
+    "show_verification_dates": {
+      "type": "boolean"
+    },
+    "support_email": {
+      "description": "Support address shown in this sub-account's messages; null when unset.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "theme": {
+      "additionalProperties": {},
+      "description": "Profile theme customization",
+      "properties": {
+        "background_color": {
+          "type": "string"
+        },
+        "background_type": {
+          "type": "string"
+        },
+        "font_style": {
+          "type": "string"
+        },
+        "gradient_end": {
+          "type": "string"
+        },
+        "gradient_start": {
+          "type": "string"
+        },
+        "primary_color": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "updated_at": {
+      "type": "string"
+    },
+    "username": {
+      "description": "Absent until a username is claimed",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "verification_level": {
+      "description": "Always 'basic'; no levels are computed; removed in the next major.",
+      "type": "string"
+    },
+    "view_count": {
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    }
+  },
+  "required": [
+    "id",
+    "profile_id",
+    "is_primary",
+    "verification_level",
+    "is_business",
+    "public_proofs",
+    "proof_order",
+    "custom_links",
+    "theme",
+    "is_public",
+    "show_verification_dates",
+    "show_proof_channels",
+    "show_delegations",
+    "support_email",
+    "email_theme",
+    "view_count",
+    "created_at",
+    "updated_at"
+  ],
+  "type": "object"
+}

First observedv1.1.0Sep 9, 2026

TDQS

A4/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

readOnlyHint=true already covers the safety profile, and the description adds real context beyond that: authentication setup requirements, a restart step, and the fact that the login flow does not unlock this tool. It stops short of noting rate limits or failure modes when the key is absent, which would have pushed it higher.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads the capability in one sentence, then separates the access prerequisite into its own labeled block, which is easy to scan. The access paragraph is slightly verbose (restart-and-retry instructions) but each sentence carries actionable information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists and there are no parameters, so the description does not need to document return shapes; it still summarizes the returned fields helpfully. The one real gap is sibling disambiguation in a toolset dense with profile/user-adjacent endpoints, which is the missing piece for full completeness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline for a no-arg tool applies. The description correctly implies a no-argument call scoped implicitly to the authenticated user.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Get the current user's primary profile") and enumerates what comes back (profile details, theme, custom links, public proof display settings). It does not, however, distinguish itself from closely named siblings such as get_profile or get_current_user, so an agent must infer the "my" vs "arbitrary profile" distinction.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a clear precondition (a Proof account plus PROOF_API_KEY set with a server restart) and explicitly rules out a tempting alternative path by stating start_login does NOT open this tool. What it omits is guidance on when to prefer it over get_profile, get_current_user, or update_my_profile.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server