Fidenta Verify
REMOTE · VERIFY.NOEVANT.AI · SCANNED AUG 12
Independent fact-checking for AI answers: a verdict and sources for every claim.
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 Security97
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. View diagnostics → Pass
- 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
- The authorisation server supports Client ID Metadata Documents, the current MCP client-registration mechanism. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability77
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
- Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage96
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 89% of tool parameters carry a description.Partial
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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 · verify.noevant.ai
claude mcp add --transport http ai-noevant-fidenta-verify https://verify.noevant.ai/mcp
[mcp_servers.ai-noevant-fidenta-verify] url = "https://verify.noevant.ai/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ai-noevant-fidenta-verify": {
"type": "remote",
"url": "https://verify.noevant.ai/mcp",
"enabled": true
}
}
} openclaw mcp add ai-noevant-fidenta-verify --url https://verify.noevant.ai/mcp --transport streamable-http
mcp_servers:
ai-noevant-fidenta-verify:
url: "https://verify.noevant.ai/mcp" {
"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.
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.
- 11 Aug 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
- 10 Aug 26 0
- Schema quality: pass → fail ▼ functional
- Stability: unverified → 0.03 ▲ functional
- “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 cosmetic
- 9 Aug 26 77
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 12 Aug 2026 · Probed https://verify.noevant.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=noevant.ai | CN=WE1,O=Google Trust Services,C=US | 6 Aug 2026 | 4 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | bd7e120e28524bee0e10be99e0736238 |
| SANs: noevant.ai, verify.noevant.ai, *.verify.noevant.ai | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
DNSSEC insecure
Validation of verify.noevant.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| noevant.ai. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer resource_metadata="https://verify.noevant.ai/.well-known/oauth-protected-resource", scope="verify"
Bearer resource_metadata="https://verify.noevant.ai/.well-known/oauth-protected-resource", scope="verify"| Header | Value |
|---|---|
| strict-transport-security | max-age=15552000 |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
Protected resource metadata
| Document | https://verify.noevant.ai/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://verify.noevant.ai/mcp |
| Authorisation server | https://verify.noevant.ai |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://verify.noevant.ai/mcp | Verified | 200 | |
| http (plaintext) | http://verify.noevant.ai/mcp | HTTPS enforced | 301 | https://verify.noevant.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.
check_usage ~22
Report how many verifications remain on this account for the current period.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
estimate_claims ~176
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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… |
No output schema declared.
No examples provided.
recall_claim ~33
Look up whether a claim has already been verified on this account, without spending a verification.
| Name | Type | Req | Description |
|---|---|---|---|
| claim | string | yes | – |
No output schema declared.
No examples provided.
top_up ~118
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.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | boolean | – | True only after the user has explicitly agreed to the charge. Never set this on your own initiative. |
No output schema declared.
No examples provided.
verify_claims ~308
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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… |
No output schema declared.
No examples provided.