# Fidenta Verify (remote · verify.noevant.ai)

Independent fact-checking for AI answers: a verdict and sources for every claim.

- Trust score: 79/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-13

## Components

- remote · `verify.noevant.ai`: 79/100 (this document), [markdown](https://verifymcp.io/servers/ai-noevant-fidenta-verify/verify.md), [page](https://verifymcp.io/servers/ai-noevant-fidenta-verify/verify)

## Channel facts

- Endpoint: `https://verify.noevant.ai/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-13.

- **Endpoint Security**: 97/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server supports Client ID Metadata Documents, the current MCP client-registration mechanism.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 77/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 657 tokens (~131/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 13/100
  - Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 96/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 89% of tool parameters carry a description.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http ai-noevant-fidenta-verify https://verify.noevant.ai/mcp
```

### Codex

```toml
[mcp_servers.ai-noevant-fidenta-verify]
url = "https://verify.noevant.ai/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ai-noevant-fidenta-verify": {
      "type": "remote",
      "url": "https://verify.noevant.ai/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ai-noevant-fidenta-verify --url https://verify.noevant.ai/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ai-noevant-fidenta-verify:
    url: "https://verify.noevant.ai/mcp"
```

### Other

```json
{
  "mcpServers": {
    "ai-noevant-fidenta-verify": {
      "type": "http",
      "url": "https://verify.noevant.ai/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-13 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-11 (score 78, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-08-10 (score 77, 0)

- [functional regression] Schema quality: pass → fail
- [functional improvement] Stability: unverified → 0.03
- [cosmetic] “verify_claims” added an optional parameter “url”
- [cosmetic] “estimate_claims” added an optional parameter “url”
- [cosmetic] “estimate_claims” reworded the description of “text”
- [cosmetic] “verify_claims” reworded the description of “text”
- [cosmetic] “estimate_claims” made “text” optional
- [cosmetic] “verify_claims” made “text” optional

### 2026-08-09 (score 77)

First indexed and scored.

## MCP tools (5)

### `verify_claims` (~308 tokens)

Fact-check text against live web evidence from two independent retrievers, then have a model from a different lab audit the verdict. Returns per-claim verdicts: SUPPORTED, CONTRADICTED, UNSUPPORTED (searched and found nothing — not the same as false), or UNVERIFIABLE (opinion or prediction). Use before relying on a factual claim, or to check your own draft answer before sending it.

Input parameters:

- `confirm` (boolean): Required to proceed when the text contains more than 3 checkable claims. Call estimate_claims first, tell the user the claim count and credit cost, then call again with confirm true once they agree.
- `force` (boolean): Re-check even if a recent saved result exists.
- `max_claims` (integer): Hard cap on how many claims to verify, and therefore on how many credits this call can spend. Use it to bound cost on a long document.
- `text` (string): The text to verify. A single claim or a full answer containing several. May also be a bare link, e.g. 'verify https://example.com/article'.
- `url` (string): A public http(s) link to an article or web page. We fetch it, extract the readable text and verify the claims in it. Use this when the user gives you a link instead of text — you do not need to fetch…

### `estimate_claims` (~176 tokens)

FREE. Break text into checkable claims and report how many there are and how many credits verifying them would cost. Spends nothing and verifies nothing. Always call this before verify_claims on anything longer than a sentence or two — an article can contain 20 claims, and each claim costs one credit, so the user should see the price before agreeing to it.

Input parameters:

- `text` (string): The text to break into claims. May also be a bare link.
- `url` (string): A public http(s) link to an article or web page. We fetch it, extract the readable text and verify the claims in it. Use this when the user gives you a link instead of text — you do not need to fetch…

### `top_up` (~118 tokens)

Buy more verification credits without leaving the conversation. Call with confirm false (or omit it) to see the price, the card on file and the remaining monthly limit; call again with confirm true once the user has agreed. Charges the card the user already saved and authorised for in-chat top-ups — if no card is saved, or the bank requires the cardholder present, it returns a secure checkout link instead of charging.

Input parameters:

- `confirm` (boolean): True only after the user has explicitly agreed to the charge. Never set this on your own initiative.

### `recall_claim` (~33 tokens)

Look up whether a claim has already been verified on this account, without spending a verification.

Input parameters:

- `claim` (string, required)

### `check_usage` (~22 tokens)

Report how many verifications remain on this account for the current period.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/ai-noevant-fidenta-verify/verify#diagnostics

## Score history

- 2026-08-13: 79
- 2026-08-12: 78
- 2026-08-11: 78
- 2026-08-10: 77
- 2026-08-09: 77

## Links

- Remote endpoint: https://verify.noevant.ai/mcp
- Website: https://verify.noevant.ai/
- Changelog RSS feed: https://verifymcp.io/servers/ai-noevant-fidenta-verify/verify.xml
- Changelog JSON feed: https://verifymcp.io/servers/ai-noevant-fidenta-verify/verify.json
- HTML version of this page: https://verifymcp.io/servers/ai-noevant-fidenta-verify/verify