Skip to content

R/IV — Verify Claims, Citations & Agent Actions MCP server

io.github.duranivrobert-glitch/rivduranivrobert-glitchstreamable-httpv3.2.3Scanned

Verify claims, citations & agent actions. Free receipt trial; paid prices via live R/IV quotes.

35 tools: 30 change things and 5 only read.

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

Tools listed without sign-in. Remote posture

Anlyon alternative

30 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

Its sign-in does not let Anlyon set up an OAuth client on its own, so there is no link to it here.

What the R/IV — Verify Claims, Citations & Agent Actions MCP server can do

The R/IV — Verify Claims, Citations & Agent Actions MCP server is published by the GitHub account duranivrobert-glitch. It has 35 tools. It can create or change data (30 tools: service.match, provenance.receipt.trial, citation.verify, claim.check and 26 more), but cannot delete data. 5 tools only read.

1 tool brings in text other people can write (source.snapshot); 2 tools can send data out of your system (source.verify and source.snapshot).

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 19, 2026, version 3.2.3.

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.

35 tools

Changes things 30Claude Code: ask
  • agent.action.verifyR/IV agent.action.verify — independent evidence-verification primitive for agent assurance.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.
    Description, as the server wrote it
    R/IV agent.action.verify — independent evidence-verification primitive for agent assurance. Completed paid execution returns an RVO plus signed R/IV Verification Receipt.
  • agent.monitorR/IV agent.monitor — independent evidence-verification primitive for monitoring.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.
    Description, as the server wrote it
    R/IV agent.monitor — independent evidence-verification primitive for monitoring. Completed paid execution returns an RVO plus signed R/IV Verification Receipt.
  • ai.use.auditR/IV ai.use.audit — independent evidence-verification primitive for enterprise assurance.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.
    Description, as the server wrote it
    R/IV ai.use.audit — independent evidence-verification primitive for enterprise assurance. Completed paid execution returns an RVO plus signed R/IV Verification Receipt.
  • answer.auditR/IV answer.audit — independent evidence-verification primitive for 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.
    Description, as the server wrote it
    R/IV answer.audit — independent evidence-verification primitive for verification. Completed paid execution returns an RVO plus signed R/IV Verification Receipt.
  • citation.verifyR/IV citation.verify — independent evidence-verification primitive for 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.
    Description, as the server wrote it
    R/IV citation.verify — independent evidence-verification primitive for verification. Completed paid execution returns an RVO plus signed R/IV Verification Receipt.
  • claim.checkR/IV claim.check — independent evidence-verification primitive for claims.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.
    Description, as the server wrote it
    R/IV claim.check — independent evidence-verification primitive for claims. Completed paid execution returns an RVO plus signed R/IV Verification Receipt.
  • claim.monitorR/IV claim.monitor — independent evidence-verification primitive for monitoring.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.
    Description, as the server wrote it
    R/IV claim.monitor — independent evidence-verification primitive for monitoring. Completed paid execution returns an RVO plus signed R/IV Verification Receipt.
  • contradiction.scanR/IV contradiction.scan — independent evidence-verification primitive for evidence.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.
    Description, as the server wrote it
    R/IV contradiction.scan — independent evidence-verification primitive for evidence. Completed paid execution returns an RVO plus signed R/IV Verification Receipt.
  • control.checkR/IV control.check — independent evidence-verification primitive for enterprise assurance.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.
    Description, as the server wrote it
    R/IV control.check — independent evidence-verification primitive for enterprise assurance. Completed paid execution returns an RVO plus signed R/IV Verification Receipt.
  • data.flow.verifyR/IV data.flow.verify — independent evidence-verification primitive for enterprise assurance.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.
    Description, as the server wrote it
    R/IV data.flow.verify — independent evidence-verification primitive for enterprise assurance. Completed paid execution returns an RVO plus signed R/IV Verification Receipt.
  • dependency.mapR/IV dependency.map — independent evidence-verification primitive for dependency risk.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.
    Description, as the server wrote it
    R/IV dependency.map — independent evidence-verification primitive for dependency risk. Completed paid execution returns an RVO plus signed R/IV Verification Receipt.
  • dependency.monitorR/IV dependency.monitor — independent evidence-verification primitive for monitoring.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.
    Description, as the server wrote it
    R/IV dependency.monitor — independent evidence-verification primitive for monitoring. Completed paid execution returns an RVO plus signed R/IV Verification Receipt.
  • evidence.bundleR/IV evidence.bundle — independent evidence-verification primitive for evidence.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.
    Description, as the server wrote it
    R/IV evidence.bundle — independent evidence-verification primitive for evidence. Completed paid execution returns an RVO plus signed R/IV Verification Receipt.
  • evidence.monitorR/IV evidence.monitor — independent evidence-verification primitive for monitoring.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.
    Description, as the server wrote it
    R/IV evidence.monitor — independent evidence-verification primitive for monitoring. Completed paid execution returns an RVO plus signed R/IV Verification Receipt.
  • fact.extractR/IV fact.extract — independent evidence-verification primitive for evidence.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.
    Description, as the server wrote it
    R/IV fact.extract — independent evidence-verification primitive for evidence. Completed paid execution returns an RVO plus signed R/IV Verification Receipt.
  • investigation.runR/IV investigation.run — independent evidence-verification primitive for investigation reporting.No findings

    Why it is in this group

    • The name "investigation.run" says "run": a word for a change.
    Description, as the server wrote it
    R/IV investigation.run — independent evidence-verification primitive for investigation reporting. Completed paid execution returns an RVO plus signed R/IV Verification Receipt.
  • model.change.auditR/IV model.change.audit — independent evidence-verification primitive for dependency risk.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.
    Description, as the server wrote it
    R/IV model.change.audit — independent evidence-verification primitive for dependency risk. Completed paid execution returns an RVO plus signed R/IV Verification Receipt.
  • number.verifyR/IV number.verify — independent evidence-verification primitive for 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.
    Description, as the server wrote it
    R/IV number.verify — independent evidence-verification primitive for verification. Completed paid execution returns an RVO plus signed R/IV Verification Receipt.
  • policy.monitorR/IV policy.monitor — independent evidence-verification primitive for monitoring.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.
    Description, as the server wrote it
    R/IV policy.monitor — independent evidence-verification primitive for monitoring. Completed paid execution returns an RVO plus signed R/IV Verification Receipt.
  • procurement.evidenceR/IV procurement.evidence — independent evidence-verification primitive for enterprise assurance.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.
    Description, as the server wrote it
    R/IV procurement.evidence — independent evidence-verification primitive for enterprise assurance. Completed paid execution returns an RVO plus signed R/IV Verification Receipt.
  • provenance.receiptR/IV provenance.receipt — independent evidence-verification primitive for provenance.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.
    Description, as the server wrote it
    R/IV provenance.receipt — independent evidence-verification primitive for provenance. Completed paid execution returns an RVO plus signed R/IV Verification Receipt.
  • provenance.receipt.trialRun one free signed R/IV provenance receipt trial.No findings

    Why it is in this group

    • The description's first verb is "run": a word for a change.
    Description, as the server wrote it
    Run one free signed R/IV provenance receipt trial. No payment or account required.
  • quote.verifyR/IV quote.verify — independent evidence-verification primitive for 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.
    Description, as the server wrote it
    R/IV quote.verify — independent evidence-verification primitive for verification. Completed paid execution returns an RVO plus signed R/IV Verification Receipt.
  • service.matchMatch a verification goal to the smallest R/IV capability without charging.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.
    Description, as the server wrote it
    Match a verification goal to the smallest R/IV capability without charging.
  • source.verifyR/IV source.verify — independent evidence-verification primitive for verification.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.

    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
    R/IV source.verify — independent evidence-verification primitive for verification. Completed paid execution returns an RVO plus signed R/IV Verification Receipt.
  • timeline.reconcileR/IV timeline.reconcile — independent evidence-verification primitive for retrieval reconstruction.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.
    Description, as the server wrote it
    R/IV timeline.reconcile — independent evidence-verification primitive for retrieval reconstruction. Completed paid execution returns an RVO plus signed R/IV Verification Receipt.
  • transaction.verifyR/IV transaction.verify — independent evidence-verification primitive for 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.
    Description, as the server wrote it
    R/IV transaction.verify — independent evidence-verification primitive for verification. Completed paid execution returns an RVO plus signed R/IV Verification Receipt.
  • vendor.diligenceR/IV vendor.diligence — independent evidence-verification primitive for dependency risk.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.
    Description, as the server wrote it
    R/IV vendor.diligence — independent evidence-verification primitive for dependency risk. Completed paid execution returns an RVO plus signed R/IV Verification Receipt.
  • vendor.monitorR/IV vendor.monitor — independent evidence-verification primitive for monitoring.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.
    Description, as the server wrote it
    R/IV vendor.monitor — independent evidence-verification primitive for monitoring. Completed paid execution returns an RVO plus signed R/IV Verification Receipt.
  • workflow.verifyR/IV workflow.verify — independent evidence-verification primitive for agent assurance.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.
    Description, as the server wrote it
    R/IV workflow.verify — independent evidence-verification primitive for agent assurance. Completed paid execution returns an RVO plus signed R/IV Verification Receipt.
