Skip to content

Fidenta Verify MCP server

ai.noevant/fidenta-verifynoevant.aistreamable-httpv1.0.0Scanned

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

5 tools: 5 change things.

Tools: 0 delete, 0 irreversible, 5 write, 0 read.
  • Reads private data · 0
  • Reads text others write · 2
  • Can send data out · 2
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

5 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Fidenta Verify MCP server can do

The Fidenta Verify MCP server is published by noevant.ai, a domain the MCP Registry verified. It has 5 tools. It can create or change data (5 tools: verify_claims, estimate_claims, top_up, recall_claim and 1 more), but cannot delete data. None of its tools only reads.

2 tools bring in text other people can write (verify_claims and top_up); 2 tools can send data out of your system (verify_claims and estimate_claims).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 11, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

5 tools

Changes things 5Claude Code: ask
  • check_usageReport how many verifications remain on this account for the current period.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Report how many verifications remain on this account for the current period.

    Annotations the server declares

    • title: Check remaining verifications
    • readOnlyHint: true
    • openWorldHint: false
  • estimate_claimsFREE.Can send data outNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Estimate claims and cost
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • recall_claimLook up whether a claim has already been verified on this account, without spending a verification.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Look up whether a claim has already been verified on this account, without spending a verification.

    Annotations the server declares

    • title: Recall a previous verification
    • readOnlyHint: true
    • openWorldHint: false
  • top_upBuy more verification credits without leaving the conversation.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Top up credits
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
  • verify_claimsFact-check text against live web evidence from two independent retrievers, then have a model from a different lab audit the verdict.Reads text others writeCan send data outNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Verify claims against live sources
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write2
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out2
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:26 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
5
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://verify.noevant.ai/.well-known/oauth-protected-resource/mcp
Authorization servers
https://verify.noevant.ai
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
yes
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 5 tools that change things (5 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://verify.noevant.ai/mcp: tools/list returned 5 tools to an anonymous client, including verify_claims (write), estimate_claims (write), top_up (write), recall_claim (write), check_usage (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [],
    "ask": [
      "mcp__fidenta-verify__verify_claims",
      "mcp__fidenta-verify__estimate_claims",
      "mcp__fidenta-verify__top_up",
      "mcp__fidenta-verify__recall_claim",
      "mcp__fidenta-verify__check_usage"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as fidenta-verify. Review it before you use it.

Capability tags behind 3 rules
  • mcp__fidenta-verify__verify_claims untrusted-input, outbound
  • mcp__fidenta-verify__estimate_claims outbound
  • mcp__fidenta-verify__top_up untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/ai.noevant/fidenta-verify/verify?hash=06c0741b44c35313da676d3609380821bb0b0ccdc686cc81d400bdda232e520b" | jq -e '.changed == false'

Pinned hash 06c0741b44c3, from Nov 11, 2026, 20:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/ai.noevant/fidenta-verify/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for ai.noevant/fidenta-verify
[![Anlyon Radar](https://radar.anlyon.com/badge/ai.noevant/fidenta-verify.svg)](https://radar.anlyon.com/servers/ai.noevant/fidenta-verify)

Source: MCP Registry. Synced Oct 21, 2026, 17:42 UTC.

Fidenta Verify MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Fidenta Verify MCP server safe?

No scan can promise that. What its definitions show: 5 tools, 5 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Fidenta Verify MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Fidenta Verify MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Fidenta Verify MCP server have?

5 tools: 5 write. verify_claims, estimate_claims, top_up, recall_claim and check_usage.

Does the Fidenta Verify MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Fidenta Verify MCP server send data to outside services?

2 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): verify_claims and estimate_claims.

Has the Fidenta Verify MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 11, 2026.