Glyt
Server Details
Human-in-the-loop approval for agent actions, with verifiable action-bound receipts.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
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.
Tool Definition Quality
Average 3.4/5 across 6 of 6 tools scored. Lowest: 2.6/5.
Each tool targets a distinct aspect of the approval workflow: discovery for metadata, request/check for approval lifecycle, file_contest for disputes, get/verify receipt for receipt handling. No two tools overlap in purpose.
Five of six tools follow the verb_noun pattern (check_approval, file_contest, get_receipt, request_approval, verify_receipt). Only 'discovery' is a noun, but it is a one-word service discovery tool, which is an acceptable minor deviation.
Six tools is well-scoped for the domain. Each tool serves a clear, non-redundant role in the approval and receipt verification process, neither too few nor too many.
The tool set covers the full lifecycle: discovery (metadata), requesting and polling approvals, contesting decisions, fetching and verifying receipts. No obvious gaps are present for the intended domain.
Available Tools
6 toolscheck_approvalInspect
Poll one of your approval requests. Requires the same id_token. Returns the request view, including the signed receipt once decided.
| Name | Required | Description | Default |
|---|---|---|---|
| id_token | Yes | ||
| request_id | Yes |
discoveryInspect
Glyt service discovery: issuer did:key, receipt schema version, and how to verify receipts offline.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
file_contestInspect
As the SUBJECT of an approval, file a Bitcoin-anchored, self-signed objection into that receipt's declared contest channel (the §12.3 upper bound). You sign the contest with your OWN ed25519 key and supply your OWN Touchstone-audience id_token — Glyt writes it AS you, holding no secret. Sign JCS{v:1,recorder_id:<standing.anchor.contest.recorder>,event_type:"touchstone.contest",actor_sub:,counterparty_sub:null,payload_hash:,client_ts:null}; target_digest is standing.anchor.attestation entry's payload_hash (from the inclusion endpoint). contestant_pubkey/contestant_sig are standard base64.
| Name | Required | Description | Default |
|---|---|---|---|
| reason | Yes | ||
| id_token | Yes | Your Glyt-audience Colony id_token (authenticates you as the subject). | |
| receipt_id | Yes | ||
| contestant_sig | Yes | Your signature over the contest signed_content, standard base64. | |
| contestant_pubkey | Yes | Your ed25519 public key, standard base64. | |
| touchstone_id_token | Yes | Your Touchstone-audience Colony id_token (authenticates the contest write as you). |
get_receiptInspect
Fetch a signed receipt envelope by id.
| Name | Required | Description | Default |
|---|---|---|---|
| receipt_id | Yes |
request_approvalInspect
Ask the operator behind this agent to approve a specific action. Requires a Colony token-exchange id_token (colony:operator) as id_token. Returns the request view; poll with check_approval. Nothing is approved without the human's decision.
| Name | Required | Description | Default |
|---|---|---|---|
| action | Yes | ||
| summary | No | ||
| id_token | Yes | A Colony token-exchange id_token audienced to Glyt. | |
| stake_tier | No | ||
| callback_url | No |
verify_receiptInspect
Verify a Glyt receipt against the exact action you are about to run. Returns {valid, decision, acr, not_after, reasons}. The authoritative check is offline against the issuer did:key; this is a convenience.
| Name | Required | Description | Default |
|---|---|---|---|
| action | Yes | ||
| receipt | Yes | The receipt envelope object or its JSON string. | |
| required_acr | No | ||
| expected_agent_sub | No |
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!