@proof-holdings/mcp-server

Official

Overview Schema Source Related Servers Discussions Admin

update_profile

Destructive

Update a profile by ID to change display details, theme, email branding, custom links, and verification display settings.

Instructions

Update a profile by ID. Supports changing display info, email branding (theme, support email), theme, custom links, and verification 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
`bio`	No	Profile bio
`theme`	No	Profile theme settings
`is_public`	No	Whether the profile is publicly visible
`avatar_url`	No	Avatar (base64 or URL, null to remove)
`is_primary`	No	Set as primary profile
`profile_id`	Yes	Profile ID
`email_theme`	No	Theme of this sub-account's emails
`is_business`	No	Whether this is a business profile
`custom_links`	No	Custom links (max 20)
`display_name`	No	Display name
`business_name`	No	Business name
`support_email`	No	Support email this sub-account's messages show (null to remove)
`show_delegations`	No	List the published, in-force delegations for the domains the profile shows (default true)
`show_proof_channels`	No	Show proof channels on public profile
`show_verification_dates`	No	Show verification dates on public profile

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.

Changed10 schema fields changedv1.7.2Nov 6, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```

changedInput schema / properties / avatar_url / anyOf

Previous value: -[
-  {
-    "anyOf": [
-      {
-        "not": {}
-      },
-      {
-        "maxLength": 100000,
-        "type": "string"
-      }
-    ]
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "maxLength": 100000,
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

removedInput schema / properties / custom_links / items / additionalProperties
```
Removed value: -false
```
addedInput schema / properties / custom_links / items / properties / display_order / maximum
```
Added value: +9007199254740991
```

changedInput schema / properties / email_theme / description

Previous value: -"Theme of this project's emails"New value: +"Theme of this sub-account's emails"

addedInput schema / properties / show_delegations

Added value: +{
+  "description": "List the published, in-force delegations for the domains the profile shows (default true)",
+  "type": "boolean"
+}

changedInput schema / properties / support_email / anyOf

Previous value: -[
-  {
-    "anyOf": [
-      {
-        "not": {}
-      },
-      {
-        "format": "email",
-        "maxLength": 254,
-        "type": "string"
-      }
-    ],
-    "description": "Support email this project's messages show"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "description": "Support email this sub-account's messages show",
+    "format": "email",
+    "maxLength": 254,
+    "pattern": "^(?:[A-Za-z0-9_'+\\-]+\\.)*[A-Za-z0-9_'+\\-]*[A-Za-z0-9_+-]@(?:[A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$",
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

changedInput schema / properties / support_email / description

Previous value: -"Support email this project's messages show (null to remove)"New value: +"Support email this sub-account's messages show (null to remove)"

removedInput schema / properties / theme / additionalProperties
```
Removed value: -false
```

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"
+}

Changed2 schema fields changedv1.7.0Oct 16, 2026

addedInput schema / properties / email_theme

Added value: +{
+  "description": "Theme of this project's emails",
+  "enum": [
+    "dark",
+    "light"
+  ],
+  "type": "string"
+}

addedInput schema / properties / support_email

Added value: +{
+  "anyOf": [
+    {
+      "anyOf": [
+        {
+          "not": {}
+        },
+        {
+          "format": "email",
+          "maxLength": 254,
+          "type": "string"
+        }
+      ],
+      "description": "Support email this project's messages show"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Support email this project's messages show (null to remove)"
+}

First observedv1.1.0Sep 9, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already flag this as a non-read-only, destructive mutation, and the description usefully adds the account/auth setup requirement that annotations cannot convey. However, for a destructive update it never explains update semantics an agent needs: whether omitted fields are preserved, whether custom_links replaces the entire list, or what removing avatar_url/support_email with null does. That gap matters given destructiveHint=true.

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?

Two tight paragraphs: purpose first, prerequisite second, both front-loaded. The access note is slightly verbose ('restart this server, then call this tool again') but it carries non-obvious information, so little is wasted.

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

Completeness3/5

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

Output schema exists, so return values need no explanation, and the 15-param surface is fully documented in the schema. What's missing is proportionate to the risk: this is a destructive mutation with nested objects and list-replacement semantics, yet the description says nothing about partial-update behavior or overwrite scope.

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

Parameters3/5

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

Schema description coverage is 100%, so every one of the 15 parameters is already documented in the schema, including enum values, hex patterns, and the max-20 custom links constraint. The description only groups fields into functional categories (email branding, theme, links, verification display), adding light orientation but no syntax or semantics beyond the schema.

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 ('Update') and resource ('a profile by ID') and enumerates the categories of changeable fields: display info, email branding, theme, custom links, verification display settings. It doesn't explicitly distinguish itself from close siblings such as update_my_profile or update_profile_proofs, so an agent must infer that 'by ID' means an arbitrary profile rather than the caller's own.

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

Usage Guidelines2/5

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

The only guidance is an access prerequisite (PROOF_API_KEY, restart, start_login won't unlock it), which is about authentication, not tool selection. There is no statement of when to use this versus update_my_profile, set_primary_profile, or update_profile_proofs, and no indication of which field groups require which flags.

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

Deploy Server