_ registry / mcp streamable-http · checked 2h ago

gsp_mcp

https://www.globalsourcepartners.com

Registry code: 3bd19953eb39549f

api record

GlobalSource Partners provides independent macroeconomic, political, policy and geopolitical research covering emerging and frontier markets worldwide.

Research is produced by locally based country experts with deep in-country knowledge, including economists, former policymakers, government officials and other senior specialists.

endpoint
https://www.globalsourcepartners.com/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is gsp_mcp live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is gsp_mcp free to use?
Yes — the hub reached it with no key and no payment.
What tools does gsp_mcp have?
4 tools: search_research_posts, read_research_author, read_research_post, search_research_entities.
Is gsp_mcp safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
99.5%

90 days 99.7%· all time 99.7%

latency
299ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 353 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • unknown → live
_ what it is for
used for
  • search emerging market research
  • read a country research post
  • find research by entity
takes → gives
text → text, data
tools
4 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 4 tools
4 never probed 0 of 4 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • search_research_posts reads unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "research_entity_uuids"
      ],
      "properties": {
        "limit": {
          "type": "integer",
          "maximum": 50,
          "minimum": 1,
          "description": "Maximum number of posts to return. Minimum 1, maximum 50, default 25."
        },
        "order": {
          "enum": [
            "published_descending",
            "published_ascending"
          ],
          "type": "string",
          "description": "Sort results by publication time. Use 'published_descending' for newest first or 'published_ascending' for oldest first. Default is published_descending."
        },
        "cursor": {
          "type": "string",
          "description": "Pagination cursor returned by a previous response. Use this to retrieve the next page of results."
        },
        "published_after": {
          "type": "string",
          "format": "date-time",
          "description": "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": {
          "type": "string",
          "format": "date-time",
          "description": "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": {
          "type": "boolean",
          "description": "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": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "description": "One or more research entity UUIDs to search against.\n\nThis field is required.\n\nAt least one research entity UUID must be supplied.\n\nDo not pass entity names.\n\nIf the user provides entity names rather than UUIDs, first call the \"search_research_entities\" tool and use the returned UUIDs from that tool.\n"
        }
      }
    }
    arguments 48 lines
  • read_research_author reads unknown 8h ago

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "author_uuid"
      ],
      "properties": {
        "author_uuid": {
          "type": "string",
          "description": "The stable UUID of the research author to read.\n\nUse an author_uuid returned by another research tool.\n"
        }
      }
    }
    arguments 13 lines
  • read_research_post reads unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "post_uuid"
      ],
      "properties": {
        "post_uuid": {
          "type": "string",
          "description": "The stable UUID of the research post to read.\n\nUse a post_uuid returned by search_research_posts.\n"
        }
      }
    }
    arguments 13 lines
  • search_research_entities reads unknown 8h ago

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "query"
      ],
      "properties": {
        "limit": {
          "type": "integer",
          "description": "Maximum number of results to return. Minimum 1, maximum 50, default 10."
        },
        "query": {
          "type": "string",
          "description": "The entity name or approximate entity reference to search for."
        }
      }
    }
    arguments 17 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 3bd19953eb39549f.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/3bd19953eb39549f/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/3bd19953eb39549f/badge.svg)](https://brick.blue/agent/3bd19953eb39549f?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
80%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.