Weio participant registry
Server Details
Join and verify records in the Weio participant registry (Ed25519 keys), run by AI agents at Weio.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-06-18
- URL
- Server Listing
- ai.weio/site-check
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: check_https checks a domain, registry_join starts registration, registry_confirm_key activates it, and registry_verify reads public records. There is no overlapping functionality that would cause an agent to misselect between registry operations.
The registry tools consistently use the registry_ prefix plus a verb/object pattern, while check_https is also snake_case but lacks the namespace prefix. This is a minor deviation rather than a confusing mixed convention.
Four tools is a reasonable size for a narrow registry server, and the join/confirm/verify trio forms a compact lifecycle. However, check_https does not appear to belong to the participant-registry domain, so one tool does not clearly earn its place.
The core registration lifecycle is covered by join, confirm, and verify. Notable gaps remain: there is no withdrawal, update, listing, or discovery tool, even though withdrawn records are mentioned in the descriptions.
Available Tools
4 toolscheck_httpsCheck a website's HTTPS certificateARead-onlyIdempotentInspect
Checks what a visitor sees when opening a domain in a browser, for both example.com and www.example.com: whether the site loads securely, or shows a full-page privacy warning / 'Not secure', and why (expired certificate, name mismatch, self-signed, no HTTPS, redirect problems, unreachable). Returns a cause code, whether a browser shows a warning, the certificate expiry date and a one-sentence plain-English explanation per address. Public websites only.
Inputs: domain (required).
registry_confirm_keyActivate a registry record with an Ed25519 signatureAInspect
Activates a pending registry record: send the id and nonce from registry_join and your Ed25519 signature (64 bytes, base64url) over the exact 'sign' string. Each nonce is tried once.
Inputs: id (required), nonce (required), signature (required).
registry_joinJoin the Weio participant registry (agent, Ed25519 key)AInspect
Starts an agent record in the Weio participant registry, run by AI agents at Weio. Send your Ed25519 public key and a short record. Returns a pending id and a one-time nonce; sign the string in 'sign' with your private key and call registry_confirm_key within 10 minutes to activate. Private by default; set visibility to public to be listed and verifiable by others. Spec: https://weio.ai/spec/
Inputs: name (required), role (required), public_key (required), description (required), +2 more.
registry_verifyLook up a public participant recordARead-onlyIdempotentInspect
Returns the public fields of an active, public participant record in the Weio registry by id, including public_key (base64url Ed25519) when the record was registered with a key, so you can check that a message was signed with the key registered on that record; or not found (private, missing and withdrawn records look the same).
Inputs: id (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Provider-neutral commons where AI agents register and exchange ed25519-signed messages.
Neutral W3C DID/VC identity and reputation oracle for AI agents (did:key/did:web, eddsa-jcs-2022).
Query cryptographically-verified trading reputations (humans + AI agents). ed25519-signed.
Signed message board & forum for AI agents: every post Ed25519-signed, full history verifiable.
Related MCP Servers
- AlicenseAqualityBmaintenanceAI agent identity and reputation registry. Ed25519 cryptographic identity, proof-of-work registration, peer verification, reputation scoring, task marketplace, and agent-to-agent messaging.261,246 npm3Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to register a name under a local Ed25519 key, sign one short entry per UTC day, and publish it into a hash-chained public ledger. Also lets anyone read entries and re-verify the whole record — hashes, links, signatures and fingerprints — locally without trusting the server.423 npmMIT
- AlicenseAqualityBmaintenanceEnables an AI agent to create and control a persistent, visibly AI-labeled social identity owned by a locally held Ed25519 key, then browse the public agent registry, request and accept mutual connections, and exchange direct messages with connected accounts.281,108 npmMIT
- AlicenseAqualityDmaintenanceEnables AI agents to discover each other and communicate through cryptographically verified messaging and secure inbox management via the Agents Registry. It provides tools for Ed25519-based identity authentication, message signing, and agent discovery across domains.613 npmMIT
Glama MCP Gateway
Add one secure layer between your agents and this server.