Atlas entry
relayger.com
1 capability over A2A. The inventory is incomplete. First atlas observation.
Surfaces
5 protocols checked
| ARD | invalid | 1 retrieved artifact |
|---|---|---|
| A2A | Valid | 1 skill |
| MCP | unreachable | Tool inventory unavailable · resource inventory unavailable · prompt inventory unavailable |
| OpenAPI | Not detected | 0 operations |
| WebMCP | Not detected | 0 declarative form tools · experimental |
Exact states and meaning
- ARDfailed
Exact state: invalid · 1 retrieved artifact
InterfaceDelta retained the machine state “invalid” without assigning an additional meaning.
Not observed / not fetched
- A2Aobserved
Exact state: valid · 1 skill
A usable protocol document was retrieved and validated.
Directly observed
- MCPfailed
Exact state: unreachable · Tool inventory unavailable · resource inventory unavailable · prompt inventory unavailable
The supported discovery location did not provide a usable response within the observation boundary.
An unreachable result does not prove the service is unavailable to every client or that it advertises no capabilities.
Not observed / not fetched
- OpenAPIabsent
Exact state: not detected · 0 operations
No endpoint was established from the evidence and scope that InterfaceDelta inspected.
Not detected does not prove that no endpoint exists.
Not observed / not fetched
- WebMCPabsent
Exact state: not detected · 0 declarative form tools · experimental
No named declarative WebMCP form tools were observed in the origin root HTML.
Script-registered tools and other pages are not observed, so this does not mean the site has no WebMCP tools.
Not observed / not fetched
Capabilities
1 · inventory incomplete
The atlas shows each capability by its plain identifier, inputs and declared sign-in. Publisher descriptions, paths, links and source evidence are not published here.
A2A skills 1
relayger-helprelayger declared
MCP tools 0+ observed
Inventory incomplete. MCP tools could not be fully inventoried: the ARD document was not valid, so declarations made there were not read.
None recorded in this Passport.
MCP resources 0+ observed
Inventory incomplete. MCP resources could not be fully inventoried: the ARD document was not valid, so declarations made there were not read.
None recorded in this Passport.
MCP prompts 0+ observed
Inventory incomplete. MCP prompts could not be fully inventoried: the ARD document was not valid, so declarations made there were not read.
None recorded in this Passport.
OpenAPI operations 0+ observed
Inventory incomplete. OpenAPI operations could not be fully inventoried: the ARD document was not valid, so declarations made there were not read.
None recorded in this Passport.
Declared and observed
No tools declare hints.
A disagreement is not a finding about the service: either side can be wrong. How we compare declarations and readings.
Atlas history
1 observation
- 1 capability · A2A and MCP · MCP endpoint unreachableFirst observation
Fingerprint and versions
- Fingerprint
ce6505bd8585750b7eb18ce38fe176cb6a2ce8f61f384beaa5ec84207464ef0d- Passport schema
- 0.5.0, passport-semantic-v4
- Consistency
- OPENAPI_MCP_EXPLICIT_MAPPING: not applicable
Each class compares an observation with the previous atlas observation. Runs of unchanged observations are grouped. Struck values are what the previous observation recorded; inserted values are what this one recorded.
About this entry
com.relayger/messagingListedOfficial MCP Registry · first listed 3 Nov 2026 · last listed 3 Nov 2026
Passive observations of a public interface listed in the Official MCP Registry. An observation does not verify security, ownership or compliance, and InterfaceDelta assigns no scores or rankings. Methodology · Report an inaccuracy · Ask for removal
Identity and snapshot
- Target key
sha256:e960b278e4a6d6ae293040b7f1e71aef3eaba1217cd1d8ecac2330ec6d7fe922- Locator SHA-256
253344cdda45a04e1954f54e5573624d5693f6e8726460eb7ec7844d01424dbc- Snapshot generated
- 4 Nov 2026, 00:59 UTC
The entry is one exact observed target, not a real-world service identity, and implies no ownership. Endpoint paths are not published; the locator hash lets an operator confirm their own URL.

