com.globalsourcepartners/emerging-markets-research

Est-ce que com.globalsourcepartners/emerging-markets-research est sûr ?

Au dernier audit MCP Hub, le serveur MCP « com.globalsourcepartners/emerging-markets-research » 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 4 outils

• read_research_author≈ 520 tokens

  Read a single research author by author UUID. Use this tool when a user wants profile details for a specific research author returned by another research tool. The response includes author metadata, biography fields, profile URL, and visible sectors associated with the author. Missing, inactive, non-author, and hidden-sector-only authors return a generic not-found error.

  Paramètres, retour & exemple (1)

  Paramètres

  • author_uuid · string · requis
    The stable UUID of the research author to read. Use an author_uuid returned by another research tool.

  Exemple d'appel

  {"name": "read_research_author", "arguments": {"author_uuid": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"author_name": "texte", "author_uuid": "texte", "author_sectors": [], "author_profile_url": "texte", "author_biography_html": "texte", "author_short_biography": "texte"}}

• read_research_post≈ 803 tokens

  Read a single published research post by post UUID. Use this tool after calling search_research_posts and selecting the most relevant result. The response includes post metadata, authors, sectors, body HTML, and a URL. Depending on the authenticated MCP user's permissions, the body HTML and URL may expose either the full research post or teaser content. Missing, unpublished, and hidden-sector posts return a generic not-found error.

  Paramètres, retour & exemple (1)

  Paramètres

  • post_uuid · string · requis
    The stable UUID of the research post to read. Use a post_uuid returned by search_research_posts.

  Exemple d'appel

  {"name": "read_research_post", "arguments": {"post_uuid": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"post_url": "texte", "post_type": "texte", "post_uuid": "texte", "post_title": "texte", "post_authors": [], "post_sectors": [], "post_updated": "texte", "post_body_html": "texte", "post_published": "texte", "post_snippet_notice": "texte"}}

• search_research_entities≈ 810 tokens

  Search research entities by name or approximate name. Use this tool whenever a user refers to an entity by name and a research entity UUID is needed. Results are ranked by match quality and include the research entity UUIDs required by other research tools. When multiple results are returned, review the entity name, description, match type, match confidence, and available research count to determine the most appropriate entity before using its entity_uuid in another tool. This tool only searches existing research entities and does not create or modify data.

  Paramètres, retour & exemple (2)

  Paramètres

  • limit · integer · optionnel
    Maximum number of results to return. Minimum 1, maximum 50, default 10.
  • query · string · requis
    The entity name or approximate entity reference to search for.

  Exemple d'appel

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

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"limit": 1, "results": [], "queried_name": "texte", "total_results_count": 1}}

• search_research_posts≈ 2020 tokens

  Search published research posts associated with one or more research entities. This tool requires research entity UUIDs. If only entity names are known, first call search_research_entities to obtain candidate research entities and their UUIDs. Use only entity_uuid values copied exactly from search_research_entities results. Never infer, guess, construct, or transform UUIDs from entity names. Use this tool only after selecting the most appropriate research entity from the search_research_entities results. Examples: - To find research about "United States", first call search_research_entities with "United States", review the returned matches, select the most appropriate entity, and then call this tool with the selected entity_uuid. - To find recent research about multiple entities, pass all selected entity_uuid values in research_entity_uuids. - To retrieve the next page of results, pass the previous response's next_cursor as cursor. Results can be filtered by publication date and retrieved using cursor-based pagination.

  Paramètres, retour & exemple (7)

  Paramètres

  • limit · integer · optionnel
    Maximum number of posts to return. Minimum 1, maximum 50, default 25.
  • order · string · optionnel · published_descending | published_ascending
    Sort results by publication time. Use 'published_descending' for newest first or 'published_ascending' for oldest first. Default is published_descending.
  • cursor · string · optionnel
    Pagination cursor returned by a previous response. Use this to retrieve the next page of results.
  • published_after · string · optionnel
    Only return posts published after this timestamp. Provide a complete RFC 3339 timestamp including a timezone, for example 2026-08-01T00:00:00Z. Date-only values such as 2026-08-01 are not accepted.
  • published_before · string · optionnel
    Only return posts published before this timestamp. Provide a complete RFC 3339 timestamp including a timezone, for example 2026-08-01T00:00:00Z. Date-only values such as 2026-08-01 are not accepted.
  • count_total_results · boolean · optionnel
    Whether to include the total number of matching posts. Use false unless the total count is specifically needed. Calculating the total count may increase response time for large result sets.
  • research_entity_uuids · array · requis
    One or more research entity UUIDs to search against. This field is required. At least one research entity UUID must be supplied. Do not pass entity names. If the user provides entity names rather than UUIDs, first call the "search_research_entities" tool and use the returned UUIDs from that tool.

  Exemple d'appel

  {"name": "search_research_posts", "arguments": {"research_entity_uuids": []}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"limit": 1, "order": "texte", "results": [], "next_cursor": "texte", "published_after": "texte", "published_before": "texte", "research_entities": [], "total_results_count": 1}}

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