Arkova Verification

io.github.carson-seePublished by GitHub account carson-seev1.0.1Updated Oct 24, 2026

Privacy-first document verification anchored to the public ledger.

VerifiedStreamable HTTPWeb executableSecurity & Monitoring

Overview

AI-generated overview

Remote MCP endpoint for Arkova, a privacy-first document verification service that anchors documents to a public ledger.

What you can do
  • The manifest lists no tools, so capabilities are inferred from the description only.
  • It presents Arkova document verification, which anchors documents to a public ledger, to the assistant.
  • It is a hosted remote endpoint rather than a local package, so the assistant connects to it directly.
  • No tool names, inputs or outputs are documented, so what the assistant can actually do is unclear.
When to use it
Consider it if you want an assistant to work with Arkova's document verification and ledger anchoring, for example checking or registering documents through a hosted service. Because no tools are documented, confirm the available operations before relying on it.
Requirements
A remote streamable HTTP endpoint at edge.arkova.ai; nothing to install locally. An Arkova account and an API key supplied in the X-API-Key header, obtainable from the Arkova developer settings. OAuth is declared as required authentication. Network access to the endpoint.
Before you install
The server requires an API key in the X-API-Key header, so treat it as a secret and avoid exposing it in logs or shared configs. Documents submitted for verification are sent to a third-party service and anchored to a public ledger, which may make their existence or hashes publicly visible; check what the service publishes before uploading sensitive material. No tools are documented, so write or delete behaviour cannot be confirmed in advance.

Installation

In SourceWeft

  1. Open Arkova Verification in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.carson-see%2Farkova-verification/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "arkova-verification": {
      "type": "http",
      "url": "https://edge.arkova.ai/mcp"
    }
  }
}

README

This repository has no README.

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.1LatestSep 16, 2026

Score

60% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.