Skip to main content
Glama

Server Details

We buy from x402 endpoints with real USDC and publish delivery outcomes. Check before you spend.

Ownership verified
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
Repository
jalcodev/nohumans-mcp
GitHub Stars
0
Server Listing
nohumans-mcp
ChatGPT
–
Claude
–

TDQS

A4.1/5.0

Scored across 4 tools

Disambiguation4/5

Each tool occupies a distinct step: keyword search, lookup by listing id, lookup by endpoint URL, and demand analytics. The only mild overlap is that resolve_endpoint returns the full listing record for 'active' matches, which duplicates get_service_details output, but the different input and pre-payment framing keep them distinguishable.

Naming Consistency3/5

Three tools follow a verb_noun pattern (find_paid_service, get_service_details, resolve_endpoint) while the fourth is a full question phrase (what_agents_are_asking_for). All snake_case and readable, but the conventions are visibly mixed.

Tool Count4/5

Four read-only tools is lean but each covers a real step in the buyer workflow (search, inspect, verify URL, gauge demand). No filler tools, though the surface is thin enough that it borders on minimal for a directory service.

Completeness4/5

The buyer path of find -> inspect -> verify endpoint is fully covered, plus demand signal. Gaps exist on the supply side: no tool to submit or manage a listing despite what_agents_are_asking_for being framed for builders/sellers, and find_paid_service documents no pagination unlike the analytics tool.

Publisher details

Operator
nohumans.directory · Publisher source
Vendor relationship
First-party · Publisher source
Privacy policy
Not provided
Trust center
Not applicable
Restrictions
None for the MCP server. No account, no API key, no OAuth app, no paid plan, no admin approval, no regional restriction. All four tools are read-only and open; the full catalogue, the CC-BY export and the change feed are unauthenticated. Two HTTP routes elsewhere on the API are paid over x402 on Base — a per-listing verdict and seller-requested verification — and neither is reachable through, or required by, this server. Rate limits apply to writes (submissions), not to reads. · Publisher source

Available Tools

4 tools
find_paid_serviceFind a paid serviceA
Read-onlyIdempotent
Inspect

Search paid x402 APIs and datasets by need. Ranked: verified first, then probe score, then price. Each result carries what you choose on: status, score (0..1), evidence_tier, paid_verified (we bought it with real USDC and it delivered), latest_purchase_delivered (false = our most recent paid purchase took real USDC and did not deliver: do not pay it), has_sample (a cheap preview exists), price. Relevance comes from the query text; a specific need in plain words matches best. Zero results means nothing listed matches. Results are dated evidence, not guarantees. Returns a summary per listing; detail='full' returns every field. Free, read-only.

Inputs: limit, query, detail, category, +4 more. Returns: count, detail, results, category_expanded

get_service_detailsGet a paid service's full recordA
Read-onlyIdempotent
Inspect

Full record for one listing id: request and response schemas, sample_query, observed 402 terms (network, payTo, scheme, x402 version), reputation detail, and paid_verification (our latest real USDC purchase, with its settlement tx where proven). Useful before paying: it shows the exact request shape and current reliability. Every timestamp has an _iso twin; on-chain counts describe the seller's wallet, usually shared by several listings, not this endpoint. Free, read-only.

Inputs: id (required). Returns: id, kind, name, score, +53 more

resolve_endpointCheck an endpoint URL before payingA
Read-onlyIdempotent
Inspect

Check an endpoint URL you already hold before paying it. Returns match 'active' with the listing's full record, 'delisted' (listed here, later removed), or 'unknown' (never checked here; absence is not a verdict either way). The record is dated evidence, not a safety rating. Free, read-only.

Inputs: url (required). Returns: note, match, detail

what_agents_are_asking_forWhat agents are asking forA
Read-onlyIdempotent
Inspect

What agents searched this directory for, for deciding which x402 service to build or list. Terms ranked by how many distinct days they were asked, each with catalogue_top: the listings our own search already returns for it. A term being asked does not mean nothing serves it. The window ends live, rebuilt hourly (no delay since 2026-11-08; delay_hours and window_ends_at in the response say so); test traffic, sellers searching their own listings and identifying terms are excluded; floor: a term appears once at least 1 distinct non-seller client IP asked it. Client counts are IP ceilings, never buyer counts. Paged: limit (default 25), offset, next_offset. Free, read-only.

Inputs: limit, offset. Returns: note, page, top_needs, read_first, +11 more

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.