AgentIndex

Name: AgentIndex
Author: cognivis

by cognivisversion 0.2.0i★ –iRuns in the cloud

Registry nameio.github.cognivis/agentindex

Install

Overview

Description from the maker (original English)

Trust scores and on-chain payment receipts for x402 services.

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 in the cloud
Transport: Streamable HTTP
Category: Online shops & payments

Install

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

Before you install

Basic checks: 1 of 1 passed
Runs on the maker’s server: what you ask it goes through their server.
The registry lists no key to fill in.

You need

Runs in the cloudNothing to install; it connects over the internet

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

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

Works in Claude on the web, desktop and mobile:

Open Settings → Connectors
Press Add custom connector
Paste the address below and press Add
If it asks you to sign in, sign in with the maker

https://mcp-agentindex.craftyour.site/mcp

Run this in your terminal

claude mcp add --transport http agentindex https://mcp-agentindex.craftyour.site/mcp

Open in Cursor

Or copy the settings yourself

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

{
  "mcpServers": {
    "agentindex": {
      "url": "https://mcp-agentindex.craftyour.site/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": {
    "agentindex": {
      "type": "http",
      "url": "https://mcp-agentindex.craftyour.site/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.

ChatGPT connects only to servers on the internet:

Open ChatGPT on the web → Settings → Connectors (Apps)
Press Create or Add (some plans need Developer mode under Advanced first)
Paste the address below, give it a name and save
If it asks you to sign in, sign in with the maker

https://mcp-agentindex.craftyour.site/mcp

Menu names can differ slightly by plan and over time.

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

We have not read this server’s tool list yet; we check endpoints in rotation.

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 cognivis, 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 checked yet
Endpoint responds
Not checked yet; we check endpoints in rotation
… Not checked yet
Sign-in with OAuth
Not checked yet; we check endpoints in rotation
… Not checked yet
No hidden instructions in tool descriptions
Not checked yet; we read the tool list when we check the endpoint

Compared with others in Online shops & paymentsi

More stars than 0% of the other 1754 servers in this category
Published to the registry more recently than 39% of the other 1754 servers in this category
Basic checks equal to or better than 100% of the other 1754 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 AgentIndex 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 in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.2.0) reached the registry 2 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.

What can I use instead?

In the same category: Spree Commerce: open-source B2B and marketplace ecommerce, Stripe MCP, MCP Cn Commerce

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

Spree Commerce: open-source B2B and marketplace ecommerce

by spree

Open-source B2B and marketplace ecommerce; new stores include an MCP server for AI agents.

Runs in the cloud★ 15,812BSD-3-ClauseUpdated 7 days ago

Install

Stripe MCP

by stripe

Stripe’s official server lets AI view and manage customers, products, payments and invoices. Connect to Stripe’s cloud and sign in with OAuth.

Runs in the cloud★ 2,043MITUpdated 12 months ago

Install

MCP Cn Commerce

by TonyWang-hub

8 read-only MCP platform entries; support is operation-specific; merchant live acceptance pending

Runs on your computer★ 96MITUpdated 28 days ago

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.

AgentIndex

AgentIndex shows AI agents which paid services are honest and which scam, with proof on-chain.

Live app · Demo video · Evidence · MCP server · Subgraph

AI agents can now discover an API and pay it automatically over x402. The payment receipt proves that money moved, but it does not prove that the API returned complete or correct data.

AgentIndex fills that gap. It pays x402 services like a normal customer, checks what they return, and publishes a trust score that another agent can inspect before spending money.

Trust from receipts, not reviews.

Ask the index who to pay before the agent spends.

The problem

Imagine an agent needs weather data and finds two paid APIs:

weatherpro costs a little more and reliably returns the fields it promises.
scamco is cheaper, accepts payment, and often returns empty or incomplete data.

A directory can show that both services exist. Usage counts can show which one is popular. Neither tells the agent whether the response is actually trustworthy.

AgentIndex makes the request itself, pays the service, checks the response against the service's published promise, and keeps the payment and verification evidence. The agent can then choose weatherpro and avoid scamco for a reason it can verify.

How it works

flowchart LR

A[Service registers ENSv2 subname + manifest] --> B[Prober discovers service] B --> C[Real x402 payment Hedera or Base] C --> D[Response verification spec + oracle + consensus] D --> E[Verdict attested on Sepolia] E --> F[The Graph subgraph builds trust score] F --> G[Agent checks trust through MCP or API]

A provider registers a subname under agentindex.eth and stores its endpoint, price, method, and response specification in ENS text records.
The prober reads that manifest directly from ENS and calls the service like a normal customer.
It pays the x402 request with real HBAR on Hedera testnet. Approved external probes can use tightly capped USDC on Base.
It checks delivery, required response fields, latency, and—when the answer is objective—accuracy against The Graph Token API and peer consensus.
The result is attested on Sepolia and indexed by the AgentIndex subgraph.
An AI agent queries the trust score and evidence through MCP before choosing which service to pay.

The live site explains each step and links to its on-chain proof.

Why these protocols matter

AgentIndex works like a credit bureau for paid APIs. Each sponsor provides a part that the system cannot work without.

Need	AgentIndex implementation	Protocol
A stable identity for every service	ENSv2 subnames and service-owned manifests	ENS
A payment history based on real behavior	Spend-capped HBAR payments over x402	Hedera
A live record that agents can query	Token API verification, a subgraph, MCP, and an agent SKILL	The Graph

The Graph

AgentIndex uses two Graph products in the same trust-checking flow.

For objective price APIs, the prober compares the paid response with live market data from The Graph Token API. A response can match the expected JSON format and still be dishonest; the oracle check catches prices that look valid but are wrong.

The verdict is then written on-chain. Our deployed subgraph indexes service registrations and probe attestations, excludes invalid auditor-input records, and calculates delivery, honesty, average latency, and a final trust score. The MCP server uses those indexed results to tell an agent who to pay and why.

This is not a dashboard-only integration:

The Token API is the independent input used to judge objective answers.
The subgraph is the live ledger that turns probe history into trust scores.
The MCP server and SKILL.md make those scores reusable by other agents.
Every MCP response includes the subgraph deployment and indexed-block freshness metadata.

Relevant code:

Token API oracle and price comparison
Subgraph trust-score calculation
Subgraph query and freshness metadata
Reusable agent workflow

Hedera

Hedera is the main payment rail for the seeded index. The autonomous prober pays all six services with real HBAR on Hedera testnet through the Blocky402 facilitator before it rates their responses.

The payment flow is built with fund safety in mind:

Only HBAR is allowed for the seeded-service payment path.
Every payment is capped at 1 HBAR.
The payer and receiver are separate Hedera accounts.
Payment references are stored with the probe evidence and linked to HashScan.
The same x402 flow also protects AgentIndex's trust API, so AgentIndex acts as both a buyer and seller of machine-readable services.

Relevant code:

Hedera signer, x402 client, asset allowlist, and payment cap
Hedera x402 paywall for the seeded services
x402-gated trust API

ENS

ENSv2 is the actual service registry, not just a display name. Every rated provider receives a revocable subname under agentindex.eth, such as weatherpro.agentindex.eth.

Each service publishes its manifest through ENS text records:

url
description
x402:method
x402:price
x402:spec

The prober reads these records before making a payment, so the endpoint and the promise being checked come from ENS rather than a private application database. ENSv2 permissions let each provider manage only its own records, while AgentIndex keeps the ability to revoke a subname when a service is caught taking payment and returning bad data.

Relevant code:

ENSv2 subname registration, permissions, renewal, and revocation
Live ENS manifest reader
Permissioned resolver deployment

Verification model

AgentIndex applies the strongest check that makes sense for each type of service.

Check	What it answers	Applies to
Delivery	Did the service return a non-empty JSON response?	Every service
Spec match	Did it return every field promised in its ENS manifest?	Every service
Oracle check	Does an objective value agree with The Graph Token API?	Price services
Consensus	Is the value an outlier compared with other providers?	Comparable services
Track record	How has the service behaved across many paid probes?	Every service

The trust score is calculated in basis points:

trust = 0.60 × delivery + 0.25 × honesty + 0.15 × latency

For subjective output such as summaries, AgentIndex does not claim to prove that the answer is “good.” It reports delivery, compliance with the published format, latency, and historical behavior. Objective data receives the additional oracle and consensus checks.

Live proof

The project includes a real paid probe against an external x402 provider, not only services created for the demo.

Provider: TickersFeed
Payment: $0.002 USDC on Base mainnet
Verification: returned BTC price checked against The Graph Token API and peer consensus
Outcome: passed the configured 2% oracle tolerance
Base payment: view on BaseScan
Sepolia attestation: view on Etherscan

Earlier probes that used an incorrect request path remain visible as valid=false. They are kept for auditability but excluded from the provider's score, so an auditor mistake does not unfairly damage a service.

The evidence dashboard is backed by the live subgraph, not a static dataset.

Seeded services

The six seeded services are a controlled teaching set used to demonstrate different trust signals.

Service	Category	Behavior	What it demonstrates
`weatherpro`	Weather	Honest and fast	A service the agent should pay
`scamco`	Weather	Takes payment but returns bad data	A service the agent should avoid
`pricefeed`	Token prices	Honest and backed by live Graph data	Oracle verification
`summarize`	Summaries	Honest but slow	Latency affects trust
`geocode`	Geocoding	Honest but occasionally unavailable	Reliability without false fraud claims
`newsfeed`	Headlines	Honest	Another service category

scamco is intentionally planted. It lets us demonstrate detection without accusing an unrelated real service of fraud.

Use AgentIndex through MCP

The public MCP server exposes four tools:

Tool	Purpose
`find_service`	Find and rank services for a need
`check_trust`	Inspect one service's trust report
`resolve_data_need`	Decide who to pay or avoid and explain why
`get_verified_data`	Fetch data from the best provider with its score and latest proof

Install the remote server in an MCP-compatible client:

npx add-mcp https://mcp-agentindex.craftyour.site/mcp

Registry name: io.github.cognivis/agentindex
Transport: stateless Streamable HTTP
Discovery manifest: https://mcp-agentindex.craftyour.site/.well-known/mcp.json

A real MCP session recommends weatherpro, rejects scamco, and explains the decision with indexed evidence.

Run locally

Requirements

Node.js 22 or newer
pnpm
Foundry for the Solidity contracts

Install

corepack enable

pnpm install cp .env.example .env

Fill in only the environment variables needed for the component you want to run. Never commit .env or private keys.

Safe local mode

Set PAYWALL=off in .env to test without making payments. Run each component in its own terminal:

pnpm services

pnpm web pnpm --filter @agentindex/mcp http

Run one non-looping probe round:

PAYWALL=off pnpm --filter @agentindex/prober run once

External Base payments are disabled by default. They require an explicit one-shot run, an approved provider, canonical Base USDC, and the configured round and daily budgets. See the prober guide before enabling them.

Test

pnpm test

Individual TypeScript packages can be checked with:

pnpm --filter @agentindex/services run typecheck

pnpm --filter @agentindex/prober run typecheck pnpm --filter @agentinde

Only the beginning is shown; read the rest in the repo

AgentIndex

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 Online shops & paymentsi

Common questions

Alternatives

Spree Commerce: open-source B2B and marketplace ecommerce

Stripe MCP

MCP Cn Commerce

README from the maker

The problem

How it works

Why these protocols matter

The Graph

Hedera

ENS

Verification model

Live proof

Seeded services

Use AgentIndex through MCP

Run locally

Requirements

Install

Safe local mode

Test