com.searchfragments/search-fragments

Est-ce que com.searchfragments/search-fragments est sûr ?

Au dernier audit MCP Hub, le serveur MCP « com.searchfragments/search-fragments » 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

• resolve_fragment≈ 1228 tokens

  Pieces together the name of a film, TV or radio show, song, book, game, quote, person, place, event or research study from the fragments a user remembers: a scene, a line, a face, roughly when. Pass every fragment in the user's own words, even uncertain ones. It searches many sources and fits them together. A shortlist or an honest "can't place it" is still useful. Use it when your own search couldn't place it. Not for known titles, trivia, recommendations or checking claims (use verify_claim). When the user says whether this helped, report it with submit_resolution_feedback.

  Paramètres, retour & exemple (1)

  Paramètres

  • fragment · string · requis
    The half-remembered or fragment-shaped query, in the user's own words. Must be at least 5 characters and describe the thing being recalled by premise, plot, relationship, or context.

  Exemple d'appel

  {"name": "resolve_fragment", "arguments": {"fragment": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"pool": [], "leads": [], "outcome": "resolved", "summary": "texte", "evidence": [], "candidate": "texte", "narrow_it": [], "territory": [], "reject_reason": "texte", "resolution_id": 1, "is_sf_question": true, "verification_state": "SUPPORTED_RELATION"}}

• submit_resolution_feedback≈ 549 tokens

  After the user reacts to a resolve_fragment result, call this with its resolution_id. accepted: it is what they meant. partial: it helped but is not quite it. rejected: it is not what they meant. If they recognised an item in the shortlist or leads, send picked_rank (1 = first item) or picked_url; if nothing fitted, send none_fitted: true. corrected_target and new_clue are optional and are stored as feedback only; they never change graph facts.

  Paramètres, retour & exemple (8)

  Paramètres

  • note · string|null · optionnel
    Optional free-text note. Max 1000 characters. No personal data.
  • status · string · requis · accepted | rejected | partial
    accepted: the result is what the user meant. partial: it helped but is not quite it. rejected: it is not what the user meant.
  • new_clue · string|null · optionnel
    Optional. An extra detail the user remembered after seeing the result. Max 500 characters.
  • picked_url · string · optionnel
    URL of the item the user recognised.
  • none_fitted · boolean · optionnel
    True if the user looked and nothing fitted.
  • picked_rank · integer · optionnel
    Position of the shortlist or lead item the user recognised.
  • resolution_id · number · requis
    The resolution_id returned by the resolve_fragment call this feedback is about.
  • corrected_target · string|null · optionnel
    Optional. What the user was actually thinking of, if they know it. Max 300 characters.

  Exemple d'appel

  {"name": "submit_resolution_feedback", "arguments": {"status": "accepted", "resolution_id": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"status": "accepted", "recorded": true, "resolution_id": 1}}

• verify_claim≈ 730 tokens

  Checks whether current web sources support a specific factual assertion. Takes a claim as a natural-language statement; returns a verdict with cited evidence and stated limits. Verdict set: - "supported" — multiple independent sources directly confirm the specific claimed detail - "partially_supported" — sources confirm the entity and domain; specific detail is pointed to but not directly stated - "insufficient_evidence" — sources don't address the specific claim; fires freely, including when the entity is well-known but the specific detail is undocumented - "unsupported" — a credible source explicitly contradicts the claim All verdicts are DECIDE-BY-EYE. A "supported" verdict means current web sources confirm it — not that it is true. Evidence may be incomplete, biased, or outdated. The stated_limits field is always present and identifies what the evidence cannot confirm. Good input shape (specific, checkable assertions): - "Werner Herzog dragged a full-size steamship over a hill during the filming of Fitzcarraldo" - "Glenn Gould stopped giving live concerts in 1964" - "The Backrooms photograph originated on 4chan" Checks one specific factual statement. Not for identifying half-remembered works. Not this shape: - "there's a documentary about a filmmaker dragging a boat over a mountain" - "a musician famous for stopping performing"

  Paramètres, retour & exemple (1)

  Paramètres

  • claim · string · requis
    A specific factual assertion to check against current web sources. Should be a concrete, checkable statement — not a question or a half-remembered fragment.

  Exemple d'appel

  {"name": "verify_claim", "arguments": {"claim": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"verdict": "supported", "evidence": [], "stated_limits": "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://searchfragments.com/api/mcp