https://<NEURON_HOST>/MCP/Identity. Use the host supplied by your provider.
What you need
You need a connected Neuron account. Identity applications require the personal information and attachments requested by the provider. Your client must support requests for user input (elicitation) for tools that collect these details interactively.Scopes and privileges
The server advertises these OAuth scopes:OAUTH.Scope.MCP.Identity. to each suffix. When a row lists multiple privileges, all are required. For example, OAUTH.Scope.MCP.Identity.Tools.Attachment.Add is a complete privilege name.
Tools
Select a tool name for its complete arguments, defaults, and return values in the original reference. Discover tools in your client to check what your session can use.Use this server
For an identity application, get the application properties, apply for a personal identity, add the required attachments, and mark it ready for approval.ReadyForApproval submits readiness; approval is a separate provider decision.
For a contract, supply an existing TemplateId and its Parameters to CreateOpenContract. Use the resulting contract identifier to propose it to a party or sign a role. ProposeContract sends an existing contract proposal; for XML template authoring, follow Create a contract from scratch. Review the contract and obtain the user’s confirmation before signing.
Resources and prompts
Resources expose identities, requested contracts, and templates you have used. Check their state and validity before using them. The prompts guide identity creation and peer review; tool permissions are still needed to carry out their steps.
See the original Identity and contracts reference for complete schemas and response types, or return to MCP servers.