Glyt

net.glytPublished by glyt.netOfficial publisherv0.1.0Updated Oct 27, 2026

Human-in-the-loop approval for agent actions, with verifiable action-bound receipts.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowSecurity & Monitoring

Overview

AI-generated overview

Remote Glyt endpoint that lets an assistant request human approval for specific actions and verify signed, action-bound receipts.

What you can do
  • Discover the service: read the issuer did:key, receipt schema version and offline verification guidance.
  • Request and poll approvals: ask the operator behind the agent to approve a specific action, then check the request view until a decision is made.
  • Fetch and verify receipts: retrieve a signed receipt envelope by id and check it against the exact action about to run, returning validity, decision, acr, expiry and reasons.
  • File a contest: as the subject of an approval, sign and submit an objection into the receipt's declared contest channel.
When to use it
Use it when an agent should get explicit human sign-off before running a sensitive action and needs a verifiable record that the approval was bound to that exact action. Also relevant when an agent must dispute or contest a decision it was subject to.
Requirements
A remote streamable HTTP endpoint; no package or local runtime. Approval calls require a Colony token-exchange id_token with the colony:operator audience, and contest filing requires the agent's own ed25519 key and its own Touchstone-audience id_token. Network access to the endpoint.
Before you install
The server handles identity tokens (id_token) and signing keys; the contest flow requires the agent's own ed25519 private key, which it uses to sign as itself. Approvals and contests are consequential actions recorded as receipts, so confirm the exact action before requesting or verifying. Offline verification against the issuer did:key is described as the authoritative check, so treat the server's verify result as a convenience.

Installation

In SourceWeft

  1. Open Glyt in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/net.glyt%2Fglyt/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "glyt": {
      "type": "http",
      "url": "https://glyt.net/mcp"
    }
  }
}

Tools

6

discovery

Glyt service discovery: issuer did:key, receipt schema version, and how to verify receipts offline.

Takes no parameters.

verify_receipt

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.

Parametersactionrequiredreceiptrequiredrequired_acrexpected_agent_sub

get_receipt

Fetch a signed receipt envelope by id.

Parametersreceipt_idrequired

request_approval

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.

Parametersactionrequiredsummaryid_tokenrequiredstake_tiercallback_url

check_approval

Poll one of your approval requests. Requires the same `id_token`. Returns the request view, including the signed receipt once decided.

Parametersid_tokenrequiredrequest_idrequired

file_contest

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:<your sub>,counterparty_sub:null,payload_hash:<target_digest>,client_ts:null}; target_digest is standing.anchor.attestation entry's payload_hash (from the inclusion endpoint). contestant_pubkey/contestant_sig are standard base64.

Parametersreasonrequiredid_tokenrequiredreceipt_idrequiredcontestant_sigrequiredcontestant_pubkeyrequiredtouchstone_id_tokenrequired

Version history

1
  1. v0.1.0LatestSep 16, 2026

Score

72% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.