Eous
REMOTE · WWW.PARTNERWITH.AI
Checks a claim at its primary source and grades it. A person reviews every answer.
Available components
Last scanned (3 hours ago)
Scores higher than 92% of remote servers
Reachable. Last reached 17 Oct 2026.
Category Search and Retrieval
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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability81
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 446 tokens (~111/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management73
- Stability observed for 22 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
- Structured output schemas are declared (75% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
- 17 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 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 40 to 50. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 40. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Sept 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.
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 17 Oct 2026 · Probed https://www.partnerwith.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=www.partnerwith.ai | CN=YR1,O=Let's Encrypt,C=US | 22 Sept 2026 | 21 Dec 2026 | RSA 2048 | SHA256-RSA | 6401c6d3f47cd0c0094835d1e3a981a3ea6 |
| SANs: www.partnerwith.ai | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of www.partnerwith.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| partnerwith.ai. | 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.partnerwith.ai/mcp | Verified | 200 | |
| http (plaintext) | http://www.partnerwith.ai/mcp | HTTPS enforced | 308 | https://www.partnerwith.ai/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 →
about_eous About Eous ~37
What Eous is, what it does and does not do, and how to work with Forged Lucidity. Read this before submitting.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
check_status Check a claim or a message ~51
Look up a claim or a message by its receipt ID. Shows the answer once a person has released it.
| Name | Type | Req | Description |
|---|---|---|---|
| receipt_id | string | yes | The EOUS-... receipt ID from submit_claim or contact_us. |
| Name | Type | Req | Description |
|---|---|---|---|
| receipt_id | string | yes | – |
| reply | string | – | – |
| status | string | yes | – |
| type | string | yes | – |
| updated_at | string | yes | – |
No examples provided.
contact_us Send Forged Lucidity a message ~134
Send a question, or a scoping, partnership or press message. Returns a receipt ID. A person reads every message before anyone replies; nothing is instant.
| Name | Type | Req | Description |
|---|---|---|---|
| acknowledge | boolean | yes | Must be true: this is not legal, medical, or financial advice, no lawyer-client relationship is formed, and no confidential information is included. |
| contact_email | string | – | Optional. If given, a person may reply by email. |
| kind | string | yes | What this is about: question, scoping, partnership, press or other. |
| message | string | yes | Your message, 10 to 4,000 characters. |
| Name | Type | Req | Description |
|---|---|---|---|
| receipt_id | string | yes | – |
| received_at | string | yes | – |
| status | string | yes | – |
No examples provided.
submit_claim Submit a claim to be checked ~192
Send one claim to be checked at its primary source and graded. Returns a receipt ID. A person reviews every submission before any answer is released; nothing is instant.
| Name | Type | Req | Description |
|---|---|---|---|
| acknowledge | boolean | yes | Must be true: this is not legal, medical, or financial advice, no lawyer-client relationship is formed, and no confidential information is included. |
| claim | string | yes | The claim to check, in one or two sentences, quoted as you found it. |
| contact_email | string | – | Optional. If given, a person may email you when the answer is released. |
| context | string | – | Where you saw the claim and why it matters to you. Optional. |
| publish_ok | boolean | – | May Eous publish the claim and its grade on the public ledger, without names? Default no. |
| sources | array | – | Where the claim says it comes from: URLs or citations, up to 10. |
| Name | Type | Req | Description |
|---|---|---|---|
| receipt_id | string | yes | – |
| received_at | string | yes | – |
| status | string | yes | – |
No examples provided.
How do I install the Eous MCP server?
Eous is a hosted endpoint at https://www.partnerwith.ai/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.partnerwith.ai
claude mcp add --transport http ai-partnerwith-eous 'https://www.partnerwith.ai/mcp'
What is the Eous MCP server?
Eous is an MCP server listed in the public MCP registry as ai.partnerwith/eous. Checks a claim at its primary source and grades it. A person reviews every answer. This page covers its hosted endpoint (https://www.partnerwith.ai/mcp).
Is the Eous MCP server safe to use?
Eous scores 85 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 Eous MCP server expose?
Eous exposes 4 tools: about_eous, submit_claim, contact_us, check_status. Their descriptions and schemas cost roughly 414 tokens of context every time the server is loaded.
Does the Eous MCP server require authentication?
No. We connected to Eous without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Eous MCP server still maintained?
Eous is still listed as active in the MCP registry. We last reached this channel on 17 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.