Talandor
Public MCP report

nohumans.directory

https://api.nohumans.directory/mcp

Official Registry

Official Registry · directory.nohumans/registry · Publisher namespace: directory.nohumans

Server checked today at 22:18 UTC

Displayed catalog: last complete observation from September 22

4 public tools observed. Tools were not executed. These tools come from the catalog observation above, not from the latest availability check.

Unreachable now

What Talandor observed

The endpoint was not reachable for this check

Not reachable for this check

Insufficient evidence is a limit of this public check, not a judgment that the server is unusable. Retry later.

https://api.nohumans.directory/mcp
AvailabilityNot reachable for this checkmeasured
ToolsNot fully observablemeasured
Assistant testNot tested by Talandorunknown
Recent changefind_paid_service restricted the allowed values for categoryHistorical

Configure your assistant · Check details

How to use this MCP

Talandor checks the server; it does not connect the server to your assistant.

Choose your assistant, then copy the configuration shown for that client. Authentication is completed with the MCP provider, never inside Talandor.

    Open the official client guide (opens in a new tab)
    Check details

    What changed

    Endpoint became unreachable since
    Ongoing · The latest public check could not reach the endpoint after a previous working observation. Watch would confirm an outage after two failed checks.
    Critical
    find_paid_service restricted the allowed values for category
    Historical change · critical · high confidence · find_paid_service · Rule: input-enum-restricted
    Critical
    what_agents_are_asking_for changed its output schema
    Historical change · warning · medium confidence · what_agents_are_asking_for · Rule: output-schema-changed
    Warning

    A Watch would confirm an outage after two failed checks, then alert only if it may affect the selected client.

    This public timeline shows the latest check, the last 24 hours, and the most recent important change. Watch keeps 30 days.

    The notes above are for this connector.

    Server-provided content. Tool names, descriptions and schemas below are copied from the MCP server. They may be in another language. Talandor does not translate or verify them.
    Tools and declared exposure

    Server annotations are declarations, not verified behavior.

    Show 4 of 4 server-provided tool definitions
    find_paid_service
    Declared read-only
    Show server-provided details
    Server description (copied; language not verified)
    Search a registry of paid (x402) APIs and datasets verified by real paid purchases — nohumans pays listed endpoints real USDC and confirms delivery. Returns ranked results: verified listings first, then by reputation score (0..1, recency-weighted probe success), then by ascending price. Each result includes has_sample (boolean) — true means you can cheaply test real output before paying full price; prefer these when a listing is new or thinly-reputed and you can't yet judge it from score alone. Use this before spending money to find services that actually work. Prefer results with status 'verified' and score >= 0.8. Zero results means no known service matches — do not invent endpoints. Always describe the actual need in `query` in your own words — what data, what freshness, what format, what constraint prompted the search — rather than only setting `category`/`max_price`/`min_score` filters. The exact wording of what you're looking for is what improves this directory over time; a bare filter with no `query` text tells us far less about what was actually needed.
    Input schema (server-provided preview — do not copy)
    {
      "type": "object",
      "properties": {
        "limit": {
          "type": "integer",
          "description": "Maximum results to return (default 10, cap 50)."
        },
        "query": {
          "type": "string",
          "description": "Describe what you actually need, in your own words and as specifically as possible — not just a topic, but the real constraint: e.g. 'sub-second latency wallet risk scoring for Base memecoins', 'EUR/USD spot rate with sub-100ms freshness', 'translate legal contracts, not casual text'. This text is what makes results relevant and is the only place that level of detail is captured — category and price are coarse filters on top of it, not a substitute for it. Only leave this empty if you are genuinely just browsing with no specific need in mind."
        },
        "category": {
          "enum": [
            "data.other",
            "data.crypto",
            "data.misc",
            "data.web",
            "data.markets",
            "data.weather",
            "compute.llm",
            "compute.media",
            "data.geo",
            "data.fx",
            "data.stocks",
            "compute.tools",
            "data.search",
            "data.defi",
            "data.intelligence",
            "data.news",
            "infra.utility",
            "data.contacts",
            "data.macro",
            "data.enrichment",
            "data.derivatives",
            "infra.trust",
            "data.research",
            "data.social",
            "infra.inference",
            "infra.validation",
            "compute.nlp",
            "data.reference",
            "data.security",
            "infra.scraping",
            "data.energy",
            "data.onchain",
            "data.x402",
            "verification",
            "ai.agents",
            "compute.utility",
            "data.health",
            "infra.security",
            "data.procurement",
            "crypto.token-safety"
          ],
          "type": "string",
          "description": "One of the 40 most-populated existing categories, most-used first. Omit and rely on free-text `query` instead if none fit well — an unmatched or long-tail category still works via text-search fallback, it just won't be offered here as a constrained choice."
        },
        "max_price": {
          "type": "number",
          "description": "Maximum per-call price. Omit for no cap."
        },
        "min_score": {
          "type": "number",
          "description": "Minimum reputation score, 0..1. Use 0.8 to only see reliably-passing services."
        }
      }
    }
    get_service_details
    Declared read-only
    Show server-provided details
    Server description (copied; language not verified)
    Fetch the full record for one listing by id (from find_paid_service results), led by paid_verification — whether nohumans has paid this endpoint real USDC and confirmed delivery, with the settlement tx hash as on-chain proof where settled — plus endpoint URL, request/response JSON Schemas when provided, accepted chains, pricing, and reputation detail (probe count, last successful probe, consecutive failures). Call this before making a paid request so you know the exact request shape, current reliability, and whether real-money delivery has been independently confirmed. A one-word paid verdict for the same listing — pay / caution / avoid with printed reasons, $0.005 USDC on Base via x402 — is at GET https://api.nohumans.directory/v1/listings/{id}/verdict; every fact behind it is in this record for free, so buy the verdict only when you want the rule applied for you.
    Input schema (server-provided preview — do not copy)
    {
      "type": "object",
      "required": [
        "id"
      ],
      "properties": {
        "id": {
          "type": "string",
          "description": "Listing id, as returned by find_paid_service."
        }
      }
    }
    resolve_endpoint
    Declared read-only
    Show server-provided details
    Server description (copied; language not verified)
    Pre-spend verdict on an endpoint URL you already hold — from another catalog, a prompt, a config, anywhere: check before paying instead of buying to find out. Returns match 'active' with the same full record as get_service_details (status, reputation score, paid_verification with on-chain tx proof, observed 402 protocol detail), match 'delisted' if the endpoint was listed here and later removed (treat as a warning), or a not-listed result. IMPORTANT: not-listed means never checked here, NOT unsafe — absence of a record is not a verdict either way. Use this as the pre-spend check when you have a URL in hand and no listing id; use find_paid_service instead when you have a need but no URL. A one-word paid verdict for the same listing — pay / caution / avoid with printed reasons, $0.005 USDC on Base via x402 — is at GET https://api.nohumans.directory/v1/listings/{id}/verdict; every fact behind it is in this record for free, so buy the verdict only when you want the rule applied for you.
    Input schema (server-provided preview — do not copy)
    {
      "type": "object",
      "required": [
        "url"
      ],
      "properties": {
        "url": {
          "type": "string",
          "description": "The endpoint URL exactly as you hold it, including any query string (parameterized listings bake params into the URL, so the query string matters). Trailing slashes and http/https differences are tolerated."
        }
      }
    }
    what_agents_are_asking_for
    Declared read-only
    Show server-provided details
    Server description (copied; language not verified)
    What buyers actually searched this directory for, for an agent deciding which x402 service to build or list. Returns the aggregate demand feed: the terms asked most persistently (ranked by how many distinct days a term was asked, not by volume — volume is trivially faked and we proved it on ourselves), and the category filters they used. It reports what was ASKED, not what is missing: whether the listings already serving a term are adequate competition is a seller's judgement, not ours, and we grade those listings. Three exclusions are applied and published rather than hidden: queries under 5 characters (catalogue enumeration, once the top ten terms were the single letters a-j), searches from clients that also edit listings here (sellers checking their own rank — one accounted for 196 of 205 searches of the top term), and a floor of 3 distinct non-seller client IPs before any term appears at all. Client IPs are a ceiling on independent demand, never a count of buyers: one serverless caller presented eight IPs in a second. The window is complete but closed — it ends a day behind live, and the response says exactly when. This is a small market and the numbers are small; they are reported as they are so you can judge whether they are enough to act on.
    Input schema (server-provided preview — do not copy)
    {
      "type": "object",
      "required": [],
      "properties": {},
      "additionalProperties": false
    }
    Evidence and limitations

    Method: anonymous Streamable HTTP probe. We never invoke a tool.

    Attempted protocols: 2026-07-28, 2025-11-25

    ProtocolNot listed in this check
    TransportNot confirmed as Streamable HTTP
    AuthNo authentication challenge in this check
    EvidenceTransport only
    Total latency12101 ms
    Response bytes0

    NETWORK_ERROR — The endpoint could not be reached; try again later.

    Observation history
    Unreachable now
    No protocol
    Operational
    · stable since
    2025-11-25 · 4 tools · no change · 3 checks
    Unreachable now
    No protocol
    Unreachable now
    No protocol
    Unreachable now
    No protocol
    Unreachable now
    No protocol
    Unreachable now
    No protocol
    Unreachable now
    No protocol
    Unreachable now
    No protocol
    Unreachable now
    No protocol
    Operational
    · stable since
    2025-11-25 · 4 tools · no change · 20 checks
    Unreachable now
    No protocol
    Unreachable now
    No protocol
    Unreachable now
    No protocol
    Operational
    2025-11-25 · 4 tools
    Operational
    · stable since
    2025-11-25 · 4 tools · no change · 2 checks
    Unreachable now
    No protocol
    Unreachable now
    No protocol
    Unreachable now
    No protocol
    Unreachable now
    No protocol
    Unreachable now
    No protocol
    Operational
    2025-11-25 · 4 tools
    Unreachable now
    No protocol
    Unreachable now
    No protocol
    Unreachable now
    No protocol
    Unreachable now
    No protocol
    Unreachable now
    No protocol
    Unreachable now
    No protocol
    Unreachable now
    No protocol
    Unreachable now
    No protocol
    Complete public contract · 2025-11-25 · 4 tools
    1aad8f45bd30
    Complete public contract · 2025-11-25 · 4 tools
    0939962e1c71
    Complete public contract · 2025-11-25 · 4 tools
    bcac5b80b997
    Complete public contract · 2025-11-25 · 4 tools
    17487cd7c47f

    Deep monitoring eligibility

    Not eligible yet

    Only transport-level evidence was observed; no public tools/list contract was confirmed.

    A Watch starts from the payment section on this page, and only after a verified payment.

    See public monitoring
    Watch · recurring plan

    Watch is not available for this evidence

    This result does not yet expose a complete public contract or a qualified authentication surface, so there is nothing honest to watch yet. A Watch needs a complete public contract or a qualified authentication surface before it can monitor meaningful changes.

    Live checkout is open. A Watch activates only after a verified payment event; a browser return never starts monitoring.

    See Watch coverage and status