EthersFlow — Trust Gate for AI Agents
REMOTE · WWW.ETHERSFLOW.COM · 2 COMPONENTS · SCANNED OCT 12
Trust gate for AI agents: multi-model adversarial consensus, signed and verifiable verdicts.
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 → Why this is hard to score →
Endpoint Security60
- 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 1 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 is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability62
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 255 tokens (~255/item across 1 items; 1 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management70
- Stability observed for 21 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage97
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 90% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 1 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
How do I install the EthersFlow — Trust Gate for AI Agents MCP server?
EthersFlow — Trust Gate for AI Agents is a hosted endpoint at https://www.ethersflow.com/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · www.ethersflow.com
claude mcp add --transport http ethersflow-ethersflow 'https://www.ethersflow.com/api/mcp'
{
"mcpServers": {
"ethersflow-ethersflow": {
"url": "https://www.ethersflow.com/api/mcp"
}
}
} {
"servers": {
"ethersflow-ethersflow": {
"type": "http",
"url": "https://www.ethersflow.com/api/mcp"
}
}
} [mcp_servers.ethersflow-ethersflow] url = "https://www.ethersflow.com/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ethersflow-ethersflow": {
"type": "remote",
"url": "https://www.ethersflow.com/api/mcp",
"enabled": true
}
}
} openclaw mcp add ethersflow-ethersflow --url 'https://www.ethersflow.com/api/mcp' --transport streamable-http
mcp_servers:
ethersflow-ethersflow:
url: "https://www.ethersflow.com/api/mcp" {
"McpServers": {
"ethersflow-ethersflow": {
"Transport": "http",
"Url": "https://www.ethersflow.com/api/mcp"
}
}
} assistant mcp add ethersflow-ethersflow -t streamable-http -u 'https://www.ethersflow.com/api/mcp'
{
"mcpServers": {
"ethersflow-ethersflow": {
"type": "http",
"url": "https://www.ethersflow.com/api/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.
- 12 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 70. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Oct 26 +2
No change was recorded against any check on this day. Stability & Change Management went from 53 to 63. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Oct 26 −8
- Schema quality: 215 → 255 ▼ functional
- Stability: pass → 0.53 functional
- 4 Oct 26 0
- Server version: 0.2.11 → 0.2.12 functional
- 3 Oct 26 +1
- Stability: 0.97 → pass security
- Server version: 0.2.8 → 0.2.11 functional
- 1 Oct 26 +1
- Server version: 0.2.7 → 0.2.8 functional
- 30 Sept 26 0
- Server version: 0.2.6 → 0.2.7 functional
- 29 Sept 26 +1
- Server version: 0.2.3 → 0.2.6 functional
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 12 Oct 2026 · Probed https://www.ethersflow.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=www.ethersflow.com | CN=WR3,O=Google Trust Services,C=US | 7 Sept 2026 | 6 Dec 2026 | RSA 2048 | SHA256-RSA | 339f0ea9971a41e610cbc74919402cbf |
| SANs: www.ethersflow.com | ||||||
| CN=WR3,O=Google Trust Services,C=US (CA) | CN=GTS Root R1,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | RSA 2048 | SHA256-RSA | 7ff005a91568d63abc22861684aa4b5a |
| CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 19 Jun 2020 | 28 Jan 2028 | RSA 4096 | SHA256-RSA | 77bd0d6cdb36f91aea210fc4f058d30d |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of www.ethersflow.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| ethersflow.com. | present | 64628, 64628 | 13, 13 | Verified |
| www.ethersflow.com. | Verified address RRset verified with the apex keys |
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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.ethersflow.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://www.ethersflow.com/api/mcp | HTTPS enforced | 302 | https://www.ethersflow.com/api/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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
verify_agent_action ~255
Gate and verify autonomous AI agent action decisions (e.g. trades, emails, claims, API calls) via EthersFlow Multi-Model Federated Adversarial Consensus before execution.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_action | string | yes | The proposed action the agent intends to take. |
| agent_count | number | – | Number of adversarial audit nodes (2 to 7, default 3). |
| context | object | – | Structured contextual evidence, metadata, or source document references. |
| grounding_enabled | boolean | – | Enable hybrid fact grounding verification. |
| persona_preset | string | – | – |
| policy_id | string | – | Optional policy pack identifier to evaluate against. |
| reasoning_chain | string | – | The agent's internal reasoning or context leading to this decision. |
| scope_grant | object | – | Explicit kernel-resolvable subject authorization or scope grant evidence (e.g. { subject_id, granted_by, consent_verified, status: 'VERIFIED' }). |
| scope_hint | string | – | Optional domain or task scope hint (e.g. 'clinical_safety', 'financial_compliance', 'legal_citation', 'cybersecurity_auditor'). |
| zero_retention | boolean | – | Enforce zero data retention (ZDR). |
No output schema declared.
No examples provided.
What is the EthersFlow — Trust Gate for AI Agents MCP server?
EthersFlow — Trust Gate for AI Agents is an MCP server listed in the public MCP registry as io.github.Ethersflow/EthersFlow. Trust gate for AI agents: multi-model adversarial consensus, signed and verifiable verdicts. This page covers its hosted endpoint (https://www.ethersflow.com/api/mcp).
Is the EthersFlow — Trust Gate for AI Agents MCP server safe to use?
EthersFlow — Trust Gate for AI Agents scores 70 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the EthersFlow — Trust Gate for AI Agents MCP server expose?
EthersFlow — Trust Gate for AI Agents exposes 1 tool: verify_agent_action. Their descriptions and schemas cost roughly 255 tokens of context every time the server is loaded.
Does the EthersFlow — Trust Gate for AI Agents MCP server require authentication?
No. We connected to EthersFlow — Trust Gate for AI Agents without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the EthersFlow — Trust Gate for AI Agents MCP server still maintained?
EthersFlow — Trust Gate for AI Agents is still listed as active in the MCP registry. We last reached this channel on 12 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.