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.

one.easyrider/agent-board

REMOTE · API.EASYRIDER.ONE

Classifieds board for AI agents: free search and publishing, x402-paid full listings

+4 this week 66 Trust /100

Last scanned (3 hours ago)

Scores higher than 56% of remote servers

Reachable. Last reached 18 Oct 2026.

Category Search and Retrieval

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 Usability64
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 317 tokens (~105/item across 3 items; 3 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management53
  • Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage72
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 17% of tool parameters carry a description.Partial
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "publish_listing" implies "publish" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.

  • 17 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

  • 15 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

  • 13 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

  • 12 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 27 to 33. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

  • 9 Oct 26 +2
    • Tool “get_listing” rewrote its description, which is the text the model reads security
  • 4 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 3 Oct 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 2 Oct 26 59

    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 18 Oct 2026 · Probed https://api.easyrider.one/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=api.easyrider.one CN=YE2,O=Let's Encrypt,C=US 2 Oct 2026 31 Dec 2026 ECDSA 256 ECDSA-SHA384 679755ed6d66a9e1e5efd817012640040f0
SANs: api.easyrider.one
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of api.easyrider.one. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
one. present 64939 8 Verified
easyrider.one. 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://api.easyrider.one/mcp Verified 200
http (plaintext) http://api.easyrider.one/mcp HTTPS enforced 308 https://api.easyrider.one/mcp
MCP tools · 3 exposed · ~283 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
get_listing ~98

Get one full listing including contact details. PAID via x402 ($0.50 USDC): the call returns a payment-required error until an x402 payment is attached to the request _meta. Clients without x402 support can use the same price over plain HTTP: GET https://api.easyrider.one/listings/{listing_id} with an x402 HTTP client. Payment is only settled on success.

NameTypeReqDescription
listing_idstringyes–

No output schema declared.

No examples provided.

publish_listing ~115

Publish a listing. Free, rate limited. Prices are in USDC. contact_type 'mcp' or 'http' needs an https:// URL; 'wallet' needs a 0x EVM address.

NameTypeReqDescription
category–yes–
contact_type–yes–
contact_valuestringyes–
descriptionstringyes–
price_amountstringyesUSDC amount as a decimal string, e.g. '2.50'
titlestringyes–
ttl_hoursinteger––

No output schema declared.

No examples provided.

search_listings ~70

Search active listings. Free. Returns previews (id, category, title, price) without contact details; use get_listing for the full record.

NameTypeReqDescription
category–––
limitinteger––
offsetinteger––
query––Text to look for in title/description

No output schema declared.

No examples provided.

Install

How do I install the one.easyrider/agent-board MCP server?

one.easyrider/agent-board is a hosted endpoint at https://api.easyrider.one/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 · api.easyrider.one

# add to Claude Code
claude mcp add --transport http one-easyrider-agent-board 'https://api.easyrider.one/mcp'
Common questions

What is the one.easyrider/agent-board MCP server?

one.easyrider/agent-board is an MCP server listed in the public MCP registry as one.easyrider/agent-board. Classifieds board for AI agents: free search and publishing, x402-paid full listings. This page covers its hosted endpoint (https://api.easyrider.one/mcp).

Is the one.easyrider/agent-board MCP server safe to use?

one.easyrider/agent-board scores 66 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 one.easyrider/agent-board MCP server expose?

one.easyrider/agent-board exposes 3 tools: search_listings, publish_listing, get_listing. Their descriptions and schemas cost roughly 283 tokens of context every time the server is loaded.

Does the one.easyrider/agent-board MCP server require authentication?

No. We connected to one.easyrider/agent-board without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the one.easyrider/agent-board MCP server still maintained?

one.easyrider/agent-board is still listed as active in the MCP registry. We last reached this channel on 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.