mcp-server-jis
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JIS_SECRET | No | Your signing secret for proofs | |
| JIS_IDENTITY | No | Your jis: identifier | |
| HUMOTICA_JIS_ENDPOINT | No | Custom JIS endpoint (default: humotica.com) | humotica.com |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| jis_whoamiA | Show your current JIS identity (jis:). If not configured, shows how to set one up. |
| jis_verifyA | Verify a jis: identifier. Check if it's valid and get public information about the identity. |
| jis_request_intentB | Request bilateral intent from a jis: identity. This is the core of the Intent-Centric Web - no interaction without mutual consent. |
| jis_send_verifiedA | Send a JIS-verified message. Requires bilateral intent acceptance first. |
| ask_humoticaB | Ask a verified question to Humotica. Uses JIS bilateral intent to ensure authentic response. Great for asking about TIBET, JIS, the Intent-Centric Web, or HumoticaOS. |
| jis_trust_scoreB | Get the trust score for a jis: identity based on TIBET audit history. |
| jis_specA | Get information about the jis: specification - The Intent-Centric Web. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Each tool has a clearly distinct purpose: asking questions, requesting intent, sending verified messages, getting spec info, checking trust scores, verifying identifiers, and showing current identity. No functional overlap exists.
Most tools follow a 'jis_verb' pattern (e.g., jis_request_intent, jis_verify), with one exception: ask_humotica uses 'ask_'. This minor inconsistency is tolerable as both patterns are clear and descriptive.
Seven tools is well-scoped for the JIS/Humotica domain, covering identity management, intent handling, verified messaging, trust analysis, and specification lookup without excess or deficiency.
The tool set covers core operations: identity verification, trust scoring, intent negotiation, verified messaging, and general inquiry. A minor gap is the lack of an explicit 'create identity' tool, but jis_whoami addresses setup implicitly.