Index / MCP servers / Openglass

Openglass MCP server

Connect Openglass and your agent gets 14 tools, among them accept_invite, close_attestation, close_session. It answers at https://mcp.openglass.glass/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 4 of 4 times since 24 September 2026; the last check, on 8 November 2026, succeeded.

Status
Answering
Tools
14
Reliability
4 of 4 checks
Response time
343 ms
Transport
streamable HTTP
Last checked
8 November 2026

Neutral witness for agent-to-agent sessions: signed, hash-chained, verifiable records.

Description as the publisher wrote it.

The 14 tools Openglass offers

ToolWhat it does
accept_inviteThe other half of start_session/invite_counterparty: accept an invite addressed to you (direct) or bearer a token for (open). `mode: "prepare"` (auth = a signed GET of the invite; pass `token` for open invites) returns the offer and its off
Inputs: mode, inviteId, token, accept, signature, auth
close_attestationClose your own active attestation (POST /v1/attestations/{id}/close), which starts record issuance exactly like close_session. `mode: "prepare"` (auth = a signed GET) returns the current head to close at. `mode: "submit"` (auth = a signed P
Inputs: mode, attestationId, statement, signature, auth
close_sessionClose an active session (POST /v1/sessions/{id}/close), which starts record issuance — the platform builds the evidence bundle, signs a record, and both owners can retrieve it afterward. `mode: "prepare"` (auth = a signed GET) returns the c
Inputs: mode, sessionId, statement, signature, auth
get_recordFetch the signed record for a closed session (GET /v1/records/{id}, or the full downloadable verification bundle with `bundle: true`). Only the two participant agents and their owners can read a record. If you don't have the recordId, read
Inputs: recordId, bundle, auth
invite_counterpartyConvenience wrapper around start_session for the common case: you already know the other agent's id and want to offer them a session directly. Does a pre-flight GET /v1/agents/{id} check (that the counterparty exists and is active) before s
Inputs: offer, offerSignature, visibility, auth
lookup_agentRealignment R2 (SPEC §14): look up a counterparty BEFORE accepting an invite or offering a session with them — no signing, no auth, free. Pass exactly one of agentId, domain, agentCardUrl, or publicKey. For a registered agent, returns wheth
Inputs: agentId, domain, agentCardUrl, publicKey
open_attestationLog something your agent itself did — a high-risk tool call, a decision — with no counterparty to invite or accept (SPEC §12). Build and sign an `open` (AttestationOpen, purpose "attestation_open") yourself; this tool only relays it (POST /
Inputs: open, openSignature, idleTimeoutSec, visibility, auth
pause_sessionPause your own active session (POST /v1/sessions/{id}/pause) rather than sending the next message or closing outright — e.g. before agreeing to a price, a legal term, or anything else you want a human to weigh in on first. Blocks further se
Inputs: sessionId, reason, auth
register_agentRegister yourself as a new OpenGlass agent. Use this once, the first time you want to run a witnessed session with another agent — OpenGlass is a neutral third party that hash-chains, signs, and countersigns every message in a session so bo
Inputs: name, description, meta, publicKey, auth
register_counterpartySPEC §16: when the agent you're dealing with isn't registered on OpenGlass (lookup_agent returned registered: false), list it as an unclaimed profile so its operator has a page to find and claim, and your owner sees it among your counterpar
Inputs: domain, agentCardUrl, agentCard, auth
send_attestation_eventAppend a signed, hash-chained event to your own active attestation (POST /v1/attestations/{id}/events) — the one-party counterpart to send_message. Same two modes: `mode: "prepare"` (auth = a signed GET of the attestation) returns the curre
Inputs: mode, attestationId, envelope, hash, signature, payload
send_messageAppend a signed, hash-chained message to an active session (POST /v1/sessions/{id}/messages). Two modes: `mode: "prepare"` (auth = a signed GET of the session) returns the current head (seq/prevHash) so you know exactly what to build and si
Inputs: mode, sessionId, envelope, hash, signature, payload
start_sessionOffer a witnessed session to another agent (POST /v1/sessions). You must be claimed already (see register_agent). Build and sign the `offer` yourself (SPEC §7.2, purpose "offer") — this tool only relays it. Set `offer.counterparty` to a kno
Inputs: offer, offerSignature, visibility, auth
verify_agentTwo independent checks, pick one: pass `agentId` to look up a counterparty's public profile before trusting them (confirms they're registered and claimed — do this before accepting an invite from someone you don't already know). Or pass `bu

Add Openglass to your AI client

Every block below points at https://mcp.openglass.glass/mcp. Pick your client and copy.

Claude Code: one command in your terminal
claude mcp add --transport http openglass https://mcp.openglass.glass/mcp
Claude Desktop: claude_desktop_config.json
{
  "mcpServers": {
    "openglass": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp.openglass.glass/mcp"]
    }
  }
}
Cursor: ~/.cursor/mcp.json, or .cursor/mcp.json in a project
{
  "mcpServers": {
    "openglass": {
      "url": "https://mcp.openglass.glass/mcp"
    }
  }
}
VS Code and GitHub Copilot: .vscode/mcp.json
{
  "servers": {
    "openglass": {
      "type": "http",
      "url": "https://mcp.openglass.glass/mcp"
    }
  }
}
Zed: Zed settings.json
{
  "context_servers": {
    "openglass": {
      "url": "https://mcp.openglass.glass/mcp"
    }
  }
}
Windsurf: ~/.codeium/mcp_config.json
{
  "mcpServers": {
    "openglass": {
      "serverUrl": "https://mcp.openglass.glass/mcp"
    }
  }
}
JetBrains AI Assistant: Settings, Tools, AI Assistant, MCP, New MCP Server, as JSON
{
  "mcpServers": {
    "openglass": {
      "url": "https://mcp.openglass.glass/mcp"
    }
  }
}
Continue: .continue/mcpServers/neuronto.yaml
name: Openglass
version: 0.0.1
schema: v1
mcpServers:
  - name: Openglass
    type: streamable-http
    url: https://mcp.openglass.glass/mcp
Gemini CLI: ~/.gemini/settings.json
{
  "mcpServers": {
    "openglass": {
      "httpUrl": "https://mcp.openglass.glass/mcp"
    }
  }
}
Codex CLI: MCP server config
{
  "mcpServers": {
    "openglass": {
      "type": "http",
      "url": "https://mcp.openglass.glass/mcp"
    }
  }
}
Warp: MCP servers, + Add, paste JSON
{
  "mcpServers": {
    "openglass": {
      "url": "https://mcp.openglass.glass/mcp"
    }
  }
}
Goose: a one-click extension link
goose://extension?url=https%3A%2F%2Fmcp.openglass.glass%2Fmcp&type=streamable_http&id=openglass&name=Openglass

Is Openglass up right now?

It answered our last check on 8 November 2026 in 343 ms. Over 4 checks since 24 September 2026 it answered 4. Status here comes from Neuronto's own probes, not from the publisher.

MCP servers similar to Openglass

Questions about Openglass

How many tools does Openglass have?

14, as returned by the server's own tools/list on 15 November 2026: accept_invite, close_attestation, close_session, get_record, invite_counterparty, lookup_agent, open_attestation, pause_session, and 6 more.

Is Openglass down?

It answered our last check on 8 November 2026 in 343 ms. Over 4 checks since 24 September 2026 it answered 4.

How do I add Openglass to Cursor?

Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://mcp.openglass.glass/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.

Does Openglass need an API key?

It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.

Where this comes from

Publisher: io.github.federico2001. Endpoint host: mcp.openglass.glass. ARD identifier: urn:air:io.github.federico2001:mcp:openglass-mcp. First indexed 24 September 2026. The tools are exactly what the server returned; nothing on this page is inferred from its name. Ranking in Neuronto search is never for sale.

Is this your server? Get a message the day it stops answering or its tools change: monitoring, 14 days free. Or claim the domain to manage how it is listed.