Agent Handoff
REMOTE · AGENT-HANDOFF-PRODUCTION-573C.UP.RAILWAY.APP · SCANNED AUG 3
Pass messages between AI agents with cleaning, metadata enrichment, and metered billing.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 2 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability71
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 192 tokens (~96/item across 2 items; 2 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
- Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · agent-handoff-production-573c.up.railway.app
claude mcp add --transport http jordan23wagner-ops-agent-handoff https://agent-handoff-production-573c.up.railway.app/mcp
[mcp_servers.jordan23wagner-ops-agent-handoff] url = "https://agent-handoff-production-573c.up.railway.app/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"jordan23wagner-ops-agent-handoff": {
"type": "remote",
"url": "https://agent-handoff-production-573c.up.railway.app/mcp",
"enabled": true
}
}
} openclaw mcp add jordan23wagner-ops-agent-handoff --url https://agent-handoff-production-573c.up.railway.app/mcp --transport streamable-http
mcp_servers:
jordan23wagner-ops-agent-handoff:
url: "https://agent-handoff-production-573c.up.railway.app/mcp" {
"mcpServers": {
"jordan23wagner-ops-agent-handoff": {
"type": "http",
"url": "https://agent-handoff-production-573c.up.railway.app/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 2 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 29 Jul 26 +1
- Stability: unverified → 0.03 ▲ functional
- 28 Jul 26 62
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 3 Aug 2026 · Probed https://agent-handoff-production-573c.up.railway.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.up.railway.app | CN=YE1,O=Let's Encrypt,C=US | 29 Jul 2026 | 27 Oct 2026 | ECDSA 256 | ECDSA-SHA384 | 6da79bb561da3efeb0e751ca21abd3999fe |
| SANs: *.up.railway.app, up.railway.app | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
DNSSEC insecure
Validation of agent-handoff-production-573c.up.railway.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| railway.app. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://agent-handoff-production-573c.up.railway.app/mcp | Verified | 200 | |
| http (plaintext) | http://agent-handoff-production-573c.up.railway.app/mcp | HTTPS enforced | 301 | https://agent-handoff-production-573c.up.railway.app/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.
get_usage_stats ~30
Return this account's total handoff count and the most recent handoffs. Read-only and not billed.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
handoff ~129
Hand a message off to another agent. Cleans and normalizes the payload, stamps it with handoff metadata (id, timestamp, estimated tokens, target agent), and records the handoff. Use this when passing work or context from one agent to the next in a multi-agent pipeline. This is a metered, billable operation.
| Name | Type | Req | Description |
|---|---|---|---|
| message | string|object|array|number|boolean | yes | The payload to hand off. Accepts a plain string or a JSON object. Max 256 KB. |
| next_agent | string | yes | Name/identifier of the agent receiving this handoff. |
No output schema declared.
No examples provided.