Only reads 5Show 5 read-only tools
  • capabilities.listList all 29 production R/IV verification capabilities.No findings

    Why it is in this group

    • The name "capabilities.list" says "list": a word for reading.
    Description, as the server wrote it
    List all 29 production R/IV verification capabilities.
  • example.getReturn a synthetic example only; never counts as demand.No findings

    Why it is in this group

    • The name "example.get" says "get": a word for reading.
    Description, as the server wrote it
    Return a synthetic example only; never counts as demand.
  • pricing.quoteGet public R/IV pricing and machine-payment routes without charging or authentication.No findings

    Why it is in this group

    • The description's first verb is "get": a word for reading.
    Description, as the server wrote it
    Get public R/IV pricing and machine-payment routes without charging or authentication.
  • source.snapshotR/IV source.snapshot — independent evidence-verification primitive for provenance.Reads text others writeCan send data outNo findings

    Why it is in this group

    • The name "source.snapshot" says "snapshot": a word for reading.

    What it can reach

    • untrusted-inputThe input takes a URL (input.url), and the tool reads it: it reads web pages, which anyone can write.
    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.

    Claude Code: ask, because it is tagged outbound.

    Description, as the server wrote it
    R/IV source.snapshot — independent evidence-verification primitive for provenance. Completed paid execution returns an RVO plus signed R/IV Verification Receipt.
  • system.statusRead R/IV production system status.No findings

    Why it is in this group

    • The name "system.status" says "status": a word for reading.
    Description, as the server wrote it
    Read R/IV production system status.

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 write1
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, 19:04 UTC, unchanged since Nov 20, 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
31
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://rdiv-production-runtime-production.up.railway.app/.well-known/oauth-protected-resource/mcp
Authorization servers
https://rdiv-production-runtime-production.up.railway.app
Legacy HTTP+SSE transport
no
Dynamic client registration
no
Client ID metadata documents
no
  • WarnThe whole server

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

    Matched text

    https://rdiv-production-runtime-production.up.railway.app/mcp: tools/list returned 35 tools to an anonymous client, including service.match (write), provenance.receipt.trial (write), citation.verify (write), claim.check (write), answer.audit (write) and 26 more

    What this check looks for

