Is the Eamwhite1 Agent Trust MCP server down?

mcp-registry/io.github.eamwhite1/agent-trust · v7.0.1

healthy
Last checked 2026-10-26 17:11 UTC · handshake 254ms

As of 2026-10-26 17:11 UTC, the Eamwhite1 Agent Trust MCP server is up with a Glimind reliability score of 88/100 (grade B). Over the last 30 days it answered 99.7% of Glimind's liveness checks. It had 2 outages in 90 days, with a median recovery of 2 minutes.

uptime (30d checks)
99.7%
checks observed
1,089
outages (90d)
2
tools
54

Trustless XRPL escrow oracle for AI agents. Create jobs, verify work, release XRP/RLUSD payments.

Point your MCP client at this streamable-http endpoint: https://xrpl-referee.onrender.com

Agent-readiness: B (83/100)

B (83/100): 0 error(s), 4 warning(s) across 50 tool(s); ~18,152 tokens of tool definitions.
Scores higher than 40% of 15,769 MCP servers Glimind has audited.
Its tool list costs an agent ~18,152 tokens per session — more than 95% of servers.
84 → 83 since 2026-10-22
no tool-poisoning patterns
Schemas100
Descriptions89
Safety hints100
Token cost23
Client compatibility100
Protocol100
Reliability100
Stability44

What to fix (5)

2 tool definition(s) exceed ~1,200 tokens each (largest: create_escrow_vault, ~2,722).

Move long reference material out of descriptions (link a doc or expose a resource), drop repeated examples, and collapse large enums. Trimming these to ~600 tokens saves ~3,337 tokens every session. How to fix →

Tools: create_escrow_vault, hire_and_pay · saves ~3,337 tokens/session

50 tools on one server. Tool-selection accuracy drops as the menu grows, and some clients (e.g. Cursor) cap the number of active tools.

Group tools by task into smaller servers or toolsets, and merge near-duplicates behind one tool with a mode parameter. How to fix →

1 parameter(s) across 1 tool(s) have no description.

Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →

Tools: recommend_release_conditions

Loading this server's tool list costs an agent ~18,152 tokens before any work — more than 95% of MCP servers.

Split rarely-used tools into a separate server or a toolset the client can enable, or expose one "search tools" entry point. Many agents load every connected server's tools into every request. How to fix →

In the last 30 days: 0 tool(s) removed and 14 schema change(s).

Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.eamwhite1/agent-trust"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/io.github.eamwhite1/agent-trust"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

Markdown
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.eamwhite1%2Fagent-trust.svg)](https://glimind.com/server/mcp-registry%2Fio.github.eamwhite1%2Fagent-trust?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fio.github.eamwhite1%2Fagent-trust?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.eamwhite1%2Fagent-trust.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.eamwhite1%2Fagent-trust.svg
   :target: https://glimind.com/server/mcp-registry%2Fio.github.eamwhite1%2Fagent-trust?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:3d089d7226c6966b…, first seen 2026-10-25, included at leaf 67535 of 74,323. Version history · verify what your client received.

Tools (54)

Compare: most reliable security servers · most reliable ml servers · most reliable finance servers · most reliable knowledge servers · most reliable other servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Eamwhite1 Agent Trust MCP server down right now?

As of 2026-10-26 17:11 UTC, the Eamwhite1 Agent Trust MCP server is up with a Glimind reliability score of 88/100 (grade B). Over the last 30 days it answered 99.7% of Glimind's liveness checks. It had 2 outages in 90 days, with a median recovery of 2 minutes.

How many tools does Eamwhite1 Agent Trust MCP server provide?

Eamwhite1 Agent Trust MCP server advertises 54 tools, including assess_counterparty_and_job, audit, audit_task, award_job, batch_wallet_trust_scores.

How do I install Eamwhite1 Agent Trust MCP server?

Point your MCP client at this streamable-http endpoint: https://xrpl-referee.onrender.com

Is the Eamwhite1 Agent Trust MCP server safe to connect to an AI agent?

Glimind scanned all 50 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Eamwhite1 Agent Trust MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.

Feedback
Help us improve