com.mcplookup/mcp

Est-ce que com.mcplookup/mcp est sûr ?

Au dernier audit MCP Hub, le serveur MCP « com.mcplookup/mcp » 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 3 outils

• find_servers≈ 1318 tokens

  Find a compact, trust-aware shortlist for a task or capability when no particular MCP server or product is known. Search by free text or MCPLookup's normalized capability taxonomy, with optional filters. Free text returns a reviewed identity-only slate when available; otherwise results are explicitly labelled catalog matches, and the two evidence lanes are never mixed. Returns at most five results with no pagination. A selected exact server name can be passed to resolve_server for reviewed identity context and connection options; named artifacts fit resolve_server directly.

  Paramètres, retour & exemple (6)

  Paramètres

  • kind · string · optionnel · package | remote | hybrid | neither
    Optional deployment kind.
  • limit · integer · optionnel
    Number of results; hard maximum 5.
  • query · string · optionnel
    Free-text discovery query when no exact server is known, such as 'postgres database'.
  • industry · string · optionnel · horizontal-general | financial-services | crypto-web3 | healthcare-life-sciences | retail-ecommerce | media-entertainment | real-estate-property | travel-hospitality
    Optional normalized industry category.
  • order_by · string · optionnel · relevance | trust | adoption
  • capability · string · optionnel · search-retrieval | data-access | knowledge-memory | web-extraction | software-development | infrastructure-devops | content-creation | media-processing
    Normalized capability category; required when query is omitted.

  Exemple d'appel

  {"name": "find_servers", "arguments": {"kind": "package", "limit": 1, "query": "texte", "industry": "horizontal-general", "order_by": "relevance", "capability": "search-retrieval"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"filters": {}, "servers": [], "has_more": true, "identity": "texte", "order_by": "texte"}}

• resolve_server≈ 1323 tokens

  Resolve a named MCP server, vendor, product, package, repository, Registry identifier, or endpoint to a canonical MCPLookup identity. Returns at most five reviewed candidates with query-relative identity and publisher explanations, a compact trust assessment, and current connection options. This is the best fit when a particular artifact or product is known; find_servers covers open-ended capability discovery, while trust_lookup returns the full current evidence record for an exact canonical name.

  Paramètres, retour & exemple (1)

  Paramètres

  • identifier · string · requis
    Exact package identifier, endpoint URL, canonical name, or complete organization, product, or service name.

  Exemple d'appel

  {"name": "resolve_server", "arguments": {"identifier": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"status": "resolved_with_servers", "matches": [], "has_more": true, "identity": "texte"}}

• trust_lookup≈ 900 tokens

  Return MCPLookup's complete current trust record for one exact canonical MCP server name. Includes the verdict, Trust Index band and 0–100 score with confidence, coarse safety, maintenance, adoption, and provenance bands, coverage, freshness, public evidence, and citation. This fits trust questions and evidence review after identity is known; resolve_server handles ambiguous names or coordinates. Current state only—no history or safety certification.

  Paramètres, retour & exemple (1)

  Paramètres

  • server_name · string · requis
    Exact MCPLookup server name, e.g. 'io.github.owner/name'.

  Exemple d'appel

  {"name": "trust_lookup", "arguments": {"server_name": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"record": "texte", "status": "found", "recovery": "texte", "requested_server_name": "texte"}}

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://mcplookup.com/mcp