Skip to main content
Glama
Sugra-Systems

sugra-api-mcp

Official

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
SUGRA_API_KEYYesYour Sugra API key. In HTTP mode with OAuth this becomes a fallback for requests without Bearer
SUGRA_APP_URLNoBase URL of the authorization serverhttps://app.sugra.ai
SUGRA_TIMEOUTNoRequest timeout in seconds30
SUGRA_API_BASENoOverride for self-hosted or beta environmentshttps://sugra.ai
SUGRA_JWKS_URLNoJWKS endpointhttps://app.sugra.ai/oauth/jwks.json
INTERNAL_API_TOKENNoShared secret for the user lookup and MCP activity endpoints on the authorization server
SUGRA_MCP_ALLOWED_HOSTSNoComma-separated hostnames to allow behind a reverse proxy
SUGRA_MCP_ALLOWED_ORIGINSNoComma-separated allowed Origins for browser-based MCP clientschatgpt.com, claude.ai, cursor.sh + others

Capabilities

Features and capabilities supported by this server

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
sugra_entity_screen

Screen a person or organization name against the Sugra sanctions corpus.

Returns a SCREENING SIGNAL, not a compliance determination. Sugra is a technology provider, not a sanctions authority or consumer reporting agency. PEP and adverse-media coverage is supplementary and non-comprehensive - a clear result is not proof of absence, and a hit is a candidate match to review, not a finding.

Output is COMPACT to protect the agent context budget: {status, matches:[{name, score, list, type}], disclaimer}. The verdict status is one of clear, review, or hit. The heavy raw fields (match rationale, source ids, publish dates) are dropped; use the Sugra API directly when the full screening envelope is needed.

Args: name: The person or organization name to screen (required). country: Optional ISO 3166-1 alpha-2 country to narrow the match. dob: Optional date of birth (YYYY-MM-DD) for a person. nationality: Optional nationality to narrow the match.

sugra_entity_lookup

Resolve an entity by identifier and return its composed KYB envelope.

anchor is lei (Legal Entity Identifier, resolved via the GLEIF registry) or vat (EU VAT number, validated via the EU VIES service). The result weaves identity, a sanctions screening signal, and - on request - ownership and adverse-media slices.

The screening verdict is a SCREENING SIGNAL, not a compliance determination, and any PEP / adverse-media content is supplementary and non-comprehensive. The disclaimer field carries this and is always present.

Output is COMPACT by default to protect the agent context budget: {entity:{name, anchor, value, status, country}, screening:{status, top_matches:[...3], hit_count}, ids:{...}, disclaimer}. Pass include to opt INTO fuller per-slice detail, e.g. include=["ownership","adverse_media"] adds those slices in full form.

On a bad anchor or an API error this returns a clean {error, detail} dict rather than raising, so the agent can branch on result.get("error").

Args: anchor: Identifier type, one of lei or vat. value: The identifier value (the 20-char LEI code or the VAT number). include: Optional list of fuller slices to add, e.g. ["ownership", "adverse_media"]. Omit for the compact default.

search_endpointsB

Search the bundled Sugra endpoint catalog by natural-language query.

describe_endpoint

Describe one Sugra API endpoint by operation_id.

Includes agent_hints (duration_class fast/slow/heavy, max_concurrency, bulk billing) so you can budget timeouts and parallelism before calling. POST endpoints with a JSON body also carry request_body_schema (the resolved JSON schema) - construct the body argument from it instead of guessing key names.

call_endpointA

Call a Sugra API endpoint by operation_id from the bundled catalog.

Plan calls with describe_endpoint's agent_hints: duration_class "fast" usually responds in under ~2s, "slow" usually 1-5s and occasionally 15s+ on a cold upstream, "heavy" can exceed the gateway timeout - keep parallel calls within max_concurrency and prefer small batches. Bulk endpoints bill 1 request credit per body item. Failures return structured errors {error, reason, status_code, elapsed_ms, retry_hint}; after "upstream_timeout" a single retry often succeeds because the aborted attempt warms upstream caches.

list_toolsets

List endpoint groups available in the bundled catalog.

fetch_data

One-step fetch: find the best Sugra endpoint for the query and call it.

Combines search_endpoints + call_endpoint into a single round trip. Use this when you want data without manually picking an operation_id. The full search_endpoints + describe_endpoint + call_endpoint dance is still available when you need explicit control, but for most natural-language queries this tool is enough.

Behavior:

  1. Search the bundled catalog for the query. Top match wins.

  2. If the matched endpoint has required parameters and they are all provided in params, call it and return the response.

  3. If required parameters are missing, return the candidate endpoints and the missing-params list so the LLM can retry with the correct params dict on the next call.

Examples:

  • fetch_data("US CPI inflation", params={"series_id": "CPIAUCSL"}) → calls /api/v1/fred/series/CPIAUCSL, returns observations.

  • fetch_data("Bitcoin price", params={"coin_id": "bitcoin"}) → calls /api/v1/crypto/bitcoin/price.

  • fetch_data("Latest financial news") → news_latest has no required params, returns latest news directly.

list_sources

List endpoint source families derived from catalog metadata.

Prompts

Interactive templates invoked by user choice

NameDescription
market_snapshotBuild a sourced price and profile snapshot for one ticker symbol.
macro_briefingBrief the key macro indicators for a country from sovereign sources.
sanctions_screeningScreen a name against the sanctions corpus and report the signal.
sector_compareCompare two sectors through ETF and valuation endpoints.
earth_conditionsReport weather, air quality, and nearby hazards for a coordinate.
source_overviewExplain what the catalog offers for a data domain, sources included.

Resources

Contextual data attached and managed by the client

NameDescription
catalog_domainsEndpoint groups (toolsets) in the bundled Sugra catalog: name, description, and endpoint count per group. Same data as the list_toolsets tool.
catalog_sourcesSource families in the bundled Sugra catalog with endpoint counts per family. Same data as the list_sources tool.
attributionHow Sugra names data sources, where per-call attribution metadata appears, and where the full source list is published.
price_chart_widgetSelf-contained MCP Apps HTML template (SEP-1865) that renders a line chart from a call_endpoint time-series result. Inline CSS and JS only - the template makes no external requests.

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Sugra-Systems/sugra-api-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server