sugra-api-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SUGRA_API_KEY | Yes | Your Sugra API key. In HTTP mode with OAuth this becomes a fallback for requests without Bearer | |
| SUGRA_APP_URL | No | Base URL of the authorization server | https://app.sugra.ai |
| SUGRA_TIMEOUT | No | Request timeout in seconds | 30 |
| SUGRA_API_BASE | No | Override for self-hosted or beta environments | https://sugra.ai |
| SUGRA_JWKS_URL | No | JWKS endpoint | https://app.sugra.ai/oauth/jwks.json |
| INTERNAL_API_TOKEN | No | Shared secret for the user lookup and MCP activity endpoints on the authorization server | |
| SUGRA_MCP_ALLOWED_HOSTS | No | Comma-separated hostnames to allow behind a reverse proxy | |
| SUGRA_MCP_ALLOWED_ORIGINS | No | Comma-separated allowed Origins for browser-based MCP clients | chatgpt.com, claude.ai, cursor.sh + others |
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| 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
Output is COMPACT to protect the agent context budget:
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.
The screening verdict is a SCREENING SIGNAL, not a compliance determination,
and any PEP / adverse-media content is supplementary and non-comprehensive.
The Output is COMPACT by default to protect the agent context budget:
On a bad anchor or an API error this returns a clean Args:
anchor: Identifier type, one of |
| 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 |
| 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:
Examples:
|
| list_sources | List endpoint source families derived from catalog metadata. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| market_snapshot | Build a sourced price and profile snapshot for one ticker symbol. |
| macro_briefing | Brief the key macro indicators for a country from sovereign sources. |
| sanctions_screening | Screen a name against the sanctions corpus and report the signal. |
| sector_compare | Compare two sectors through ETF and valuation endpoints. |
| earth_conditions | Report weather, air quality, and nearby hazards for a coordinate. |
| source_overview | Explain what the catalog offers for a data domain, sources included. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| catalog_domains | Endpoint groups (toolsets) in the bundled Sugra catalog: name, description, and endpoint count per group. Same data as the list_toolsets tool. |
| catalog_sources | Source families in the bundled Sugra catalog with endpoint counts per family. Same data as the list_sources tool. |
| attribution | How Sugra names data sources, where per-call attribution metadata appears, and where the full source list is published. |
| price_chart_widget | Self-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
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
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