com.robinsaige/verifier

Est-ce que com.robinsaige/verifier est sûr ?

Au dernier audit MCP Hub, le serveur MCP « com.robinsaige/verifier » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 8 outils

• changes_since≈ 97 tokens

  What changed in the tool economy since a date: verdict flips, deaths, revivals, new servers, confirmed drift — the census diff as data. Poll this weekly to keep a local view current without re-crawling.

  Paramètres, retour & exemple (1)

  Paramètres

  • since · string · optionnel
    YYYY-MM-DD; omit for the whole latest diff

  Exemple d'appel

  {"name": "changes_since", "arguments": {"since": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• check_server≈ 207 tokens

  The FULL evidence behind the verdict for ONE server, by exact registry name — call should_i_use first for the one-word decision; call this when you want the whole record. Leads with the verdict (allow/warn/block), then the `rating` grouped as REACH (answers, latency vs population, protocol, auth), USE (tool count vs population, capability breadth, harness readiness) and TRUST (costume-farm?, duplicate inventory?, verifiability grade, drift / rug-pull, and where checkable whether its ANSWERS are true vs a public primary), a cluster tag, a distinctiveness score, and an explicit not_claimed block. Argument: name.

  Paramètres, retour & exemple (1)

  Paramètres

  • name · string · requis
    exact registry name, e.g. io.github.you/your-mcp

  Exemple d'appel

  {"name": "check_server", "arguments": {"name": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• find_tools≈ 361 tokens

  Find and RANK the trustworthy tool for a NEED. Describe the task in plain words ('screen a company for sanctions', 'US tariff data', 'vessel tracking') — the search is full-text over tool names AND their stored descriptions (stemmed, BM25-ranked), so your words need not appear in any tool's name. Servers come best-rated first, and EACH ROW carries its verdict (allow/warn/block), cluster, distinctiveness and the matching tool names, so you can pick without a second call. Alive, non-costume, current-protocol servers rank on top; dead / costume-farm / walled ones sink. Argument: need.

  Paramètres, retour & exemple (6)

  Paramètres

  • need · string · requis
    what the tool should do, in plain words
  • nature · string · optionnel · retrieval-public | retrieval-private | action | generative | predictive | computational | orchestration
    only servers whose dominant tool nature is this (see robinsaige.com/verification)
  • verdict · string · optionnel · allow | warn | block
    only servers with this verdict
  • free_only · boolean · optionnel
    exclude servers that demand payment at the handshake
  • open_only · boolean · optionnel
    exclude auth-walled servers
  • max_latency_ms · integer · optionnel
    only servers at or under this probe latency

  Exemple d'appel

  {"name": "find_tools", "arguments": {"need": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• list_findings≈ 88 tokens

  The observatory's ruled findings — each with its claim and its falsification test — plus the public corrections log (what we published, then corrected, never deleted). Call this to cite what has been established, or to see where we were wrong. No arguments.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "list_findings", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• registry_pulse≈ 124 tokens

  Call this FIRST for the state of the MCP tool ecosystem in one shot: how many servers exist, how many actually answer a real handshake, how many are behind a login, the largest costume-farm concentration, AND the Tier-2 truth summary (how many server answers were re-derived against a public primary source and matched). Every number is re-derivable; grades observed/reported/derived. No arguments.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "registry_pulse", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• report_call≈ 220 tokens

  AFTER your agent calls a tool, fire-and-forget how it went — success/failure, latency, cost — so the observatory accumulates realized reliability (the one thing outside-in probing can't see: did it actually work for a real call). Anchored against our own probe: a 'worked' report on a server we saw dead is discarded. Does NOT change the current rating yet (probing stays load-bearing) — this is accumulate-ahead-of-demand. Args: server (required), tool, ok, latency_ms, cost_tokens, call_hash (a hash binding the report to a real call).

  Paramètres, retour & exemple (6)

  Paramètres

  • ok · boolean · optionnel
  • tool · string · optionnel
  • server · string · requis
    exact registry name
  • call_hash · string · optionnel
  • latency_ms · integer · optionnel
  • cost_tokens · integer · optionnel

  Exemple d'appel

  {"name": "report_call", "arguments": {"server": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• resolve_server_name≈ 132 tokens

  Resolve a partial or misspelled server name to its EXACT registry id before calling should_i_use / check_server. Matches a fragment against registry NAMES only (not capabilities — for 'which tool does X' use find_tools). Returns candidate exact names with each one's latest liveness outcome. Empty query rejected.

  Paramètres, retour & exemple (1)

  Paramètres

  • query · string · requis
    a fragment of a registry name, e.g. 'tariff'

  Exemple d'appel

  {"name": "resolve_server_name", "arguments": {"query": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• should_i_use≈ 210 tokens

  THE GATE — call this before your agent depends on a tool you don't already trust. Give an exact server registry name and get a one-word verdict — allow / warn / block — with the reason, plus the full rating underneath. 'block' = dead/unreachable/costume-farm-shaped, don't depend on it; 'warn' = usable but look first; 'allow' = safe to depend on. If you have a NEED not a name, use find_tools; if you have a fuzzy name, use resolve_server_name. Argument: name, e.g. 'com.trimtabist/us-tariff-ledger'.

  Paramètres, retour & exemple (2)

  Paramètres

  • name · string · optionnel
    exact registry name, e.g. io.github.you/your-mcp
  • names · array · optionnel
    batch form: vet a whole config at session start (max 20)

  Exemple d'appel

  {"name": "should_i_use", "arguments": {"name": "texte", "names": []}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

https://robinsaige.com/mcp