Signometric MCP server

Connect Signometric to the agentic AI world.

An MCP endpoint that teaches an AI agent how Signometric works: what each product proves, what every backend action does, and what its error messages actually mean.

114documented actions

What it does not do

It reads documentation, not your account. This server holds no credential, opens no database and reaches no customer data. It cannot send a Seal, read a document or see a client.

That is deliberate rather than cautious. Signometric has no API key: the only credential is a session token, and most actions additionally require a face confirmation that expires. An agent has no face, so it cannot hold durable access. Granting one would mean building a way around the product's central control, which is the opposite of the point.

Connecting

Add it to any MCP client that speaks JSON-RPC over HTTP:

{
  "mcpServers": {
    "signometric": {
      "url": "https://mcp.signometric.com/"
    }
  }
}

No key, no sign-up, no rate limit worth mentioning. Protocol 2024-11-05, one endpoint, POST only.

The tools

list_actions(area?, auth?, search?)

List Signometric backend actions with how each one authenticates, whether it needs a confirmed face, whether it is rate limited and whether it consumes the monthly document allowance. Filter by area, auth type, or a substring of the name.

describe_action(action)

Everything known about one action: its parameters and their types, how it authenticates, whether the face gate applies, its rate limits, the error messages it can return, and the explanatory comment from the source.

explain_error(message)

Explain a Signometric error message or HTTP status: what it actually means, what usually causes it, and how it is resolved. Use this FIRST when a user reports a message they do not understand -- most of these messages are not self-explanatory and the obvious reading is often the wrong one.

explain_concept(topic?)

Explain how part of Signometric works: the four products and what each proves, the encryption model, the face gate, retention and what survives a purge, how invitation links carry their key. Call with no argument to list the available topics.

choose_product(goal)

Given what someone is trying to achieve, say which of the four products fits and what the record will and will not prove. Use this before advising anyone to send something: the four look similar and the differences are legally load-bearing.

plans(no arguments)

The subscription tiers: price, monthly document allowance, seats, and how long stored copies are kept. Note that One Time View and Wet Sign do not consume the allowance.

Where the answers come from

Half of what this server knows is generated from the Signometric source on every deploy: the action list, each one's parameters, the errors it can raise, whether the face gate applies, and the plan figures. Documentation about an API rots at the speed the API changes, and the failure is silent, so nothing that can be derived is written by hand.

The other half — what a Seal proves that a Wet Sign does not, why a link-only delivery is a different thing, what survives a purge — is written and reviewed by a person, because it says what things mean.