Posture changes

  1. Nov 20, 2026
    • Tools that change things, listed without credentials: 30 to 31
  2. Nov 13, 2026
    • HTTP status of an anonymous initialize: 404 to 200
    • tools/list served without credentials: no to yes
    • Tools that change things, listed without credentials: 0 to 30
    • Protocol version: none to 2025-06-18
    • RFC 9728 protected resource metadata: none to https://rdiv-production-runtime-production.up.railway.app/.well-known/oauth-protected-resource/mcp
    • Authorization servers: none to https://rdiv-production-runtime-production.up.railway.app
    • Dynamic client registration: not observed to no
    • Client ID metadata documents: not observed to no
  3. Nov 6, 2026
    • HTTP status of an anonymous initialize: 200 to 404
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 30 to 0
    • Protocol version: 2025-06-18 to none
    • RFC 9728 protected resource metadata: https://rdiv-production-runtime-production.up.railway.app/.well-known/oauth-protected-resource/mcp to none
    • Authorization servers: https://rdiv-production-runtime-production.up.railway.app to none
    • Dynamic client registration: no to not observed
    • Client ID metadata documents: no to not observed

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.

  1. PostureRemote posture changed. Tools that change things, listed without credentials: 30 -> 31.View diff
    • Tools that change things, listed without credentials: 30 to 31
  2. PostureRemote posture changed. HTTP status of an anonymous initialize: 404 -> 200; tools/list served without credentials: no -> yes; Tools that change things, listed without credentials: 0 -> 30 (and 5 more).View diff
    • HTTP status of an anonymous initialize: 404 to 200
    • tools/list served without credentials: no to yes
    • Tools that change things, listed without credentials: 0 to 30
    • Protocol version: none to 2025-06-18
    • RFC 9728 protected resource metadata: none to https://rdiv-production-runtime-production.up.railway.app/.well-known/oauth-protected-resource/mcp
    • Authorization servers: none to https://rdiv-production-runtime-production.up.railway.app
    • Dynamic client registration: not observed to no
    • Client ID metadata documents: not observed to no
  3. PostureRemote posture changed. HTTP status of an anonymous initialize: 200 -> 404; tools/list served without credentials: yes -> no; Tools that change things, listed without credentials: 30 -> 0 (and 5 more).View diff
    • HTTP status of an anonymous initialize: 200 to 404
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 30 to 0
    • Protocol version: 2025-06-18 to none
    • RFC 9728 protected resource metadata: https://rdiv-production-runtime-production.up.railway.app/.well-known/oauth-protected-resource/mcp to none
    • Authorization servers: https://rdiv-production-runtime-production.up.railway.app to none
    • Dynamic client registration: no to not observed
    • Client ID metadata documents: no to not observed

