mcp-server-jis
Related Servers
Alternatives to mcp-server-jis
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceMCP server for AI agent identity — verify agents with Ed25519 signatures, check trust scores, sign and verify content, exchange encrypted messages. Built on the Agent Identity Protocol (AIP).8MIT
- AlicenseNot gradedqualityDmaintenanceMCP Server for AI agent identity and authorization. Create, verify, and manage agent identities with trust scores and scoped authorization tokens.MIT
- FlicenseNot gradedqualityBmaintenanceMCP server for the TETA+PI verified entity registry, enabling AI agents to search, verify, and route intents to trusted entities.1-
- AlicenseAqualityDmaintenanceMCP server for AI agent trust verification, enabling agents to verify identities, check trust scores, and build reputation across multiple blockchain and web platforms.125 npm1MIT
- FlicenseAqualityBmaintenanceMock identity-management MCP server for decentralized identity that allows minting DIDs, issuing signed Verifiable Credentials, and verifying them.8-
- AlicenseNot gradedqualityDmaintenanceMCP server for Citizen of the Cloud — agent identity verification, trust scoring, and registry access for any AI runtime that speaks the Model Context Protocol.7 npmMIT
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.