Sugra MCP

{
  "id": "aix_6bb2611745",
  "name": "Sugra MCP",
  "operator": "(unclaimed - source: registry-official · publisher: ai.sugra)",
  "description": "Connect AI agents to primary sources - markets, macro, entities, news, network, earth and research.",
  "depth": 1,
  "status": "unclaimed",
  "last_crawled": "2026-11-03",
  "missing_fields": [
    "pricing",
    "reputation",
    "aix_score",
    "operator.identity"
  ],
  "skills": [
    "calendar-sync",
    "onchain-data"
  ],
  "protocols": {
    "mcp": "https://mcp.sugra.ai/mcp",
    "a2a": null
  },
  "pricing": null,
  "regions": [
    "global"
  ],
  "languages": [
    "en"
  ],
  "reputation": null,
  "aix_score": null,
  "verification": {
    "identity": "none",
    "health": "liveness-only",
    "pricing": "unknown",
    "last_check": "2026-11-03T09:01:00.364Z"
  },
  "pricing_model": "unknown",
  "links": [
    {
      "label": "repository",
      "url": "https://github.com/Sugra-Systems/sugra-api-mcp"
    }
  ],
  "avatar": "https://github.com/Sugra-Systems.png?size=160",
  "socials": [
    {
      "label": "github",
      "url": "https://github.com/Sugra-Systems"
    }
  ],
  "payment_method": "oauth",
  "unreachable": false,
  "profile": {
    "mcp_server": "sugra-api",
    "mcp_version": "0.13.0",
    "tool_count": 11,
    "tools": [
      {
        "name": "sugra_entity_screen",
        "description": "Screen a person or organization name against the Sugra sanctions corpus.\n\nReturns a SCREENING SIGNAL, not a compliance determination. Sugra is a\ntechnology provider, not a sanctions authority or consumer reporting agency.\nPEP and adverse-media coverage is supplementary and non-comprehensive - a\n`clear` result is not proof of absence, and a `hit` is a candidate match to\nreview, not a finding.\n\nOutput is COMPACT to protect the agent context budget:\n`{status, matches:[{name, score, list, type}], disclaimer}`. The verdict\n`status` is one of `clear`, `review`, or `hit`. The heavy raw fields\n(match "
      },
      {
        "name": "sugra_entity_lookup",
        "description": "Resolve an entity by identifier and return its composed KYB envelope.\n\n`anchor` is `lei` (Legal Entity Identifier, resolved via the GLEIF registry)\nor `vat` (EU VAT number, validated via the EU VIES service). The result\nweaves identity, a sanctions screening signal, and - on request - ownership\nand adverse-media slices.\n\nThe screening verdict is a SCREENING SIGNAL, not a compliance determination,\nand any PEP / adverse-media content is supplementary and non-comprehensive.\nThe `disclaimer` field carries this and is always present.\n\nOutput is COMPACT by default to protect the agent context budget"
      },
      {
        "name": "search_endpoints",
        "description": "Search the bundled Sugra endpoint catalog by natural-language query.\n\nUse this to pick an operation_id. It does not fetch data. Typical loop:\n1. search_endpoints(query) -> ranked hits with required_parameters\n2. describe_endpoint(operation_id) -> params, request_body_schema, agent_hints\n3. call_endpoint(operation_id, params=..., body=...) or fetch_data(query, params=...)\n\nFilter with toolset or source only after list_toolsets / list_sources;\na misspelled filter is an error, not a silent empty result.\n\nExamples:\n- search_endpoints(\"US CPI inflation\")\n- search_endpoints(\"AAPL price\", toolset=\"ma"
      },
      {
        "name": "describe_endpoint",
        "description": "Describe one Sugra API endpoint by operation_id.\n\nIncludes agent_hints (duration_class fast/slow/heavy, max_concurrency,\nbulk billing) so you can budget timeouts and parallelism before calling.\nPOST endpoints with a JSON body also carry request_body_schema (the\nresolved JSON schema) - construct the `body` argument from it instead\nof guessing key names. Call this after search_endpoints and before\ncall_endpoint when you need the exact parameter names and examples.\n"
      },
      {
        "name": "call_endpoint",
        "description": "Call a Sugra API endpoint by operation_id from the bundled catalog.\n\nPlan calls with describe_endpoint's agent_hints: duration_class \"fast\"\nusually responds in under ~2s, \"slow\" usually 1-5s and occasionally 15s+\non a cold upstream, \"heavy\" can exceed the gateway timeout - keep parallel\ncalls within max_concurrency and prefer small batches. Bulk endpoints bill\n1 request credit per body item. Failures return structured errors {error,\nreason, status_code, elapsed_ms, retry_hint}; after \"upstream_timeout\" a\nsingle retry often succeeds because the aborted attempt warms upstream\ncaches.\n"
      },
      {
        "name": "list_toolsets",
        "description": "List catalog groups with endpoint counts and short descriptions.\n\nUse the group names as the toolset filter on search_endpoints. This\ndoes not call the Sugra API; it reads the bundled catalog.\n"
      },
      {
        "name": "fetch_data",
        "description": "One-step fetch: find the best Sugra endpoint for the query and call it.\n\nCombines search_endpoints + call_endpoint into a single round trip. Use\nthis when you want data without manually picking an operation_id. The\nfull search_endpoints + describe_endpoint + call_endpoint dance is still\navailable when you need explicit control, but for most natural-language\nqueries this tool is enough.\n\nBehavior:\n1. Search the bundled catalog for the query. Top match wins.\n2. If the matched endpoint has required parameters and they are all\n   provided in `params`, call it and return the response.\n3. If require"
      },
      {
        "name": "list_sources",
        "description": "List source families in the bundled catalog with endpoint counts.\n\nUse the family names as the source filter on search_endpoints. This\ndoes not call the Sugra API.\n"
      },
      {
        "name": "resolve_entity",
        "description": "Resolve free text to a canonical market or macro entity.\n\nTurns a ticker, company name, macro indicator, coin, or currency pair into\nthe agent plane's ``{namespace, ids}`` entity for use with get_snapshot and\nget_timeseries. A cross-namespace collision (e.g. a ticker that is both an\nequity and a coin) returns status \"ambiguous\" with ranked candidates and\nNEVER silently picks one; pass type_hint (e.g. \"equity\", \"etf\", \"coin\") to\nnarrow the universe. Crypto aliases resolve too (e.g. \"bitcoin\" -> the\nBTC coin entity). Status \"low_confidence\" means the best match cleared\nresolution but scored weak"
      },
      {
        "name": "get_snapshot",
        "description": "Composed current view of an entity via a named recipe.\n\nExecutes a fixed server-side recipe (company_snapshot, etf_snapshot,\nquote_snapshot, macro_indicator_snapshot, macro_calendar,\nearnings_snapshot, debt_snapshot) and returns one envelope with freshness,\nprovenance, per-component coverage, and billing. Composed calls charge the\nrecipe's fixed cost (1-2 units) from the daily quota. status \"partial\"\nmeans an optional component was unavailable - the present components are\nstill trustworthy; honor the freshness block (stale=true means the data\naged past its budget); for macro_calendar, entity i"
      },
      {
        "name": "get_timeseries",
        "description": "Bounded timeseries for an entity: price, macro_series, etf_flows or\netf_monthly_flows.\n\nReturns points oldest-first with an explicit downsampling flag when the\nraw series exceeded max_points. Times are UTC. Costs 1 unit per call.\n\nRead the step from ``served_granularity``, not ``granularity``. The\nlatter echoes the request; the former is the step the source built the\npoints at, and the two can differ (a long price range can come back as\nmonthly bars under a \"1d\" request). It reads ``mixed`` when the points do\nnot share one step, ``unknown`` when the source does not say, and null\nwhen no point "
      }
    ],
    "profiled_at": "2026-11-03T09:01:00.364Z"
  }
}