Install

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

claude mcp add --transport http riv https://rdiv-production-runtime-production.up.railway.app/mcp
claude mcp add --transport http riv https://rdiv-production-runtime-production.up.railway.app/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": [
      "mcp__riv__capabilities_list",
      "mcp__riv__pricing_quote",
      "mcp__riv__example_get",
      "mcp__riv__system_status"
    ],
    "ask": [
      "mcp__riv__service_match",
      "mcp__riv__provenance_receipt_trial",
      "mcp__riv__citation_verify",
      "mcp__riv__claim_check",
      "mcp__riv__answer_audit",
      "mcp__riv__contradiction_scan",
      "mcp__riv__evidence_bundle",
      "mcp__riv__provenance_receipt",
      "mcp__riv__dependency_map",
      "mcp__riv__agent_action_verify",
      "mcp__riv__evidence_monitor",
      "mcp__riv__investigation_run",
      "mcp__riv__source_verify",
      "mcp__riv__quote_verify",
      "mcp__riv__number_verify",
      "mcp__riv__source_snapshot",
      "mcp__riv__timeline_reconcile",
      "mcp__riv__fact_extract",
      "mcp__riv__workflow_verify",
      "mcp__riv__transaction_verify",
      "mcp__riv__claim_monitor",
      "mcp__riv__vendor_monitor",
      "mcp__riv__dependency_monitor",
      "mcp__riv__policy_monitor",
      "mcp__riv__agent_monitor",
      "mcp__riv__control_check",
      "mcp__riv__data_flow_verify",
      "mcp__riv__model_change_audit",
      "mcp__riv__vendor_diligence",
      "mcp__riv__procurement_evidence",
      "mcp__riv__ai_use_audit"
    ],
    "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 riv. Review it before you use it.

Capability tags behind 2 rules
  • mcp__riv__source_verify outbound
  • mcp__riv__source_snapshot untrusted-input, outbound

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/io.github.duranivrobert-glitch/riv/verify?hash=d983c504ec842e62e151daf2e8e1a0ac49637248fbe64bfe2a335ed08b4db683" | jq -e '.changed == false'

Pinned hash d983c504ec84, from Nov 19, 2026, 03:18 UTC.

Watch

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

https://radar.anlyon.com/servers/io.github.duranivrobert-glitch/riv/changes.xml

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

Badge

Anlyon Radar badge for io.github.duranivrobert-glitch/riv
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.duranivrobert-glitch/riv.svg)](https://radar.anlyon.com/servers/io.github.duranivrobert-glitch/riv)

Source: MCP Registry · repository. Synced Nov 19, 2026, 04:17 UTC.

R/IV — Verify Claims, Citations & Agent Actions MCP server: questions and answers

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

Is the R/IV — Verify Claims, Citations & Agent Actions MCP server safe?

No scan can promise that. What its definitions show: 35 tools, 30 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 R/IV — Verify Claims, Citations & Agent Actions MCP server delete data?

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

Can the R/IV — Verify Claims, Citations & Agent Actions 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 R/IV — Verify Claims, Citations & Agent Actions MCP server have?

35 tools: 30 write, 5 read. service.match, provenance.receipt.trial, citation.verify, claim.check, answer.audit, contradiction.scan, evidence.bundle, provenance.receipt and 27 more.

Does the R/IV — Verify Claims, Citations & Agent Actions MCP server need sign-in or OAuth?

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

Does the R/IV — Verify Claims, Citations & Agent Actions 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): source.verify and source.snapshot.

Has the R/IV — Verify Claims, Citations & Agent Actions MCP server changed its tools?

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