Talandor
Rapport de connecteur

nohumans.directory

https://api.nohumans.directory/mcp

Registre officiel

Registre officiel · directory.nohumans/registry · Espace de l’éditeur : directory.nohumans

Serveur vérifié aujourd’hui à 21:31 UTC

Catalogue affiché : dernière observation complète du 22 septembre

4 outils publics observés. Outils non exécutés. Ces outils viennent de l’observation de catalogue ci-dessus, pas du dernier contrôle de disponibilité.

Serveur accessible

Qu’a observé Talandor ?

Le serveur a répondu

Ajoutez l’adresse à votre assistant à l’aide de la configuration ci-dessous. Un Watch peut vous prévenir si ce catalogue public change.

Contrôle public du protocole et de tools/list, pas une validation fonctionnelle.

https://api.nohumans.directory/mcp
DisponibilitéServeur accessiblemesuré
Outils4 outils publics observésmesuré
Test de l’assistantNon testé par Talandorinconnu
Changement récentfind_paid_service restricted the allowed values for categoryHistorique

Configurer votre assistant · Détails du contrôle

Configuration pour votre assistant

Talandor contrôle le serveur ; il ne le connecte pas à votre assistant.

Choisissez votre assistant, puis copiez la configuration affichée. L’authentification se fait chez le fournisseur du connecteur, jamais dans Talandor.

    Ouvrir le guide officiel (nouvel onglet)
    Détails du contrôle

    Ce qui a changé

    Public contract stable since
    Last check · No semantic contract change since the previous complete snapshot.
    Info
    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 alert only if this change may affect uses of the selected client that depend on the changed tools.

    Cette frise publique montre le dernier contrôle, les 24 dernières heures et le dernier changement important. Watch conserverait 30 jours.

    Les notes ci-dessus concernent ce connecteur.

    Contenu fourni par le serveur. Les noms, descriptions et schémas ci-dessous sont copiés du serveur MCP. Ils peuvent être dans une autre langue. Talandor ne les traduit pas et ne les vérifie pas.
    Outils et exposition déclarée

    Les annotations du serveur sont des déclarations, pas un comportement vérifié.

    Afficher 4 définitions d’outils fournies par le serveur sur 4
    find_paid_service
    Déclaré en lecture seule
    Afficher les détails fournis par le serveur
    Description du serveur (copiée ; langue non vérifiée)
    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.
    Schéma d’entrée (aperçu fourni par le serveur — ne pas copier)
    {
      "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
    Déclaré en lecture seule
    Afficher les détails fournis par le serveur
    Description du serveur (copiée ; langue non vérifiée)
    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.
    Schéma d’entrée (aperçu fourni par le serveur — ne pas copier)
    {
      "type": "object",
      "required": [
        "id"
      ],
      "properties": {
        "id": {
          "type": "string",
          "description": "Listing id, as returned by find_paid_service."
        }
      }
    }
    resolve_endpoint
    Déclaré en lecture seule
    Afficher les détails fournis par le serveur
    Description du serveur (copiée ; langue non vérifiée)
    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.
    Schéma d’entrée (aperçu fourni par le serveur — ne pas copier)
    {
      "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
    Déclaré en lecture seule
    Afficher les détails fournis par le serveur
    Description du serveur (copiée ; langue non vérifiée)
    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.
    Schéma d’entrée (aperçu fourni par le serveur — ne pas copier)
    {
      "type": "object",
      "required": [],
      "properties": {},
      "additionalProperties": false
    }
    Preuves et limites

    Méthode : sonde HTTP anonyme. Aucun outil n’est exécuté.

    Protocoles essayés : 2026-07-28, 2025-11-25

    Protocole2025-11-25
    TransportHTTP Streamable
    AuthentificationAucun défi d’authentification observé
    PreuvesContrat public observé
    Latence totale4099 ms
    Octets de réponse12705

    Aucune erreur de diagnostic.

    Historique des observations
    Serveur accessible
    · stable depuis
    2025-11-25 · 4 outils · aucun changement · 3 contrôles
    Impossible de conclure
    Aucun protocole
    Impossible de conclure
    Aucun protocole
    Impossible de conclure
    Aucun protocole
    Impossible de conclure
    Aucun protocole
    Impossible de conclure
    Aucun protocole
    Impossible de conclure
    Aucun protocole
    Impossible de conclure
    Aucun protocole
    Impossible de conclure
    Aucun protocole
    Serveur accessible
    · stable depuis
    2025-11-25 · 4 outils · aucun changement · 20 contrôles
    Impossible de conclure
    Aucun protocole
    Impossible de conclure
    Aucun protocole
    Impossible de conclure
    Aucun protocole
    Serveur accessible
    2025-11-25 · 4 outils
    Serveur accessible
    · stable depuis
    2025-11-25 · 4 outils · aucun changement · 2 contrôles
    Impossible de conclure
    Aucun protocole
    Impossible de conclure
    Aucun protocole
    Impossible de conclure
    Aucun protocole
    Impossible de conclure
    Aucun protocole
    Impossible de conclure
    Aucun protocole
    Serveur accessible
    2025-11-25 · 4 outils
    Impossible de conclure
    Aucun protocole
    Impossible de conclure
    Aucun protocole
    Impossible de conclure
    Aucun protocole
    Impossible de conclure
    Aucun protocole
    Impossible de conclure
    Aucun protocole
    Impossible de conclure
    Aucun protocole
    Impossible de conclure
    Aucun protocole
    Impossible de conclure
    Aucun protocole
    Impossible de conclure
    Aucun protocole
    Contrat public complet · 2025-11-25 · 4 outils
    1aad8f45bd30
    Contrat public complet · 2025-11-25 · 4 outils
    0939962e1c71
    Contrat public complet · 2025-11-25 · 4 outils
    bcac5b80b997
    Contrat public complet · 2025-11-25 · 4 outils
    17487cd7c47f

    Éligibilité à la surveillance approfondie

    Éligible à la surveillance approfondie

    Un contrat public tools/list complet a été observé ; une future base de surveillance approfondie pourra être comparée en toute sécurité.

    Un Watch démarre depuis la section de paiement de cette page, et seulement après un paiement vérifié.

    Voir la surveillance publique
    Watch · recurring plan

    Watch this MCP

    Your agent depends on this MCP. When Watch is active, periodic checks alert you when we observe a change that may affect the client you selected.

    • Know when it goes downWhen Watch is active, availability is observed about every 5 minutes. An outage is confirmed after two failed checks, so a single miss is not treated as a lasting outage.
    • Know when its contract changesDeep checks about every hour compare public tool catalogs and authentication surfaces over time.
    • Know what changed and what to fixAn alert names the observed change and the next step for the client you selected.

    Full public-contract coverage: Availability, protocol, auth and public tool contract changes can be compared.

    Full WatchAvailability, protocol, auth and public tool contract changes
    Surface WatchAvailability, TLS, protocol and auth surface — no private tool diff

    Early access currently activates this first endpoint; adding more endpoints up to the planned limit of five is not open in this deployment. Live checkout is open. A Watch activates only after a verified payment event; a browser return never starts monitoring.

    Start Watch