Verify MCP (AgentBook verification)

Name: Verify MCP (AgentBook verification)
Author: niclydon

by niclydonversion 0.2.1i★ –iRuns on your computer

Registry nameio.github.niclydon/verify-mcp

Install

Overview

Description from the maker (original English)

Verify AgentBook registration and operator attestations for agent wallets on World Chain.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Other

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
The registry lists no key to fill in.

You need

npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "verify": {
      "command": "npx",
      "args": [
        "-y",
        "@fiador/verify-mcp"
      ]
    }
  }
}

Run this in your terminal

claude mcp add verify -- npx -y @fiador/verify-mcp

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "verify": {
      "command": "npx",
      "args": [
        "-y",
        "@fiador/verify-mcp"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "verify": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@fiador/verify-mcp"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account niclydon, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Otheri

More stars than 0% of the other 18329 servers in this category
Published to the registry more recently than 78% of the other 18329 servers in this category
Basic checks equal to or better than 100% of the other 18329 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Verify MCP (AgentBook verification) safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.2.1) reached the registry 11 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, Excaliself

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago

Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated 2 days ago

Install

Excaliself

by maciekzygmunt

Find, read, create, edit, and organize Excalidraw drawings in your self-hosted Excaliself instance.

Runs in the cloudUpdated today

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

Fiador — human-backed attestation for Discord bots

This is independent open source. It is not affiliated with or endorsed by World, Worldcoin, or Tools for Humanity; "World ID" and "AgentKit" name the systems this software interoperates with.

A Discord bot's profile tells you a name and an avatar, but little about the person who operates it. Fiador is an open protocol for checking a signed claim from a wallet registered by a unique, verified human using World ID and AgentBook on World Chain. The claim names a Discord application. Current Fiador code cannot prove that the wallet holder controls that application.

The verifier establishes that a unique human registered the wallet that signed the attestation. It does not prove application control. It also does not prove that the human wrote any particular message, endorses any particular output, or controls the bot at this moment. Those limits are part of the design, stated everywhere the badge appears, because a trust mark that overstates itself is worse than none.

Fiador has no token, will not issue one, and is not launching an asset. Verification is never something to buy or speculate on. Any token claiming the Fiador name is unaffiliated with this project.

How it works

The operator registers an agent wallet in AgentBook with their Orb-verified World ID, then signs an attestation binding their Discord application ID and bot user ID to that wallet. The attestation carries an expiry (90 days maximum), a nonce, and a hash of the human identifier, never the identifier itself.
The attestation is published at a URL and listed in a public registry mapping Discord application IDs to attestation URLs.
The self-hosted verifier bot and the locally built static verify page check the signature, expiry, and wallet registration. They display the operator claim with an application-control warning. The verifier bot does not grant or revoke the server's Human-backed role.

Verification is a live check at verification time, not a permanent stamp: the badge assets in this repo render verified, expired, and unverified states, in light and dark variants, because an honest mark has to be able to say "no longer true."

Privacy rules

Attestations publish the signing wallet's full address and a hash of the human identifier, never the raw identifier. Fiador verifiers read the on-chain value for a check. Their default public results omit it; trusted local callers can explicitly request a raw internal result, which must never be published. AgentBook lookup and registration events are public. A disclosed registered wallet or this published hash can be matched against that finite public data to reveal the pseudonymous identifier and other wallets registered to it. Two bots backed by the same human also publish the same hash.
An optional operator display name exists for operators who want to be named. It is off by default and never required.
This repository does not contain live private keys or service tokens. Test signing keys and test identifiers are synthetic. The founding public attestation intentionally includes a dedicated wallet address, a human-identifier hash, and an operator display name.

Status

Founding stage; status checked October 27, 2026. The protocol specification is written (docs/SPEC.md). This repository contains:

The full protocol spec, including the verification order, the discovery model (registry plus install-time claim), and the honest limits of the proof
The badge asset set (verified / expired / unverified, pill and icon, light and dark) under assets/, with a dynamic served-badge design so the mark can reflect a live check
The verify package, self-hosted Discord verifier bot, static verify page (/verify/), and registry source. The browser page has local tests and a protected preview route check. A local browser check fetched the public attestation and read World Chain successfully on October 26. The bot's role automation is disabled pending trusted proof of Discord application control.
Root Vercel preview packaging for the site, browser page, registry, attestation, and /v/ link previews (runbook). Local route checks and a protected preview smoke pass are recorded. fiador.org serves the site, public registry, founding attestation, privacy page, and support page. The production /verify/ and /v/ routes still return 404. A production browser check, Discord unfurl, and application-control witness remain unverified.
A tested AgentKit free-trial integration in a private prototype, verified end to end against AgentBook with a real Orb-verified registration (October 25, 2026).

The live privacy and support pages also describe a separate owner-only Slack trial. As of October 27, owner enrollment, Slack sign-in, and a World ID check have not run live. The available source, local tests, and protected previews do not establish a production verifier or Discord application control. Guild admins upgrading the verifier bot must manually audit existing Human-backed role holders; stored legacy claims do not prove application control, and the bot changes no roles.

Design decisions already settled

Self-hosted verifier for v1: every adopting server runs its own verifier with its own bot token. No central hosted bot holds role-granting power across servers.
The verify code ships as a clearly separated package inside this repo first, designed for extraction when a second project needs it.
Apache-2.0 throughout, so the protocol can be adopted without encumbrance.

The wider program

Fiador is the first public project in a small program exploring what becomes possible when agents can prove a unique human stands behind them: presence-approved actions for personal agent fleets, provenance seals for agent-written content, and callback verification for agent assistants that deal with businesses on a human's behalf. Those projects will appear as their own repositories under the same author, built in the open with the same rules: spec first, tests including the failure cases, live verification evidence recorded, and a narrative entry for every arc.

The founding narrative is at docs/narrative/2026-10-25-founding.md.

Verify MCP (AgentBook verification)

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Otheri

Common questions

Alternatives

Spec Driven Development

Remote Desktop Commander

Excaliself

README from the maker

Fiador — human-backed attestation for Discord bots

How it works

Privacy rules

Status

Design decisions already settled

The wider program