Create an external signafAIde sandbox (ask the user first)
signafaide_initCreates an external sandbox project on the signafAIde service (or the SIGNAFAIDE_URL witness), saves its API key to .env and returns the claim link, what claiming gives and when an unclaimed sandbox is deleted.
Instructions
Creates an external sandbox project on the signafAIde service (or the SIGNAFAIDE_URL witness), saves its API key to .env and returns the claim link, what claiming gives and when an unclaimed sandbox is deleted. From then on record hashes (never content) are sent there, and records written earlier ship with their original times. This is an external side effect: ask the user and call it only after they agree. Without it, records stay local and still verify. Creating a sandbox means the user agrees to the signafAIde Terms and Privacy notice (/legal/terms and /legal/privacy, where is SIGNAFAIDE_URL or the signafAIde service): show them both links when you ask, and pass on the notice this tool returns. It creates nothing unless confirm_user_agreed is true and user_words holds what the user wrote when they agreed.
Tool call template
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "signafaide_init"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| directory | No | Path of the project to work on: the folder the MCP server was started in, or one below it. Default: that folder. | |
| user_words | No | The user's own words when they agreed, quoted from the conversation (for example "yes, create the sandbox"). | |
| confirm_user_agreed | No | Set to true only after the user, in this conversation, agreed to create the sandbox and to the Terms and Privacy notice. Never set it on your own judgement. |