A
license-
qualityC
maintenanceRead-only MCP server that provides tools to fetch SealChat public protocol docs, manifest, channel counts, and chat messages via the HTTP Agent API, without write access or database access.
MIT
HODLXXI Read-Only
Server Details
Public read-only MCP server for HODLXXI agent identity, trust, receipts, and verification.
- Status
- Unhealthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- hodlxxi/Universal-Bitcoin-Identity-Layer
- GitHub Stars
- 0
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
MCP client
Glama
MCP server
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
100% free. Your data is private.
Tool Definition Quality
A3.6/5.0
Tool DescriptionsB
Average 3.7/5 across 26 of 26 tools scored. Lowest: 2.4/5.
Server CoherenceA
Disambiguation5/5
Every tool has a clearly distinct purpose—each retrieves a specific document or piece of metadata (e.g., identity, capabilities, trust events). No two tools overlap in functionality, and descriptions are precise, leaving no ambiguity about which tool to select.
Naming Consistency4/5
All tools follow the 'hodlxxi_get_<resource>' pattern except 'hodlxxi_verify_receipt', which uses 'verify' instead of 'get'. This minor deviation is the only inconsistency, but the overall naming is predictable and clear.
Tool Count4/5
26 tools is on the higher side, but each tool corresponds to a unique document or endpoint necessary for the comprehensive read-only trust and identity server. The scope justifies the count, though it could be slightly trimmed without loss.
Completeness5/5
The tool surface exhaustively covers all major aspects of the HODLXXI protocol: identity, capabilities, trust, covenants, receipts, OAuth, Nostr, and more. There are no obvious gaps for read-only operations; every needed resource is accessible.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Servers
- Alicense-qualityBmaintenanceA local, read-only MCP server that exposes verified profile, posts, corpus, and other identity data from robertdelanghe.dev's signed static API.34MIT
- Alicense-qualityAmaintenancePublic read-only MCP server for turva.dev's agent-readiness audit, enabling AI agents to query service catalog, security evidence, and engagement principles via structured JSON.1MIT
- Flicense-qualityCmaintenanceRead-only MCP server for querying an evidence-aware knowledge vault with temporal and provenance-aware data, supporting agent memory and semantic graph projections.