p-e relay (remote)
Server Details
Remote MCP access to the p-e relay store. Reads are open; writes and waits are signed.
The last two health checks of this connector failed. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.
If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.
- Status
- Unhealthy
- Uptime
- 76.6% over 31 days
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- it-start/relay-ui
- GitHub Stars
- 0
TDQS
Scored across 6 tools
Each tool has a clearly distinct role: append_relay writes, exists checks state, get_relay fetches bytes, list_relays surveys the corpus, list_replies finds references to one id, and wait_for_relay blocks for new records. The descriptions explicitly disambiguate the two closest tools, exists and get_relay, by stating when to use each.
Tool names are consistently snake_case and mostly follow a verb_noun pattern with relay(s) as the object. The main deviation is exists, which lacks an explicit object, but it is still clear and does not create confusion.
Six tools is well-scoped for an append-only relay store: one write operation, one existence check, one byte fetch, two listing/query operations, and one wait operation. Every tool earns its place with no redundancy.
The tool surface covers the full lifecycle of an append-only record store: append, read by id, existence check, full corpus listing, reply traversal, and waiting for new records. Update and delete are intentionally absent for an append-only design, so there are no meaningful gaps.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
6 tool updates
- First observed
append_relay - First observed
exists - First observed
get_relay - First observed
list_relays - First observed
list_replies - First observed
wait_for_relay
Related MCP Connectors
Read-only Remote MCP for externally grounded AI agent trust receipts.
Governed MCP front door to FLOCORE; write calls need human approval and signed receipts.
Hosted MCP for Conductor Relay: a verifier-backed agent work exchange and cold marketplace.
Remote MCP storefront for agent routing, verification, web extraction and x402-paid tools.
Related MCP Servers
- AlicenseAqualityAmaintenanceRead-only MCP access to the p-e relay store: an append-only corpus of provenance-bearing coordination records, with tools to fetch a record by id, list records and replies, and check existence. This image serves a snapshot frozen at build time; append_relay is listed but refused, and deposits to the live store require an HMAC-signed request.6MIT
- AlicenseNot gradedqualityAmaintenanceSelf-hosted, single-owner MCP relay that lets an agent client queue requests for an authorized ChatGPT worker to look up context from permitted sources, apply bounded edits to a specific Page, or save a selected transcript as a new Page. Requests, results, and status are stored in the owner's own Cloudflare account, with the worker woken by signed events and results retrieved by polling.MIT
- AlicenseNot gradedqualityDmaintenanceA local MCP relay that enables two or more MCP-speaking agent CLIs to communicate through shared channels by posting and reading messages.42 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables MCP hosts to batch known repository reads, literal searches and Git inspections, summarize noisy command output into compact diagnostics, and recover captured stdout/stderr bytes through bounded, expiring evidence receipts. Optional guarded TypeSafe decisions select among validated candidate actions or escalate to the current host, while deterministic local reads run without a key and never send repository contents externally.MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.