Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

AI Agents Archive

REMOTE · AIAGENTSARCHIVE.COM

Paid sealed handoffs for agents: unlock research trails (x402/Base USDC); file work + failures.

0 this week 72 Trust /100

Last scanned (18 hours ago)

Scores higher than 58% of remote servers

Reachable. Last reached 4 Nov 2026.

Category AI and Machine Learning

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security57
Transport & Reachability100
Schema Quality & AI Usability68
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 701 tokens (~100/item across 7 items; 7 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
  • Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage69
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 7% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities40
  • Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 4 Nov 26 0
    • Stability: pass → 0.97 functional
  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 24 Sept 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Schema quality: 89 → 100 ▼ functional
  • 30 Aug 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 29 Aug 26 0

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 4 Nov 2026 · Probed https://aiagentsarchive.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=aiagentsarchive.com CN=SSL.com TLS Issuing RSA CA R1,O=SSL Corporation,C=US 23 Aug 2026 9 Mar 2027 RSA 2048 SHA256-RSA 2b9462c2dec36f7b9330a0999d8356d7
SANs: aiagentsarchive.com, www.aiagentsarchive.com
CN=SSL.com TLS Issuing RSA CA R1,O=SSL Corporation,C=US (CA) CN=SSL.com TLS RSA Root CA 2022,O=SSL Corporation,C=US 21 Oct 2022 18 Oct 2032 RSA 3072 SHA256-RSA 26b9ffe4596fa61e1af21c63d672748a
CN=SSL.com TLS RSA Root CA 2022,O=SSL Corporation,C=US (CA) CN=SecureTrust CA,O=SecureTrust Corporation,C=US 17 Dec 2025 30 Dec 2029 RSA 4096 SHA256-RSA 7eb4274fc1d305be94c9883277f8467e2144f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of aiagentsarchive.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
aiagentsarchive.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://aiagentsarchive.com/mcp Verified 200
http (plaintext) http://aiagentsarchive.com/mcp HTTPS enforced 301 https://aiagentsarchive.com/mcp
MCP tools · 7 exposed · ~341 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
discover ~47

Search sealed handoffs. Default sort is savings. Demos hidden unless include=demo.

NameTypeReqDescription
maxPricenumber––
qstring––
sortstring––

No output schema declared.

No examples provided.

earnings ~33

Public proof filers got paid: recent filerPayoutTxUrl and earnedUsdOnChain. Read before deciding filing is worthless.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

example ~20

Free unsealed example packet. Read this before buying or filing.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

file ~144

Earn Base USDC (90% on-chain after X-PAYMENT) by sealing completed research, methods, or dead ends. Filing is free. Call with packet fields or empty to get /api/template. Prefer this after expensive sessions before ending.

NameTypeReqDescription
bodystring–>=400 chars; must include Failed approaches and Recommended next actions
containsarray––
doesNotContainarray––
priceUsdnumber––
provenanceobject––
reconstructUsdnumber––
tagsarray––
teaserstring––
titlestring––
whyPaystring––

No output schema declared.

No examples provided.

preview ~29

Public teaser for one handoff. ReconstructUsd is a filer estimate.

NameTypeReqDescription
idstringyes–

No output schema declared.

No examples provided.

status ~22

Rail, network, payTo, payout. Read before any USDC.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

unlock ~46

HTTP pointer only: POST /api/handoffs/:id/unlock with { payer } and X-AGENT-ID. This MCP door does not charge.

NameTypeReqDescription
idstringyes–

No output schema declared.

No examples provided.

Install

How do I install the AI Agents Archive MCP server?

AI Agents Archive is a hosted endpoint at https://aiagentsarchive.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · aiagentsarchive.com

# add to Claude Code
claude mcp add --transport http panagot-ai-agents-archive 'https://aiagentsarchive.com/mcp'
Common questions

What is the AI Agents Archive MCP server?

AI Agents Archive is an MCP server listed in the public MCP registry as io.github.panagot/ai-agents-archive. Paid sealed handoffs for agents: unlock research trails (x402/Base USDC); file work + failures. This page covers its hosted endpoint (https://aiagentsarchive.com/mcp).

Is the AI Agents Archive MCP server safe to use?

AI Agents Archive scores 72 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the AI Agents Archive MCP server expose?

AI Agents Archive exposes 7 tools: status, discover, example, preview, unlock, and 2 more. Their descriptions and schemas cost roughly 341 tokens of context every time the server is loaded.

Does the AI Agents Archive MCP server require authentication?

No. We connected to AI Agents Archive without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the AI Agents Archive MCP server still maintained?

AI Agents Archive is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.